The Symantec Endpoint Protection service stops with a "java -1" error in event log and the error "Failed to connect to server" at login.

Symantec.com > Enterprise > Support > Knowledge Base

The Symantec Endpoint Protection service stops with a "java -1" error in event log and the error "Failed to connect to server" at login.

Question/Issue:
How to resolve the login error "Failed to connect to server."

Symptoms:
The scm-server-0.log file reports HTTP 401 unauthorized.
IIS log shows status codes 401 3 64 and 404 0 64 when attempting to connect to the Endpoint Manager.
The Symantec Endpoint Protection Manager service is not listed in the IIS admin service restart dependency list.

Cause:
Unresponsive IIS services will not allow the Endpoint Protection Manager service to stay started.

Solution:
To reset unresponsive IIS services:

Click Start, then Run.
Type inetmgr, then click OK.
Right click on the Server name (location) immediately under Internet Information Services.
Click Disconnect.
Close the Internet Information Services (IIS) Manager window.
Click Start, then Run.
Type services.msc, then click OK.
Right-click the IIS Admin Service and click Restart.

If connectivity with the Endpoint Protection Manager (SEPM) is not restored please refer to the document below or call Symantec Technical Support for further assistance.

References:
Symantec Endpoint Protection Manager 11.x communication troubleshooting:
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007101711103548

Document ID: 2008030400460348
Last Modified: 02/17/2009
Date Created: 03/03/2008
Operating System(s): Windows Server 2003 Web/Standard/Enterprise/Datacenter Edition
Product(s): Endpoint Protection 11
Release(s): Endpoint Protection 11 [All Releases]