The Symantec Embedded Database service not present under services.msc and the Symantec Endpoint Protection Manager fails to start.
Last Updated December 15, 2011
The Symantec Embedded Database Service no longer starts since the service responsible for its functioning is not present under services.msc. This condition prevents the Symantec Endpoint Protection Manager (SEPM) from starting.
While trying to open the SEPM, the following error appears : "Failed to connect to Server."
When checking services.msc, the Symantec Embedded database Service is not listed.
Restore Database and Repairing the Symantec Endpoint Protection Manager does not resolve the issue..
Here are the recommended steps:
Stop the Symantec Endpoint Protection Manager Service.
Using Windows Explorer, navigate to "...\Program Files\Symantec\Symantec Endpoint Protection Manager\Bin".
Run the the file: Upgrade.Bat (Complete the Upgrade Wizard.)
Reboot the system.
From Services.msc, and check if the Symantec Embedded Database service is now listed.
Ensure Symantec Embedded Database service and Symantec Endpoint Protection Manager service are Started.
Verify SEPM functionality by logging on to the SEPM.
Windows Server 2003 R2 32 Bit
Symantec Endpoint Protection Manager 12.1 RU1
Imported Document ID: TECH176614
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe