If configured to use the embedded database verify that it is running and reachable.Verify the connection to the SQL database from the SEPM machine.If configured to use a Microsoft SQL server and the database is down or the machine unreachable this can also cause the SEPM service to shut down.Once this is completed the Symantec Endpoint Protection Manager service should start properly again. Open up the "Management Server Configuration Wizard" from the start menu and walk through the "Reconfigure the management server" wizard to make sure all settings for the database are correct.If you see this error just after an install or a database reconfiguration or restore then the error might be caused by incomplete database settings.If running on a 64bit machine IIS needs to be in 64bit mode(default but can be changed by other programs if IIS is running other sites before the install of the manager.To correct this go to the Properties dialog of the Default Web Site (or the site configured during the install) in the IIS management console and change the IP address binding back to (All Unassigned).This issue can happen if the SEPM web server in IIS is set to bind to a specific IP address instead of (All Unassigned) which is the default.Most common are problems connecting to the database but examine the full list of possible causes below. This problem can have several different causes. In the event log there is an error: "The Java Virtual Machine has exited with a code of -1, the service is being stopped". The Symantec Endpoint Protection Manager (SEPM) 11.x service "SemSrv" stops a few seconds after it has been started. %programfiles%\Symantec\Symantec Endpoint Protection Manager\tomcat\logs
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |