Symantec Endpoint Protection Manager not starting after migration to RU5.

Products

• Endpoint Protection

Issue/Introduction

Migrated to RU5 from MR2 or MR3 and the Symantec Endpoint Protection Manager service is not starting.

Symptoms
The migration installation completes without issue however, the manager console is not starting. You might get an error by trying to start the Symantec Endpoint Protection Manager service. Error 1067 - "The Service could not start because it had terminated unexpectedly". In the Windows System Event logs you see Error 7031 SEPM service failed to start.

Cause

The Migration installation failed to restart the machine and the installation fails without a warning.

Resolution

Restart/Reboot the server first, the SEPM service should be started now but still not able to log in warning about the Database not being synchronized.
Run the upgrade.bat to migrate the database in C:\PROGRAMM FILES\SYMANTEC\SYMANTEC ENDPOINT PROTECTION MANAGER\BIN\

After the database upgrade the Manager console should be able to start and the user able to log in.

References

http://service1.symantec.com/support/ent-security.nsf/docid/2009111202394748
http://service1.symantec.com/support/ent-security.nsf/docid/2009092423245648

Technical Information

You can find the following at the end of the SEPM_INST.LOG file found under %TEMP% or the windows TEMP folder.


MSI (c) (B0:C8) [11:19:22:953]: Note: 1: 1707
MSI (c) (B0:C8) [11:19:22:953]: Product: Symantec Endpoint Protection Manager -- Installation operation completed successfully.

MSI (c) (B0:C8) [11:19:22:968]: The Windows Installer initiated a system restart to complete or continue the configuration of 'Symantec Endpoint Protection Manager'.

MSI (c) (B0:C8) [11:19:22:984]: Grabbed execution mutex.
MSI (c) (B0:C8) [11:19:22:984]: Cleaning up uninstalled install packages, if any exist
MSI (c) (B0:C8) [11:19:22:984]: MainEngineThread is returning 3010