Video Screencast Help

Problem upgrading from SEPM 12.1 to SEPM 12.1 RU1

Created: 05 Dec 2011 • Updated: 13 Dec 2011 | 20 comments
This issue has been solved. See solution.

I am having problems updating my SEPM 12.1 installation to 12.1 RU1.

We have two sep managers on Windows Server 2008 R2 servers, and an SQL 2008 R2 on a Windows 2008 R2 server.

The service account has a DBO role at the sem5 database. It also has local administrator rights on both SEPM Servers.

Here is a short log of the process:

  1. Backed up sem5 database
  2. Stopped sepm services on both servers
  3. Started setup.exe (run as administrator) on first server
  4. Setup ended on a failure, log files indicate some sort of an SQL error.

We are running on the SEPM Server number 2, the number one does not start anymore. We are safe, but the situation is very inconvenient so I'd appreciate you help here.

 

Here is the setup log error:

2011-12-04 19:58:34.434 THREAD 1 SEVERE: ================== Server Environment ===================
2011-12-04 19:58:34.434 THREAD 1 SEVERE: os.name = Windows Server 2008 R2
2011-12-04 19:58:34.434 THREAD 1 SEVERE: os.version = 6.1
2011-12-04 19:58:34.434 THREAD 1 SEVERE: os.arch = x86
2011-12-04 19:58:34.434 THREAD 1 SEVERE: java.version = 1.6.0_26
2011-12-04 19:58:34.434 THREAD 1 SEVERE: java.vendor = Sun Microsystems Inc.
2011-12-04 19:58:34.434 THREAD 1 SEVERE: java.vm.name = Java HotSpot(TM) Client VM
2011-12-04 19:58:34.434 THREAD 1 SEVERE: java.vm.version = 20.1-b02
2011-12-04 19:58:34.434 THREAD 1 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jre
2011-12-04 19:58:34.434 THREAD 1 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
2011-12-04 19:58:34.434 THREAD 1 SEVERE: java.user = null
2011-12-04 19:58:34.434 THREAD 1 SEVERE: user.language = fi
2011-12-04 19:58:34.434 THREAD 1 SEVERE: user.country = FI
2011-12-04 19:58:34.434 THREAD 1 SEVERE: scm.server.version = 12.1.1000.157
2011-12-04 19:58:34.434 THREAD 1 INFO: Main>> Main> Upgrade parameters
2011-12-04 19:58:34.434 THREAD 1 INFO: Main>> Main> Upgrade args length = 0
2011-12-04 19:58:34.434 THREAD 1 INFO: Main>> Main> Unable to get the command-line arguments
2011-12-04 19:58:34.434 THREAD 1 INFO: Main>> Main> Server Home: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
2011-12-04 19:58:35.966 THREAD 1 INFO: Main>> Main> You are using MSSQL server.
2011-12-04 19:58:36.012 THREAD 1 SEVERE: java.sql.SQLException: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
2011-12-04 19:58:36.012 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
2011-12-04 19:58:36.012 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
2011-12-04 19:58:36.012 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
2011-12-04 19:58:36.012 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:603)
2011-12-04 19:58:36.012 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:345)
2011-12-04 19:58:36.012 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
2011-12-04 19:58:36.012 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)
2011-12-04 19:58:36.012 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:188)
2011-12-04 19:58:36.012 THREAD 1 SEVERE:  at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:137)
2011-12-04 19:58:36.012 THREAD 1 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:522)
2011-12-04 19:58:36.012 THREAD 1 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:419)
2011-12-04 19:58:36.012 THREAD 1 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:404)
2011-12-04 19:58:36.012 THREAD 1 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:394)
2011-12-04 19:58:36.012 THREAD 1 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.testDBConnection(DatabaseUtilities.java:2876)
2011-12-04 19:58:36.012 THREAD 1 SEVERE:  at com.sygate.scm.server.upgrade.ui.Main.<init>(Main.java:221)
2011-12-04 19:58:36.012 THREAD 1 SEVERE:  at com.sygate.scm.server.upgrade.ui.Main.main(Main.java:763)
2011-12-04 19:58:36.012 THREAD 1 INFO: UpgradeDBUtil: testDBConnection: Exception - Can't connect to database.
2011-12-04 19:58:36.012 THREAD 1 INFO: Main>> Main> DB test connection failed. Cannot continue with upgrade tool.
2011-12-04 19:58:36.012 THREAD 1 INFO: Main>> executePreLaunchSteps> DbVersion: 12.1.0.3 schemaVersionFromDB: 12.1.0.3 isSpm51Mr7: false hasOtherOSAgents: false dbcompanySize: 0 dbConnected: false
2011-12-04 19:58:36.012 THREAD 1 INFO: Main>> checkUpgradeFeasibility> Checking for upgrade feasibility, current schema version = 12.1.1.0, schema version from db = 12.1.0.3
2011-12-04 19:58:36.012 THREAD 1 INFO: Main>> launchMainFrame> Launching the UI
2011-12-04 19:58:36.387 THREAD 1 INFO: Has valid SAV license
2011-12-04 19:58:36.387 THREAD 1 INFO: Info>> No SNAC license file in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\license
2011-12-04 19:58:37.231 THREAD 1 INFO: isLicenseInstallationValid:  sep.slf =true  OD file=true
2011-12-04 19:58:39.919 THREAD 25 INFO: Initializing ...
2011-12-04 19:58:39.934 THREAD 25 INFO: Executing command - stop semsrv
2011-12-04 19:58:39.965 THREAD 25 INFO: The Symantec Endpoint Protection Manager service is not started.
2011-12-04 19:58:39.965 THREAD 25 INFO:
2011-12-04 19:58:39.965 THREAD 25 INFO: More help is available by typing NET HELPMSG 3521.
2011-12-04 19:58:39.965 THREAD 25 INFO:
2011-12-04 19:58:39.965 THREAD 25 INFO: Waiting for service termination: semsrv
2011-12-04 19:58:39.965 THREAD 25 INFO: Checking whether the service is running semsrv
2011-12-04 19:58:40.012 THREAD 25 INFO: Service is not running.
2011-12-04 19:58:40.012 THREAD 25 INFO: Executing command - stop semwebsrv
2011-12-04 19:58:40.028 THREAD 25 INFO: The Symantec Endpoint Protection Manager Webserver service is not started.
2011-12-04 19:58:40.028 THREAD 25 INFO:
2011-12-04 19:58:40.028 THREAD 25 INFO: More help is available by typing NET HELPMSG 3521.
2011-12-04 19:58:40.028 THREAD 25 INFO:
2011-12-04 19:58:40.028 THREAD 25 INFO: Stop SemSrv done.
2011-12-04 19:58:40.044 THREAD 25 INFO: Action Start:0
2011-12-04 19:58:40.044 THREAD 25 INFO: initDataSource
2011-12-04 19:58:40.059 THREAD 25 SEVERE: java.sql.SQLException: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:603)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:345)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:188)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:137)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:522)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:419)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:404)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:394)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.testDBConnection(DatabaseUtilities.java:2876)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.initDataSource(DatabaseUtilities.java:2856)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.initDataSource(DatabaseUtilities.java:2686)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:302)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:94)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:131)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
2011-12-04 19:58:40.059 THREAD 25 SEVERE:  at java.lang.Thread.run(Thread.java:662)
2011-12-04 19:58:40.059 THREAD 25 INFO: UpgradeDBUtil: testDBConnection: Exception - Can't connect to database.
2011-12-04 19:58:41.497 THREAD 28 SEVERE: java.io.IOException: Read error
2011-12-04 19:58:41.497 THREAD 28 SEVERE:  at java.io.FileInputStream.readBytes(Native Method)
2011-12-04 19:58:41.497 THREAD 28 SEVERE:  at java.io.FileInputStream.read(FileInputStream.java:220)
2011-12-04 19:58:41.497 THREAD 28 SEVERE:  at com.sygate.scm.util.RunCommandHandler$ReadThread.run(RunCommandHandler.java:200)
2011-12-04 19:58:41.512 THREAD 25 INFO: grantSEMUserPrivilege isDBowner true
2011-12-04 19:58:41.544 THREAD 25 SEVERE: com.sygate.scm.server.metadata.MetadataException:
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:915)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.metadata.MetadataManager.startTransaction(MetadataManager.java:85)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.metadata.MetadataManager.startTransaction(MetadataManager.java:81)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.configmanager.ConfigManager.startTransaction(ConfigManager.java:289)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.upgrade.ui.Main.createRecoveryFile(Main.java:654)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:404)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:94)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:131)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at java.lang.Thread.run(Thread.java:662)
2011-12-04 19:58:41.544 THREAD 25 SEVERE: Caused by: java.sql.SQLException: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:603)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:345)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:188)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:137)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:522)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:419)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:404)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:394)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:913)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  ... 9 more
2011-12-04 19:58:41.544 THREAD 25 SEVERE: com.sygate.scm.server.metadata.MetadataException:
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:915)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.metadata.MetadataManager.startTransaction(MetadataManager.java:85)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.metadata.MetadataManager.startTransaction(MetadataManager.java:81)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.configmanager.ConfigManager.startTransaction(ConfigManager.java:289)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.upgrade.ui.Main.createRecoveryFile(Main.java:654)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:404)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:94)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:131)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at java.lang.Thread.run(Thread.java:662)
2011-12-04 19:58:41.544 THREAD 25 SEVERE: Caused by: java.sql.SQLException: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:603)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:345)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:188)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:137)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:522)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:419)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:404)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:394)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:913)
2011-12-04 19:58:41.544 THREAD 25 SEVERE:  ... 9 more
2011-12-04 19:58:41.559 THREAD 25 SEVERE: com.sygate.scm.server.util.ServerException: Unexpected server error.
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at com.sygate.scm.server.configmanager.ConfigManager.startTransaction(ConfigManager.java:291)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at com.sygate.scm.server.upgrade.ui.Main.createRecoveryFile(Main.java:654)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:404)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:94)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:131)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at java.lang.Thread.run(Thread.java:662)
2011-12-04 19:58:41.559 THREAD 25 SEVERE: Caused by: com.sygate.scm.server.metadata.MetadataException:
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:915)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at com.sygate.scm.server.metadata.MetadataManager.startTransaction(MetadataManager.java:85)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at com.sygate.scm.server.metadata.MetadataManager.startTransaction(MetadataManager.java:81)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at com.sygate.scm.server.configmanager.ConfigManager.startTransaction(ConfigManager.java:289)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  ... 6 more
2011-12-04 19:58:41.559 THREAD 25 SEVERE: Caused by: java.sql.SQLException: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.TdsCore.login(TdsCore.java:603)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:345)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:188)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at net.sourceforge.jtds.jdbcx.JtdsDataSource.getConnection(JtdsDataSource.java:137)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:522)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:419)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:404)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:394)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:913)
2011-12-04 19:58:41.559 THREAD 25 SEVERE:  ... 9 more
2011-12-04 19:58:41.559 THREAD 25 SEVERE: Upgrade.doUpgrade com.sygate.scm.server.util.ServerException: Unexpected server error.
2011-12-04 19:58:47.981 THREAD 16 INFO: UpgradeFinalPanel >> saveStage > Launching log file...

 

It seems that setup did not update the Schema of Database, but updated the files on the sepm server. Here is the error message when trying to start SEPM Console:

2011-12-04 20:00:03.790 THREAD 1 SEVERE: ================== Server Environment ===================
2011-12-04 20:00:03.790 THREAD 1 SEVERE: os.name = Windows Server 2008 R2
2011-12-04 20:00:03.790 THREAD 1 SEVERE: os.version = 6.1
2011-12-04 20:00:03.790 THREAD 1 SEVERE: os.arch = x86
2011-12-04 20:00:03.790 THREAD 1 SEVERE: java.version = 1.6.0_26
2011-12-04 20:00:03.790 THREAD 1 SEVERE: java.vendor = Sun Microsystems Inc.
2011-12-04 20:00:03.790 THREAD 1 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
2011-12-04 20:00:03.790 THREAD 1 SEVERE: java.vm.version = 20.1-b02
2011-12-04 20:00:03.790 THREAD 1 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jre
2011-12-04 20:00:03.790 THREAD 1 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
2011-12-04 20:00:03.790 THREAD 1 SEVERE: java.user = null
2011-12-04 20:00:03.790 THREAD 1 SEVERE: user.language = fi
2011-12-04 20:00:03.790 THREAD 1 SEVERE: user.country = FI
2011-12-04 20:00:03.790 THREAD 1 SEVERE: scm.server.version = 12.1.1000.157
2011-12-04 20:00:05.899 THREAD 1 SEVERE: The server schema is higher than the database schema. The server will now exit. Run the upgrade wizard to synchronize the schemas.
2011-12-04 20:00:05.946 THREAD 1 SEVERE:  in: com.sygate.scm.server.servlet.StartupServlet
com.sygate.scm.server.util.ScmServerError: The server schema is higher than the database schema. The server will now exit. Run the upgrade wizard to synchronize the schemas.
 at com.sygate.scm.server.servlet.StartupServlet.verifySchemaVersion(StartupServlet.java:491)
 at com.sygate.scm.server.servlet.StartupServlet.registerServer(StartupServlet.java:357)
 at com.sygate.scm.server.servlet.StartupServlet.init(StartupServlet.java:137)
 at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173)
 at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
 at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4420)
 at org.apache.catalina.core.StandardContext.start(StandardContext.java:4733)
 at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
 at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:675)
 at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:601)
 at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
 at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1315)
 at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
 at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1061)
 at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
 at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
 at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
 at org.apache.catalina.core.StandardService.start(StandardService.java:525)
 at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
 at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
 at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
 

Comments 20 CommentsJump to latest comment

Mithun Sanghavi's picture

Hello,

Upon checking the Logs, we found as following

2011-12-04 19:58:36.012 THREAD 1 SEVERE: java.sql.SQLException: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

2011-12-04 20:00:05.899 THREAD 1 SEVERE: The server schema is higher than the database schema. The server will now exit. Run the upgrade wizard to synchronize the schemas.

Here are few Suggestions,

  1. Run the upgrade wizard located: 'C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\upgrade.bat'
  2. Run the Management Server Configuration Wizard again to complete the migration process.

Also, Have a looked at this KB. Do you missed something?

Best Practices guide for Installing the Symantec Endpoint Protection Manager 11 RU5 with a SQL Server 2008 Database

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

abhishek8866's picture

Hello,

Thumbs up to mithun.

  1. Run the upgrade wizard located: 'C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin\upgrade.bat'
  2. Run the Management Server Configuration Wizard again to complete the migration process.
Chetan Savade's picture

Hi,

Log says "2011-12-04 20:00:05.899 THREAD 1 SEVERE: The server schema is higher than the database schema. The server will now exit. Run the upgrade wizard to synchronize the schemas"

After running Upgrade.bat it should work fine.

You will find at C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\bin\upgrade.bat'

OR at custom install drive.

I hope it will help you !!!

Chetan Savade
Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

Simpson Homer's picture

Agree with Chetan, Running upgrade.bat would help.

Kedarnath Lal's picture

i agree with Mithun and chetan.

they are correct.

Go with upgrade.bat or Run a Repair the SEPM.

Pekka K.'s picture

Upgrade.bat sounds like a solution, I'll try it asap. I'll let you know what happens!

Thanks in advance!

Pekka K.'s picture

The upgrade.bat is actually the same SEPM wizard that is run by the setup.exe, and still doesn't work. Obviously, it gives the same error message.

Pete, we don't accept NTLM below versio 2, but SEP 12.1 seems to support NTLMv2 according to the article you pointed out: "Migrating/installing Symantec Endpoint Protection Manager 12.1 will completely mitigate this issue as NTLMv2 support has been added to this version."

The SQL Configuration has been working since last summer when we installed SEP 12.1, the problem occurs only now when upgrading to RU1.

I checked out the SQL Server's Windows Security log, the logon succeeded.

Is there a script that would only upgrade the database, or do you have other suggestions?

pete_4u2002's picture

the SEPM will upgrade the DB schema, there is no script as such.DO you still see the same error message?

pete_4u2002's picture

do you use any special character in SQL password, if yes can you reset to normal and check?

Pekka K.'s picture

I did some additional testing.

  • Logged on to SEPM server using SEPM Service Account (a domain account)
  • opened SQL Management Studio
  • connected to the SQL Server
  • Created a backup.

So the SQL security seems to be sufficient.

Our SQL guy noticed an error message from the faulting SEPM Server on out SQL 2008 R2 Server:

SSPI handshake failed with error code 0x80090302, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure.

Pekka K.'s picture

How could I change the service account to use SQL Authentication? Please remember that I am not able to start SEPM.

Simpson Homer's picture

You can consult your DBA for the same and use SA authentication, Also when you use Windows Authentication, are using it in the following manner?

domain/admin as the user name and then the password?

Pekka K.'s picture

Creating the account for SQL Authentication is not the problem, but how do I tell SEPM to use that account, since I am not able to start SEPM? Now we are using a Windows domain account DOMAIN\svcAccount.

Pekka K.'s picture

Management Server Configuration Wizard allows the SQL account reconfiguration.

It is a pitty that our SQL Server supports Windows Authentication Only. To change that needs an SQL Server reconfiguration and cannot be taken place on the middle of the day.

I'll let you know what happens.

Simpson Homer's picture

This is just a part of troubleshooting. We would wait for your response.

Pekka K.'s picture

RU1 upgrade worked! It seems that NTLMv2 isn't supported after all at RU1 upgrade at least, older versions are denied by Group Policy in our domain. It is funny, that SQL Windows Authentication worked until RU1 update with 12.1.

I don't know if it was Tom Petty and Free Fallin' that made the upgrade finally work, or pete_4u2002's advice. Both happening at the same time.. well you can guess.

The starting situation: At this point I had already ran once RU1 and failed on SEPM1 server. The SEPM1 has 12.1 RU1 files but DB has old 12.1 schema. SEPM2 is running 12.1 files and SQL has 12.1 schema.

We changed SQL Server to mixed mode.

Stopped SEPM Service on both SEPM Servers.

Started Management Server Configuration Wizard on the previously failed SEPM1 server:

  • Reconfigure Management Server
  • Accepted other defaults which were given at the original installation
  • Changed Authentication Type from Windows Authentication to SQL authentication
  • Gave new Database user name (SQL account) and password
  • Wizard noticed that the schema is too old, and started the RU1 upgrade wizard (!)
  • Wizard completed succesfully
  • Tested SEPM1 UI succesfully
  • OK!

Started Management Server Configuration Wizard on the previously working SEPM2 server:

  • Reconfigure Management Server
  • Accepted other defaults which were given at the original installation
  • Changed Authentication Type from Windows Authentication to SQL authentication
  • Gave new Database user name (SQL account) and password
  • Wizard noticed that the schema is too NEW, and FAILED

That was kinda expected, must run upgrade wizard now, which is expected to fail due to DB problems:

  • Next
  • Setup.exe Upgrade wizard complained about pending reboots.
  • Changed Symantec Endpoint Manager service to manual and rebooted.
  • After reboot, changed Symantec Endpoint Manager service to automatic
  • Started setup.exe
  • Failed to the DB Wizard (obviously, since DB account is using Windows authentication - must change that)

Started Management Server Configuration Wizard again on SEPM2 server:

  • Reconfigure Management Server
  • Accepted other defaults which were given at the original installation
  • Changed Authentication Type from Windows Authentication to SQL authentication
  • Gave new Database user name (SQL account) and password
  • (No need for DB wizard again)
  • Tested SEPM2 UI succesfully
  • OK!

Created new 64 bit client packages and updated server clients. Done! Thanks to everyone for help, especially pete_4u2002!

I Won't Back Down ;-)

SOLUTION