Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

How to resolve the login error " Failed to connect to server " ?

Created: 20 Jul 2009 • Updated: 22 May 2010 | 4 comments
This issue has been solved. See solution.

The Symantec Endpoint Protection Manager Console service stop

Windows Event Viewer Application Log appear this error :
Event ID: 4096
Source: SemSrv
Description: The Java Virtual Machine has exited with a code of -1, the service is being stopped.

Comments 4 CommentsJump to latest comment

Rafeeq's picture

Hi,

is this a fresh install?
were u able to log in before successfully?
go to services and check if Symantec Embedded database service is started if you are using Embedded database.
check this link hope this helps

http://service1.symantec.com/SUPPORT/ent-security....

Rafeeq

Thomas K's picture

Another possible cause - The transaction log in the SQL server has become full preventing the SEPM from communicating properly with the database.

http://service1.symantec.com/SUPPORT/ent-security....

What http errors are showing in the smc-server log?

Aniket Amdekar's picture

Hi,

The first step should always be to check the scm-server-0.log file in the sepm\tomcat\logs folder.

Also check the catalina.out logfile. It may contain info if there is a port conflict on the server.

In the scm-server-0.log, you will find the error in the line, just before the indentation changes!! 

Also, f you have upgraded the SEPM, then you will have upgrade.log . That log is extremely useful in case of troubleshooting Java 01 in SEP SBE 12

Please post the error message from the logs above, and then we can decide the steps ahead.

Cheers,
Aniket

SOLUTION
Yesd0g's picture

Check the scm-server-0.log for Http error 503

Another test is to access http://localhost:8014/Reporting or http://localhost:8014/secars/secars?hello,secars  Through Internet Explorer and see if it gives you a "Service Unavailable" error.

And a third test to check is if there are any errors in the Event Viewer related to rpcproxy.dll.

If you find the issues above, the most likely problem is that the Default Application Pool is not starting.