The following process has been performed. version 12.1.1xxx: 1. Stop Symantec Embedded Database and Symantec Endpoint Protection Manager services in the Services.MSC. 2. Rename sem5.log to sem5.log.old Path for 32 Bit: "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\" Path for 64 Bit: "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\" 3. Click Start, click on Run and Type “CMD” then click OK 4. In the Command prompt (as Administrator if applicable): For 32 Bit, type: "CD C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\" For 64 Bit, type: "CD C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\ASA\win32\" and press Enter. This will change directories to the folder containing dbsrv11.exe. 5. Force the recreation of sem5.log. For 32 Bit, type: dbsrv11 -f "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db" For 64 Bit, type: dbsrv11 -f "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db" and press Enter. 6. Click Start, click on Run and Type “Services.MSC” then click OK and start the Symantec Embedded Database Service 7. Start the Symantec Endpoint Protection Manager service. 8. If it stays started then go ahead and log into the Symantec Endpoint Protection Manager and everything should now be working properly. OR If the Symantec Endpoint Protection Manager service fails to start then run Management Server Configuration Wizard in order to log in to the Symantec Endpoint Protection Manager. To force the recreation of sem5.log, the error pop up as shown in the attachement.