The Symantec Endpoint Protection Manager (SEPM) service starts but will not stay running, and so users cannot login to the console. The Windows Event logs report that the Java virtual Machine has exited with a code -1.

The SCM-server-0.log displays the following errors:

012-06-26 11:29:18.642 THREAD 1 SEVERE: user.country = US
2012-06-26 11:29:18.642 THREAD 1 SEVERE: scm.server.version = 12.1.1000.157
2012-06-26 11:29:42.382 THREAD 1 SEVERE:
org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.)
 at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createPoolableConnectionFactory(BasicDataSource.java:1549)
 at org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:1388)
 at org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection(BasicDataSource.java:1044)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:522)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:419)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:404)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:394)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDBConnection(DatabaseUtilities.java:2588)
 at com.sygate.scm.server.db.util.DatabaseUtilities.testConnection(DatabaseUtilities.java:2545)

This error can be caused if Windows authentication is used for connecting the SEPM to the MS SQL database, and the credentials supplied are subsequently locked out due to a password policy on the domain

To overcome this, run the SEPM Management Configuration Wizard specifying a SQL account and password for connecting to the SEM5 database.

Applies To

Symantec Endpoint Protection ver 12.1 RU1

SQL 2008 database