Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

SEPM 12.1.2 Upgrade Error

Created: 23 Jan 2013 | 4 comments

I succesfully upgraded from from SEPM 12.1.1101.401 to 12.1.2015.2015 on 3 management servers and the last failed with a db error.  The system was running with no issues prior to the upgrade and now it's dead in the water, 2008 R2 with current updates.  I've attempted restoring a number of backup dbs but when it comes time to update the schema to 12.1.2 the install immediatly errors out with the following.

Any ideas would be appreciated!

2013-01-23 17:27:04.021 THREAD 1 SEVERE: ================== Server Environment ===================

2013-01-23 17:27:04.021 THREAD 1 SEVERE: os.name = Windows Server 2008 R2
2013-01-23 17:27:04.021 THREAD 1 SEVERE: os.version = 6.1
2013-01-23 17:27:04.021 THREAD 1 SEVERE: os.arch = x64
2013-01-23 17:27:04.021 THREAD 1 SEVERE: java.version = 1.7.0_09
2013-01-23 17:27:04.021 THREAD 1 SEVERE: java.vendor = Oracle Corporation
2013-01-23 17:27:04.021 THREAD 1 SEVERE: java.vm.name = Java HotSpot(TM) Client VM
2013-01-23 17:27:04.021 THREAD 1 SEVERE: java.vm.version = 23.5-b02
2013-01-23 17:27:04.021 THREAD 1 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jre
2013-01-23 17:27:04.021 THREAD 1 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
2013-01-23 17:27:04.021 THREAD 1 SEVERE: java.user = null
2013-01-23 17:27:04.021 THREAD 1 SEVERE: user.language = en
2013-01-23 17:27:04.021 THREAD 1 SEVERE: user.country = US
2013-01-23 17:27:04.021 THREAD 1 SEVERE: scm.server.version = 12.1.2015.2015
2013-01-23 17:27:04.021 THREAD 1 INFO: Main>> Main> Upgrade parameters 
2013-01-23 17:27:04.021 THREAD 1 INFO: Main>> Main> Upgrade args length = 0
2013-01-23 17:27:04.021 THREAD 1 INFO: Main>> Main> Unable to get the command-line arguments
2013-01-23 17:27:04.021 THREAD 1 INFO: Main>> Main> Server Home: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
2013-01-23 17:27:04.428 THREAD 1 INFO: DatabaseUtilities>initDataSource: Found 12.x driver
2013-01-23 17:27:04.428 THREAD 1 INFO: initDatasource dbport:2638
2013-01-23 17:27:04.443 THREAD 1 INFO: Datasource set in sqlanywhere>>ds:sybase.jdbc4.sqlanywhere.ASADataSource@1716e12
2013-01-23 17:27:04.443 THREAD 1 INFO: Checking whether the service is running: SQLANYs_sem5
2013-01-23 17:27:04.443 THREAD 1 INFO: Retrieve status for service SQLANYs_sem5
2013-01-23 17:27:04.521 THREAD 1 INFO: The status for SQLANYs_sem5' service is 1
2013-01-23 17:27:04.553 THREAD 1 INFO: Main>> Main> You are using version 11x embedded db.
2013-01-23 17:27:04.553 THREAD 1 INFO: Main>> executePreLaunchSteps> DbVersion: 12.1.1.1 schemaVersionFromDB: 12.1.1.1 isSpm51Mr7: false hasOtherOSAgents: false dbcompanySize: 1 dbConnected: false
2013-01-23 17:27:04.553 THREAD 1 INFO: Main>> checkUpgradeFeasibility> Checking for upgrade feasibility, current schema version = 12.1.2.2, schema version from db = 12.1.1.1
2013-01-23 17:27:04.568 THREAD 1 INFO: VersionToBeSupported: 12.1.1.1
2013-01-23 17:27:04.568 THREAD 1 INFO: SchemaVersion>> isSupported> versionToBeSupported '12.1.1.1  is supported for this release
2013-01-23 17:27:04.568 THREAD 1 INFO: Main>> launchMainFrame> Launching the UI
2013-01-23 17:27:04.849 THREAD 1 INFO: Has valid SAV license
2013-01-23 17:27:04.849 THREAD 1 INFO: Info>> No SNAC license file in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\license
2013-01-23 17:27:04.928 THREAD 1 INFO: isLicenseInstallationValid:  sep.slf =true  OD file=true
2013-01-23 17:27:22.693 THREAD 14 INFO: scm.server.port is found in conf.properties
2013-01-23 17:27:22.693 THREAD 14 INFO: scm.http.port is found in conf.properties
2013-01-23 17:27:22.693 THREAD 14 INFO: scm.webserver.http.port is found in conf.properties
2013-01-23 17:27:22.693 THREAD 14 INFO: scm.webserver.https.port is not found in conf.properties
2013-01-23 17:27:22.693 THREAD 14 INFO: scm.shutdown.port is found in conf.properties
2013-01-23 17:27:22.693 THREAD 14 INFO: scm.console.reporting.https.port is found in conf.properties
2013-01-23 17:27:22.693 THREAD 14 INFO: scm.webservices.port is found in conf.properties
2013-01-23 17:27:22.693 THREAD 14 INFO: scm.iis.http.port is not found in conf.properties
2013-01-23 17:27:22.693 THREAD 14 INFO: scm.iis.https.port is not found in conf.properties
2013-01-23 17:27:22.693 THREAD 14 INFO: scm.iisproxy.http.port is not found in conf.properties
2013-01-23 17:27:22.693 THREAD 14 INFO: scm.iisproxy.https.port is not found in conf.properties
2013-01-23 17:27:23.740 THREAD 18 INFO: Initializing ...
2013-01-23 17:27:23.740 THREAD 18 INFO: UpgradeStep >> checkUpgradeStatus.
2013-01-23 17:27:23.756 THREAD 18 INFO: Executing command - stop semsrv
2013-01-23 17:27:23.849 THREAD 18 INFO: The Symantec Endpoint Protection Manager service is not started.
2013-01-23 17:27:23.849 THREAD 18 INFO: 
2013-01-23 17:27:23.849 THREAD 18 INFO: More help is available by typing NET HELPMSG 3521.
2013-01-23 17:27:23.849 THREAD 18 INFO: 
2013-01-23 17:27:23.849 THREAD 18 INFO: Waiting for service termination: semsrv
2013-01-23 17:27:23.849 THREAD 18 INFO: Checking whether the service is stopped: semsrv
2013-01-23 17:27:23.849 THREAD 18 INFO: Retrieve status for service semsrv
2013-01-23 17:27:23.928 THREAD 18 INFO: The status for semsrv' service is 1
2013-01-23 17:27:23.928 THREAD 18 INFO: Service is stopped.
2013-01-23 17:27:23.928 THREAD 18 INFO: Executing command - stop semwebsrv
2013-01-23 17:27:24.006 THREAD 18 INFO: The Symantec Endpoint Protection Manager Webserver service is not started.
2013-01-23 17:27:24.006 THREAD 18 INFO: 
2013-01-23 17:27:24.006 THREAD 18 INFO: More help is available by typing NET HELPMSG 3521.
2013-01-23 17:27:24.021 THREAD 18 INFO: 
2013-01-23 17:27:24.021 THREAD 18 INFO: Stop SemSrv done.
2013-01-23 17:27:24.021 THREAD 18 INFO: Action Start:0
2013-01-23 17:27:24.021 THREAD 18 INFO: DatabaseUtilities>initDataSource: Found 12.x driver
2013-01-23 17:27:24.021 THREAD 18 INFO: initDatasource dbport:2638
2013-01-23 17:27:24.021 THREAD 18 INFO: Datasource set in sqlanywhere>>ds:sybase.jdbc4.sqlanywhere.ASADataSource@154052a
2013-01-23 17:27:24.021 THREAD 18 INFO: 11x upgrade Started
2013-01-23 17:27:24.021 THREAD 18 INFO: Upgrade.java>>upgrade 11x_to_12x
2013-01-23 17:27:25.068 THREAD 18 INFO: doUpgrade: Update to latest DB driver.
2013-01-23 17:27:25.068 THREAD 18 INFO: Serverxml>>updateDrivers>Did nt find jdbc parameters in server.xml..trying root.xml
2013-01-23 17:27:25.084 THREAD 18 INFO: Running net stop SQLANYs_sem5......
2013-01-23 17:27:25.162 THREAD 18 INFO: 
2013-01-23 17:27:25.162 THREAD 18 INFO: Executing command - stop SQLANYs_sem5
2013-01-23 17:27:25.256 THREAD 18 INFO: The Symantec Embedded Database service is not started.
2013-01-23 17:27:25.256 THREAD 18 INFO: 
2013-01-23 17:27:25.256 THREAD 18 INFO: More help is available by typing NET HELPMSG 3521.
2013-01-23 17:27:25.256 THREAD 18 INFO: 
2013-01-23 17:27:25.256 THREAD 18 INFO: Waiting for service termination: SQLANYs_sem5
2013-01-23 17:27:25.256 THREAD 18 INFO: Checking whether the service is stopped: SQLANYs_sem5
2013-01-23 17:27:25.256 THREAD 18 INFO: Retrieve status for service SQLANYs_sem5
2013-01-23 17:27:25.334 THREAD 18 INFO: The status for SQLANYs_sem5' service is 1
2013-01-23 17:27:25.334 THREAD 18 INFO: Service is stopped.
2013-01-23 17:27:25.334 THREAD 18 INFO: Running dbsvc.exe -d sem5 -q -y
2013-01-23 17:27:25.396 THREAD 18 INFO: Result of unInstallEmbeddedDBService0
2013-01-23 17:27:25.615 THREAD 18 INFO: SQL Anywhere Service Utility Version 12.0.1.3554Service "sem5" was created successfully.
2013-01-23 17:27:25.615 THREAD 18 INFO: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\bin\ServiceUtil.exe 
2013-01-23 17:27:25.615 THREAD 18 INFO: -service 
2013-01-23 17:27:25.615 THREAD 18 INFO: SQLANYs_sem5 
2013-01-23 17:27:25.615 THREAD 18 INFO: -setservicerecovery 
2013-01-23 17:27:25.615 THREAD 18 INFO: 
2013-01-23 17:27:25.678 THREAD 18 INFO: Service Recovery options for SQLANYs_sem5 have been successfully configured.
2013-01-23 17:27:25.678 THREAD 18 INFO: Result of installEmbeddedDBService:0
2013-01-23 17:27:27.834 THREAD 18 INFO: The Symantec Embedded Database service is starting.The Symantec Embedded Database service was started successfully.
2013-01-23 17:27:27.881 THREAD 18 FINE: connection is null.
2013-01-23 17:27:27.881 THREAD 18 INFO: initDataSource 
2013-01-23 17:27:27.881 THREAD 18 INFO: DatabaseUtilities>initDataSource: Found 12.x driver
2013-01-23 17:27:27.881 THREAD 18 INFO: initDatasource dbport:2638
2013-01-23 17:27:27.881 THREAD 18 INFO: Datasource set in sqlanywhere>>ds:sybase.jdbc4.sqlanywhere.ASADataSource@5197fd
2013-01-23 17:27:27.974 THREAD 18 FINE: isEmbeddedDB:true
2013-01-23 17:27:27.990 THREAD 18 FINE: Borrow connection from pool.
2013-01-23 17:27:28.006 THREAD 18 FINE: Return connection to pool.
2013-01-23 17:27:29.646 THREAD 18 INFO: UpgradeStep >> checkUpgradeStatus.
2013-01-23 17:27:29.646 THREAD 18 INFO: UpgradeStep >> checkUpgradeStatus.
2013-01-23 17:27:29.678 THREAD 18 FINE: Borrow connection from pool.
2013-01-23 17:27:29.678 THREAD 18 FINE: ========== Start transtraction ============
2013-01-23 17:27:31.146 THREAD 18 INFO: Saving disaster recovery data to: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Server Private Key Backup\recovery_2013-01-23-17-27-31.zip
2013-01-23 17:27:31.178 THREAD 18 FINE: ========== Rollback transtraction ============
2013-01-23 17:27:31.193 THREAD 18 FINE: Return connection to pool.
2013-01-23 17:27:31.209 THREAD 18 FINE: Borrow connection from pool.
2013-01-23 17:27:31.209 THREAD 18 FINE: ========== Start transtraction ============
2013-01-23 17:27:31.209 THREAD 18 INFO: updateEmbeddedStatementCount done
2013-01-23 17:27:31.224 THREAD 18 INFO: Config schema format is upgraded from: 12.1.1.1
2013-01-23 17:27:31.224 THREAD 18 INFO: Upgrade schema started ...
2013-01-23 17:27:31.256 THREAD 18 INFO: Process SQL script file:EmbeddedAmberRU1MP1ToJaguarPFC.sql
2013-01-23 17:27:31.256 THREAD 18 INFO: Process SQL InputStream sqlis:sun.net.www.protocol.jar.JarURLConnection$JarURLInputStream@1018010
2013-01-23 17:27:31.256 THREAD 18 INFO: DatabaseUtilities>>execCommandFromScript>>cmdSeperator:;;
2013-01-23 17:27:31.256 THREAD 18 INFO: DatabaseUtilities>>execCommandFromScript>>sqlStr:ALTER TABLE BASIC_METADATA  ALTER DESCRIPTION nvarchar(2048) NULL
2013-01-23 17:27:31.256 THREAD 18 INFO: ALTER TABLE BASIC_METADATA  ALTER DESCRIPTION nvarchar(2048) NULL
2013-01-23 17:27:31.271 THREAD 18 INFO:   IF NOT EXISTS (SELECT TECH_ID FROM DATA_HANDLER WHERE IDX = '966665E10AB4F6D4000ECE6523320426' )  INSERT INTO DATA_HANDLER (IDX, TECH_ID, LF_EXT, LF_SORT, STATE_HANDLER) VALUES ('966665E10AB4F6D4000ECE6523320426', 'ElamMan',  '.dat',       0,   'com.sygate.scm.server.statereader.elam.StateHandler')
2013-01-23 17:27:31.287 THREAD 18 INFO:  IF NOT EXISTS (SELECT C.NAME FROM SYSOBJECTS S, SYSCOLUMNS C          WHERE C.ID = S.ID AND S.NAME = 'SEM_AGENT' AND C.NAME='ELAM_ONOFF')  BEGIN     ALTER TABLE SEM_AGENT ADD ELAM_ONOFF TINYINT NOT NULL DEFAULT 127  END
2013-01-23 17:27:31.615 THREAD 18 SEVERE: SQL Exception:
2013-01-23 17:27:31.615 THREAD 18 SEVERE: SQL Command:  IF NOT EXISTS (SELECT C.NAME FROM SYSOBJECTS S, SYSCOLUMNS C          WHERE C.ID = S.ID AND S.NAME = 'SEM_AGENT' AND C.NAME='ELAM_ONOFF')  BEGIN     ALTER TABLE SEM_AGENT ADD ELAM_ONOFF TINYINT NOT NULL DEFAULT 127  END
2013-01-23 17:27:31.615 THREAD 18 SEVERE: SQLState:  HY000
2013-01-23 17:27:31.615 THREAD 18 SEVERE: Message:  [Sybase][JDBC Driver][SQL Anywhere]Internal database error *** ERROR *** Assertion failed: 200610 (12.0.1.3554)[sem5]
Attempting to normalize a non-continued row (0x29d:0x4) -- transaction rolled back
2013-01-23 17:27:31.615 THREAD 18 SEVERE: Vendor:  -301
2013-01-23 17:27:31.615 THREAD 18 SEVERE: java.sql.SQLException: [Sybase][JDBC Driver][SQL Anywhere]Internal database error *** ERROR *** Assertion failed: 200610 (12.0.1.3554)[sem5]
Attempting to normalize a non-continued row (0x29d:0x4) -- transaction rolled back
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at sybase.jdbc4.sqlanywhere.IIStatement.execute(Native Method)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at sybase.jdbc4.sqlanywhere.IStatement.execute(IStatement.java:309)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.execCommandFromScript(DatabaseUtilities.java:1950)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at com.sygate.scm.server.db.util.DbHelper.execCommandFromScript(DbHelper.java:199)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at com.sygate.scm.server.db.util.EmbededDbHelper.upgrade(EmbededDbHelper.java:284)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at com.sygate.scm.server.upgrade.Upgrade.upgradeDatabaseSchema(Upgrade.java:2031)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:523)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:127)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:138)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at java.lang.Thread.run(Thread.java:722)
2013-01-23 17:27:31.615 THREAD 18 FINE: ========== Rollback transtraction ============
2013-01-23 17:27:31.615 THREAD 18 FINE: Return connection to pool.
2013-01-23 17:27:31.615 THREAD 18 SEVERE: java.sql.SQLException: [Sybase][JDBC Driver][SQL Anywhere]Connection was terminated
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at sybase.jdbc4.sqlanywhere.IConnection.rollback(Native Method)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at com.sygate.scm.server.db.util.EmbededDbHelper.upgrade(EmbededDbHelper.java:306)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at com.sygate.scm.server.upgrade.Upgrade.upgradeDatabaseSchema(Upgrade.java:2031)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:523)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:127)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:138)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: at java.lang.Thread.run(Thread.java:722)
2013-01-23 17:27:31.615 THREAD 18 SEVERE: Upgrade.doUpgrade java.sql.SQLException: [Sybase][JDBC Driver][SQL Anywhere]Connection was terminated
2013-01-23 17:27:37.756 THREAD 14 INFO: UpgradeFinalPanel >> saveStage > Launching log file...
 

Comments 4 CommentsJump to latest comment

.Brian's picture
  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.

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

tavinsv's picture

Thanks Brian, the error occurs when 12.1.2 upgrade is attempting to update the schema.  I've tried running upgrade.bat manually and via the install.

SebastianZ's picture

2013-01-23 17:27:31.615 THREAD 18 SEVERE: Message:  [Sybase][JDBC Driver][SQL Anywhere]Internal database error *** ERROR *** Assertion failed: 200610 (12.0.1.3554)[sem5]

...usually is not a good sign and points to database corruption. Were your 3 SEPMs in replication?

If all attempts to update are failing it may be required to install this 3rd SEPM from scratch without DB import and then reconnect the replication if it was in place.

Have a look at the doc about disater recovery for sep 12.1 (this would apply then without database restore):

http://www.symantec.com/business/support/index?pag...

tavinsv's picture

Thanks for the information. This is the main server and all other servers replicate to it. I've gone back as far as two months of dbs attempting to restore them with the same results. On all previous versions of sepm 12.1 we ran fine with no indication of DB corruption. With 12.1.2 we now need to ditch all the backups and start again?