ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Symantec Endpoint Protection Manager could not connect to the database.

book

Article ID: 155275

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

When the Administrator attempts to log on the Symantec Endpoint Protection Manager (SEPM), the following error is presented:
 

Error: Failed to connect to the server.

Symptoms:
 
1)      SEPM services stopped.
2)      ODBC connection credentials are not getting synchronized.
3)      Cannot run the Server Configuration Wizard due to the fact that the default port (8443) was already in use.
4)      Windows Application Event Logs display a “Java -1 error” for the failed logon attempt.
5)      In the “C:\Program Files\Symantec Endpoint Protection Manager\tomcat\logs\catalina.out” file, the following error message is seen (multiple times.):
Com.Sygate.SCM.Server.Util.SCMServerError: Failed to connect to database after tried 20 times. Please start the data

Failed to connect to the server.

Cause

When the SEPM was installed, the defaults were used and the default port (8443) was already in use.
Accordingly, the service “Symantec Endpoint Protection Manager Webserver” is missing.

This can be confirmed by the following steps:
  1. Click Start > Run
  2. Type Services.msc > Enter
  3. Scroll down to the Symantec services and confirm the state of the service:
Symantec Endpoint Protection Manager Webserver
 

Resolution

Change the port to an unused port by following the Disaster Recovery procedure.

In performing the Disaster Recovery procedure to restore the SEPM Webserver service, select a port number other than the default port 8443.

Symantec Endpoint Protection 12.1: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager
http://www.symantec.com/docs/TECH160736


Applies To

SQL 2005 Database.

Symantec Endpoint Protection 12.1