Endpoint Protection

Hi All,

After the successfull upgrade of SEPM v11.0.6005 into v12.1 somehow my SEPM console login is always failed.

I have tried LDAP and local SEP (admin) account but always end up with "Local authorization failed" message.

The database is using SQL Server 2005 SP4.

Can anyone please assist me here ?

Hi,

Check this Forums

https://www-secure.symantec.com/connect/forums/administrators-user-name-or-password-incorrect-symantec-endpoint-protection-manager

I still receive "Unexpected Server Error"

can you attach teh file scm-server-0.log after you attempt to login?

2012-07-25 19:04:47.484 THREAD 1 SEVERE: ================== Server Environment ===================

2012-07-25 19:04:47.484 THREAD 1 SEVERE: os.name = Windows Server 2008

2012-07-25 19:04:47.484 THREAD 1 SEVERE: os.version = 6.0

2012-07-25 19:04:47.484 THREAD 1 SEVERE: os.arch = x86

2012-07-25 19:04:47.484 THREAD 1 SEVERE: java.version = 1.6.0_26

2012-07-25 19:04:47.484 THREAD 1 SEVERE: java.vendor = Sun Microsystems Inc.

2012-07-25 19:04:47.484 THREAD 1 SEVERE: java.vm.name = Java HotSpot(TM) Client VM

2012-07-25 19:04:47.484 THREAD 1 SEVERE: java.vm.version = 20.1-b02

2012-07-25 19:04:47.484 THREAD 1 SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jre

2012-07-25 19:04:47.484 THREAD 1 SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat

2012-07-25 19:04:47.484 THREAD 1 SEVERE: java.user = null

2012-07-25 19:04:47.484 THREAD 1 SEVERE: user.language = en

2012-07-25 19:04:47.484 THREAD 1 SEVERE: user.country = AU

2012-07-25 19:04:47.484 THREAD 1 SEVERE: scm.server.version = 12.1.1000.157

Are you using the same shortcuts which you were used to login to 11.0.x server? If yes, please delete it and create a new shortcut to the file: sesm.bat, which is located by default in the folder: C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\

Hi ARavind, it is already pointing to the sesm.bat

Try by repairing SEPM from add/remove programs...

Hi Dushan,

Try to upgrade thru upgrade.bat file from C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\

2012-07-27 09:46:27.510 THREAD 1 INFO: logger initialized ...

2012-07-27 09:46:27.510 THREAD 1 INFO: SEPM Server Home:[C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Tools\..\tomcat]

2012-07-27 09:46:28.807 THREAD 1 INFO: Initialized the database.

2012-07-27 09:46:28.916 THREAD 1 SEVERE: Error occurred.

com.sygate.scm.server.metadata.MetadataException: 

at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:915)

at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:881)

at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:921)

at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:947)

at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:250)

at com.sygate.scm.server.configmanager.ConfigManagerCache.prepareTopLevelObject(ConfigManagerCache.java:362)

at com.sygate.scm.server.configmanager.ConfigManagerCache.getTopLevelObject(ConfigManagerCache.java:275)

at com.sygate.scm.server.configmanager.ConfigManager.getTopLevelObject(ConfigManager.java:348)

at com.sygate.scm.server.configmanager.ConfigManager.getSemConfigRootObject(ConfigManager.java:2098)

at com.sygate.scm.tools.ludbfix.XmlValidator.<init>(XmlValidator.java:120)

at com.sygate.scm.tools.ludbfix.XmlValidator.main(XmlValidator.java:466)

Caused by: java.sql.SQLException: Login failed for user ''. The user is not associated with a trusted SQL Server connection.

at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)

at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)

at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)

at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:610)

at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:345)

at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)

at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)

at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:188)

at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:137)

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.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:913)

... 10 more

com.sygate.scm.server.util.ServerException: Unexpected server error.

at com.sygate.scm.server.configmanager.ConfigManagerCache.prepareTopLevelObject(ConfigManagerCache.java:379)

at com.sygate.scm.server.configmanager.ConfigManagerCache.getTopLevelObject(ConfigManagerCache.java:275)

at com.sygate.scm.server.configmanager.ConfigManager.getTopLevelObject(ConfigManager.java:348)

at com.sygate.scm.server.configmanager.ConfigManager.getSemConfigRootObject(ConfigManager.java:2098)

at com.sygate.scm.tools.ludbfix.XmlValidator.<init>(XmlValidator.java:120)

at com.sygate.scm.tools.ludbfix.XmlValidator.main(XmlValidator.java:466)

Caused by: com.sygate.scm.server.metadata.MetadataException: 

at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:915)

at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:881)

at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:921)

at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:947)

at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:250)

at com.sygate.scm.server.configmanager.ConfigManagerCache.prepareTopLevelObject(ConfigManagerCache.java:362)

... 5 more

Caused by: java.sql.SQLException: Login failed for user ''. The user is not associated with a trusted SQL Server connection.

at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)

at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)

at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)

at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:610)

at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:345)

at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)

at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)

at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:188)

at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:137)

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.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:913)

... 10 more

Non of the admin users are able to login to SEPM console now?

If yes, try this

Resetting the administrator user name and password to admin

If any admin user is able to login try to SEPM console, double check AD authentication configuration.

Many thanks guys for the assistance here.

It was the combination of unknown password and the broken Database schema during the upgrade from v11.0.6005 into v12.1