You receive the following Java-1 error in the scm-server-0.log: "Can't read local server from database!"

book

Article ID: 178018

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

After running the Symantec Endpoint Protection Management Server Configuration Wizard, either to reconfigure the server or to perform disaster recovery, the Symantec Endpoint Protection Manager service will not stay started and generates a "Java-1" error.

 

You see the following error in the scm-server-0.log:

"2009-10-26 15:46:45.352 SEVERE: Unknown Exception in: com.sygate.scm.server.consolemanager.RequestHandler
com.sygate.scm.server.util.ScmServerError: Can't read local server from database!"

Cause

When running the Symantec Endpoint Protection Management (SEPM) Server Configuration Wizard, the incorrect case sensitive spelling of the server name was provided. Java is case sensitive, therefore the server name that is entered into the database during the initial installation is also case sensitive.

Resolution

Re-run the Symantec Endpoint Protection Management Server Configuration Wizard and input the correct server name.  If you left the default value and it failed, attempt to use the all lower-case or all upper-case alternative to the server name listed.  If both options fail, you can use the server IP address or contact Symantec Technical Support for further assistance.

Please note that code improvements in Symantec Endpoint Protection 12.1 Release Update 4 (SEP 12.1.4) should help to remedy this specific cause of the Java error.  Please upgrade to take advantage of this and many other important enhancements and improvements.


Attachments