"Unexpected Error" when logging in after server name change in conf.properties
search cancel

"Unexpected Error" when logging in after server name change in conf.properties

book

Article ID: 178018

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

When logging into the Endpoint Protection Manager you receive an "Unexpected Error" popup. You recently manually changed the server name in the Endpoint Protection Manager (SEPM) conf.properties file.

The following error is seen in the scm-server-0.log:

com.sygate.scm.server.util.ScmServerError: Can't read local server from database!

Cause

Manually editing the server name in the conf.properties file of the SEPM does not update the site in the database resulting in the SEPM being unable to find a server of the new name entered in the conf.properties in the database.

Resolution

Change the name back to the original name in the conf.properties and restart the SEPM services.

If you need to change the name of the server, such as going from short name to FQDN to match a new certificate, you must do so by running the Management Server Configuration Wizard and editing the server name from there which will update the conf.properties and add the new server name to the database.