Endpoint Protection

 View Only
Back to discussions
Expand all | Collapse all

Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema

Migration User

Migration UserOct 25, 2012 09:55 AM

How can I downgrade to 11.0 RU7 ?

  • 1.  Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema

    Posted Oct 25, 2012 09:50 AM

    Hi, I try to upgrade my sep 11.7 MP2 to sep 12.1 RU1 and then to 12.1 RU1 MP1

    when the upgrade wizard run it stops in 3% and then i see the error- upgrade shcema failed.

    The error log:

     

    2012-10-23 11:15:48.673 THREAD 1 SEVERE: ================== Server Environment ===================
    2012-10-23 11:15:48.689 THREAD 1 SEVERE: os.name = Windows Server 2008 R2
    2012-10-23 11:15:48.689 THREAD 1 SEVERE: os.version = 6.1
    2012-10-23 11:15:48.689 THREAD 1 SEVERE: os.arch = x86
    2012-10-23 11:15:48.689 THREAD 1 SEVERE: java.version = 1.6.0_26
    2012-10-23 11:15:48.689 THREAD 1 SEVERE: java.vendor = Sun Microsystems Inc.
    2012-10-23 11:15:48.689 THREAD 1 SEVERE: java.vm.name = Java HotSpot(TM) Client VM
    2012-10-23 11:15:48.689 THREAD 1 SEVERE: java.vm.version = 20.1-b02
    2012-10-23 11:15:48.689 THREAD 1 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jre
    2012-10-23 11:15:48.689 THREAD 1 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
    2012-10-23 11:15:48.689 THREAD 1 SEVERE: java.user = null
    2012-10-23 11:15:48.689 THREAD 1 SEVERE: user.language = en
    2012-10-23 11:15:48.689 THREAD 1 SEVERE: user.country = US
    2012-10-23 11:15:48.689 THREAD 1 SEVERE: scm.server.version = 12.1.1000.157
    2012-10-23 11:15:48.689 THREAD 1 INFO: Main>> Main> Upgrade parameters 
    2012-10-23 11:15:48.689 THREAD 1 INFO: Main>> Main> Upgrade args length = 1
    2012-10-23 11:15:48.689 THREAD 1 INFO: Upgrade args = SQL
    2012-10-23 11:15:48.689 THREAD 1 INFO: Waited for 1 seconds to get info from stdin.
    2012-10-23 11:15:48.689 THREAD 1 INFO: Get string from stdin:username=sa
    2012-10-23 11:15:48.689 THREAD 1 INFO: adminUserID sa
    2012-10-23 11:15:48.689 THREAD 1 INFO: Password is received
    2012-10-23 11:15:48.689 THREAD 1 INFO: Get string from stdin:END_INPUT_FROM_STDIN
    2012-10-23 11:15:48.689 THREAD 1 INFO: Main>> Main> Unable to retrieve the admin password
    2012-10-23 11:15:48.689 THREAD 1 INFO: Main>> Main> Server Home: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
    2012-10-23 11:15:50.095 THREAD 1 INFO: Main>> Main> You are using MSSQL server.
    2012-10-23 11:15:50.517 THREAD 1 INFO: Has valid SAV license
    2012-10-23 11:15:50.517 THREAD 1 INFO: Info>> No SNAC license file in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\license
    2012-10-23 11:15:52.564 THREAD 1 INFO: Main>> executePreLaunchSteps> Config schema format is upgraded from (schema version from db): 11.0.7.0
    2012-10-23 11:15:52.767 THREAD 1 INFO: Saving disaster recovery data to: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Server Private Key Backup\recovery_2012-10-23-11-15-52.zip
    2012-10-23 11:15:52.798 THREAD 1 INFO: Main>> executePreLaunchSteps> DbVersion: 11.0.7.0 schemaVersionFromDB: 11.0.7.0 isSpm51Mr7: false hasOtherOSAgents: false dbcompanySize: 0 dbConnected: true
    2012-10-23 11:15:52.798 THREAD 1 INFO: Main>> checkUpgradeFeasibility> Checking for upgrade feasibility, current schema version = 12.1.1.0, schema version from db = 11.0.7.0
    2012-10-23 11:15:52.814 THREAD 1 INFO: Main>> displayOnlineServerListIfAny> Checking online servers... siteId = A9A36CEF0814041A011A731D92944BC4
    2012-10-23 11:15:52.830 THREAD 1 INFO: SELECT CONTENT FROM SYSTEM_STATE WHERE OWNER = '108DB1990814041A006DAE3B733C49FA'
    2012-10-23 11:15:52.939 THREAD 1 INFO: SYSOUT : Checking onlist status for server SERVERSEP
    2012-10-23 11:15:52.939 THREAD 1 INFO: SYSOUT : Not checking status. offline status detected
    2012-10-23 11:15:52.939 THREAD 1 INFO: SYSOUT : [name=SERVERSEP,id=108DB1990814041A006DAE3B733C49FA] is offline
    2012-10-23 11:15:52.939 THREAD 1 INFO: Main>> displayOnlineServerListIfAny> Checking online servers... exclude local server id = 108DB1990814041A006DAE3B733C49FA
    2012-10-23 11:15:52.939 THREAD 1 INFO: Main>> displayOnlineServerListIfAny> Online servers:[]
    2012-10-23 11:15:52.939 THREAD 1 INFO: Main>> launchMainFrame> Launching the UI
    2012-10-23 11:15:53.298 THREAD 1 INFO: isDefaultWebSite: null
    2012-10-23 11:15:53.298 THREAD 1 INFO: iisPort: 8014
    2012-10-23 11:15:53.298 THREAD 1 INFO: bReplaceIISwithApache: true
    2012-10-23 11:15:53.330 THREAD 1 INFO: isLicenseInstallationValid:  sep.slf =true  OD file=true
    2012-10-23 11:15:57.174 THREAD 21 INFO: scm.webserver.http.port is not found in conf.properties
    2012-10-23 11:15:57.174 THREAD 21 INFO: scm.webserver.https.port is not found in conf.properties
    2012-10-23 11:15:57.174 THREAD 21 INFO: scm.shutdown.port is not found in conf.properties
    2012-10-23 11:15:57.174 THREAD 21 INFO: scm.iis.https.port is not found in conf.properties
    2012-10-23 11:15:57.174 THREAD 21 INFO: scm.iisproxy.http.port is not found in conf.properties
    2012-10-23 11:15:57.174 THREAD 21 INFO: scm.iisproxy.https.port is not found in conf.properties
    2012-10-23 11:15:58.189 THREAD 21 INFO: scm.webserver.http.port is not found in conf.properties
    2012-10-23 11:15:58.189 THREAD 21 INFO: scm.webserver.https.port is not found in conf.properties
    2012-10-23 11:15:58.189 THREAD 21 INFO: scm.shutdown.port is not found in conf.properties
    2012-10-23 11:15:58.189 THREAD 21 INFO: scm.iis.https.port is not found in conf.properties
    2012-10-23 11:15:58.189 THREAD 21 INFO: scm.iisproxy.http.port is not found in conf.properties
    2012-10-23 11:15:58.189 THREAD 21 INFO: scm.iisproxy.https.port is not found in conf.properties
    2012-10-23 11:16:04.127 THREAD 26 INFO: Initializing ...
    2012-10-23 11:16:04.127 THREAD 26 INFO: Executing command - stop semsrv
    2012-10-23 11:16:04.299 THREAD 26 INFO: The Symantec Endpoint Protection Manager service is not started.
    2012-10-23 11:16:04.299 THREAD 26 INFO: 
    2012-10-23 11:16:04.299 THREAD 26 INFO: More help is available by typing NET HELPMSG 3521.
    2012-10-23 11:16:04.299 THREAD 26 INFO: 
    2012-10-23 11:16:04.299 THREAD 26 INFO: Waiting for service termination: semsrv
    2012-10-23 11:16:04.299 THREAD 26 INFO: Checking whether the service is running semsrv
    2012-10-23 11:16:04.549 THREAD 26 INFO: Service is not running.
    2012-10-23 11:16:04.549 THREAD 26 INFO: Executing command - stop semwebsrv
    2012-10-23 11:16:04.643 THREAD 26 INFO: The service name is invalid.
    2012-10-23 11:16:04.643 THREAD 26 INFO: 
    2012-10-23 11:16:04.643 THREAD 26 INFO: More help is available by typing NET HELPMSG 2185.
    2012-10-23 11:16:04.643 THREAD 26 INFO: 
    2012-10-23 11:16:04.643 THREAD 26 INFO: Stop SemSrv done.
    2012-10-23 11:16:04.643 THREAD 26 INFO: Action Start:0
    2012-10-23 11:16:04.643 THREAD 26 INFO: initDataSource 
    2012-10-23 11:16:05.002 THREAD 26 INFO: createODBC: the SQL Server port number:1433
    2012-10-23 11:16:05.252 THREAD 26 INFO: grantSEMUserPrivilege isDBowner true
    2012-10-23 11:16:05.252 THREAD 26 INFO: Config schema format is upgraded from: 11.0.7.0
    2012-10-23 11:16:05.284 THREAD 26 INFO: Max Log File Size from DB: 20000
    2012-10-23 11:16:05.284 THREAD 26 INFO: Upgrade call setUnrestrictedLogFileSize 
    2012-10-23 11:16:05.284 THREAD 26 INFO: setTransactionLogSizeUnrestricted ALTER DATABASE sem5 MODIFY FILE ( NAME = sem5_log1, MAXSIZE = UNLIMITED )
    2012-10-23 11:16:05.315 THREAD 26 INFO: Upgrade call setUnrestrictedLogFileSize done
    2012-10-23 11:16:05.315 THREAD 26 INFO: Upgrade schema started ...
    2012-10-23 11:16:05.330 THREAD 26 INFO: Process SQL script file:MSSQLServerLicense.sql
    2012-10-23 11:16:05.549 THREAD 26 INFO: Process SQL script file:MSSQLServer12000Misc.sql
    2012-10-23 11:16:05.706 THREAD 26 INFO: Process SQL script file:MSSQLServerAmberLicense.sql
    2012-10-23 11:16:05.815 THREAD 26 INFO: Inserted index disabled table names into the database. Table names are SEM_APPLICATION,COMPUTER_APPLICATION
    2012-10-23 11:16:05.846 THREAD 26 INFO: Process SQL script file:MSSQLServerAmberMisc.sql
    2012-10-23 11:16:09.565 THREAD 26 INFO: Process SQL script file:MSSQLServerRU6stoAmber.sql
    2012-10-23 11:16:10.378 THREAD 26 INFO: Process SQL script file:MSSQLServerAmberMiscIndexes.sql
    2012-10-23 11:16:14.144 THREAD 26 INFO: executeDroppingTempTable...temp=AGENT_SECURITY_LOG_INSERT_108DB1990814041A006DAE3B733C49FA, log=AGENT_SECURITY_LOG_1
    2012-10-23 11:16:14.159 THREAD 26 INFO: executeDroppingTempTable...temp=AGENT_TRAFFIC_LOG_INSERT_108DB1990814041A006DAE3B733C49FA, log=AGENT_TRAFFIC_LOG_1
    2012-10-23 11:16:14.159 THREAD 26 INFO: Process SQL script file:MSSQLServerAmberBeta1toAmberBeta2.sql
    2012-10-23 11:16:14.581 THREAD 26 INFO: Upgrade Filter Tables...
    2012-10-23 11:16:14.597 THREAD 26 INFO: FilterTableUpgrader>>doUpgrade: Begin... table=INVENTORYREPORT,col_idx=INVENTORYFILTER_IDX
    2012-10-23 11:16:14.597 THREAD 26 INFO: FilterTableUpgrader>>dropOldPrimaryKey: Begin... table=INVENTORYREPORT, idx_constraint=PK_INVENTORYREPORT
    2012-10-23 11:16:14.597 THREAD 26 INFO: FilterTableUpgrader>>dropOldPrimaryKey, sql=IF EXISTS (SELECT NAME FROM SYSINDEXES WHERE NAME = 'PK_INVENTORYREPORT' ) ALTER TABLE INVENTORYREPORT DROP CONSTRAINT PK_INVENTORYREPORT
    2012-10-23 11:16:14.612 THREAD 26 INFO: FilterTableUpgrader>>dropOldPrimaryKey: End. table=INVENTORYREPORT
    2012-10-23 11:16:14.612 THREAD 26 INFO: FilterTableUpgrader>>checkTable: Begin... table=INVENTORYREPORT
    2012-10-23 11:16:14.612 THREAD 26 INFO: FilterTableUpgrader>>checkTable: End. table=INVENTORYREPORT
    2012-10-23 11:16:14.612 THREAD 26 INFO: FilterTableUpgrader>>delDuplicateFilters: Begin... table=INVENTORYREPORT, idx_del_list=[]
    2012-10-23 11:16:14.612 THREAD 26 INFO: FilterTableUpgrader>>delDuplicateFilters: End. table=INVENTORYREPORT
    2012-10-23 11:16:14.612 THREAD 26 INFO: FilterTableUpgrader>>createNewPrimaryKey: Begin... table=INVENTORYREPORT
    2012-10-23 11:16:14.612 THREAD 26 INFO: FilterTableUpgrader>>createNewPrimaryKey: End. table=INVENTORYREPORT
    2012-10-23 11:16:14.612 THREAD 26 INFO: FilterTableUpgrader>>doUpgrade: End. table=INVENTORYREPORT
    2012-10-23 11:16:14.612 THREAD 26 INFO: FilterTableUpgrader>>doUpgrade: Begin... table=ALERTFILTER,col_idx=ALERTFILTER_IDX
    2012-10-23 11:16:14.612 THREAD 26 INFO: FilterTableUpgrader>>dropOldPrimaryKey: Begin... table=ALERTFILTER, idx_constraint=PK_ALERTFILTER
    2012-10-23 11:16:14.612 THREAD 26 INFO: FilterTableUpgrader>>dropOldPrimaryKey, sql=IF EXISTS (SELECT NAME FROM SYSINDEXES WHERE NAME = 'PK_ALERTFILTER' ) ALTER TABLE ALERTFILTER DROP CONSTRAINT PK_ALERTFILTER
    2012-10-23 11:16:14.628 THREAD 26 INFO: FilterTableUpgrader>>dropOldPrimaryKey: End. table=ALERTFILTER
    2012-10-23 11:16:14.628 THREAD 26 INFO: FilterTableUpgrader>>checkTable: Begin... table=ALERTFILTER
    2012-10-23 11:16:14.628 THREAD 26 INFO: FilterTableUpgrader>>checkTable: End. table=ALERTFILTER
    2012-10-23 11:16:14.628 THREAD 26 INFO: FilterTableUpgrader>>delDuplicateFilters: Begin... table=ALERTFILTER, idx_del_list=[]
    2012-10-23 11:16:14.628 THREAD 26 INFO: FilterTableUpgrader>>delDuplicateFilters: End. table=ALERTFILTER
    2012-10-23 11:16:14.628 THREAD 26 INFO: FilterTableUpgrader>>createNewPrimaryKey: Begin... table=ALERTFILTER
    2012-10-23 11:16:14.628 THREAD 26 INFO: FilterTableUpgrader>>createNewPrimaryKey: End. table=ALERTFILTER
    2012-10-23 11:16:14.628 THREAD 26 INFO: FilterTableUpgrader>>doUpgrade: End. table=ALERTFILTER
    2012-10-23 11:16:14.628 THREAD 26 INFO: FilterTableUpgrader>>doUpgrade: Begin... table=AUDIT_REPORT,col_idx=AUDITFILTER_IDX
    2012-10-23 11:16:14.628 THREAD 26 INFO: FilterTableUpgrader>>dropOldPrimaryKey: Begin... table=AUDIT_REPORT, idx_constraint=PK_AUDITREPORT
    2012-10-23 11:16:14.628 THREAD 26 INFO: FilterTableUpgrader>>dropOldPrimaryKey, sql=IF EXISTS (SELECT NAME FROM SYSINDEXES WHERE NAME = 'PK_AUDITREPORT' ) ALTER TABLE AUDIT_REPORT DROP CONSTRAINT PK_AUDITREPORT
    2012-10-23 11:16:14.659 THREAD 26 INFO: FilterTableUpgrader>>dropOldPrimaryKey: End. table=AUDIT_REPORT
    2012-10-23 11:16:14.659 THREAD 26 INFO: FilterTableUpgrader>>checkTable: Begin... table=AUDIT_REPORT
    2012-10-23 11:16:14.659 THREAD 26 INFO: FilterTableUpgrader>>checkTable: End. table=AUDIT_REPORT
    2012-10-23 11:16:14.659 THREAD 26 INFO: FilterTableUpgrader>>delDuplicateFilters: Begin... table=AUDIT_REPORT, idx_del_list=[]
    2012-10-23 11:16:14.659 THREAD 26 INFO: FilterTableUpgrader>>delDuplicateFilters: End. table=AUDIT_REPORT
    2012-10-23 11:16:14.659 THREAD 26 INFO: FilterTableUpgrader>>createNewPrimaryKey: Begin... table=AUDIT_REPORT
    2012-10-23 11:16:14.659 THREAD 26 INFO: FilterTableUpgrader>>createNewPrimaryKey: End. table=AUDIT_REPORT
    2012-10-23 11:16:14.659 THREAD 26 INFO: FilterTableUpgrader>>doUpgrade: End. table=AUDIT_REPORT
    2012-10-23 11:16:14.659 THREAD 26 INFO: FilterTableUpgrader>>doUpgrade: Begin... table=BEHAVIOR_REPORT,col_idx=BEHAVIORFILTER_IDX
    2012-10-23 11:16:14.659 THREAD 26 INFO: FilterTableUpgrader>>dropOldPrimaryKey: Begin... table=BEHAVIOR_REPORT, idx_constraint=PK_BEHAVIORREPORT
    2012-10-23 11:16:14.659 THREAD 26 INFO: FilterTableUpgrader>>dropOldPrimaryKey, sql=IF EXISTS (SELECT NAME FROM SYSINDEXES WHERE NAME = 'PK_BEHAVIORREPORT' ) ALTER TABLE BEHAVIOR_REPORT DROP CONSTRAINT PK_BEHAVIORREPORT
    2012-10-23 11:16:14.675 THREAD 26 INFO: FilterTableUpgrader>>dropOldPrimaryKey: End. table=BEHAVIOR_REPORT
    2012-10-23 11:16:14.675 THREAD 26 INFO: FilterTableUpgrader>>checkTable: Begin... table=BEHAVIOR_REPORT
    2012-10-23 11:16:14.675 THREAD 26 INFO: FilterTableUpgrader>>checkTable: End. table=BEHAVIOR_REPORT
    2012-10-23 11:16:14.675 THREAD 26 INFO: FilterTableUpgrader>>delDuplicateFilters: Begin... table=BEHAVIOR_REPORT, idx_del_list=[]
    2012-10-23 11:16:14.675 THREAD 26 INFO: FilterTableUpgrader>>delDuplicateFilters: End. table=BEHAVIOR_REPORT
    2012-10-23 11:16:14.675 THREAD 26 INFO: FilterTableUpgrader>>createNewPrimaryKey: Begin... table=BEHAVIOR_REPORT
    2012-10-23 11:16:14.675 THREAD 26 INFO: CovertSQLServerDBNullableColumn, check default constraint sql=SELECT name FROM sysobjects so JOIN sysconstraints sc ON so.id=sc.constid WHERE object_name(so.parent_obj) = 'BEHAVIOR_REPORT' AND so.xtype='D' AND sc.colid = (SELECT colid FROM syscolumns WHERE id=object_id('BEHAVIOR_REPORT') AND name='BEHAVIORTYPE')
    2012-10-23 11:16:14.706 THREAD 26 INFO: CovertSQLServerDBNullableColumn, drop default constraint sql=ALTER TABLE BEHAVIOR_REPORT DROP CONSTRAINT DF__BEHAVIOR___BEHAV__2610A626
    2012-10-23 11:16:14.706 THREAD 26 INFO: CovertSQLServerDBNullableColumn, update default value sql=UPDATE BEHAVIOR_REPORT SET BEHAVIORTYPE=0 WHERE BEHAVIORTYPE IS NULL
    2012-10-23 11:16:14.706 THREAD 26 INFO: CovertSQLServerDBNullableColumn, convert nullable column sql=ALTER TABLE BEHAVIOR_REPORT ALTER COLUMN BEHAVIORTYPE TINYINT NOT NULL
    2012-10-23 11:16:14.706 THREAD 26 INFO: CovertSQLServerDBNullableColumn, set default constraint sql=ALTER TABLE BEHAVIOR_REPORT ADD CONSTRAINT DCONS_BEHAVIOR_REPORT_BEHAVIORTYPE DEFAULT 0 FOR BEHAVIORTYPE
    2012-10-23 11:16:14.722 THREAD 26 INFO: FilterTableUpgrader>>createNewPrimaryKey: End. table=BEHAVIOR_REPORT
    2012-10-23 11:16:14.722 THREAD 26 INFO: FilterTableUpgrader>>doUpgrade: End. table=BEHAVIOR_REPORT
    2012-10-23 11:16:14.722 THREAD 26 INFO: FilterTableUpgrader>>doUpgrade: Begin... table=COMPLIANCE_REPORT,col_idx=COMPLIANCEFILTER_IDX
    2012-10-23 11:16:14.722 THREAD 26 INFO: FilterTableUpgrader>>dropOldPrimaryKey: Begin... table=COMPLIANCE_REPORT, idx_constraint=PK_COMPLIANCEREPORT
    2012-10-23 11:16:14.722 THREAD 26 INFO: FilterTableUpgrader>>dropOldPrimaryKey, sql=IF EXISTS (SELECT NAME FROM SYSINDEXES WHERE NAME = 'PK_COMPLIANCEREPORT' ) ALTER TABLE COMPLIANCE_REPORT DROP CONSTRAINT PK_COMPLIANCEREPORT
    2012-10-23 11:16:14.722 THREAD 26 INFO: FilterTableUpgrader>>dropOldPrimaryKey: End. table=COMPLIANCE_REPORT
    2012-10-23 11:16:14.722 THREAD 26 INFO: FilterTableUpgrader>>checkTable: Begin... table=COMPLIANCE_REPORT
    2012-10-23 11:16:14.722 THREAD 26 INFO: FilterTableUpgrader>>checkTable: End. table=COMPLIANCE_REPORT
    2012-10-23 11:16:14.722 THREAD 26 INFO: FilterTableUpgrader>>delDuplicateFilters: Begin... table=COMPLIANCE_REPORT, idx_del_list=[]
    2012-10-23 11:16:14.722 THREAD 26 INFO: FilterTableUpgrader>>delDuplicateFilters: End. table=COMPLIANCE_REPORT
    2012-10-23 11:16:14.722 THREAD 26 INFO: FilterTableUpgrader>>createNewPrimaryKey: Begin... table=COMPLIANCE_REPORT
    2012-10-23 11:16:14.737 THREAD 26 INFO: CovertSQLServerDBNullableColumn, check default constraint sql=SELECT name FROM sysobjects so JOIN sysconstraints sc ON so.id=sc.constid WHERE object_name(so.parent_obj) = 'COMPLIANCE_REPORT' AND so.xtype='D' AND sc.colid = (SELECT colid FROM syscolumns WHERE id=object_id('COMPLIANCE_REPORT') AND name='COMPLIANCE_TYPE')
    2012-10-23 11:16:14.753 THREAD 26 INFO: CovertSQLServerDBNullableColumn, drop default constraint sql=ALTER TABLE COMPLIANCE_REPORT DROP CONSTRAINT DF__COMPLIANC__COMPL__1D314762
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: java.sql.SQLException: 'DF__COMPLIANC__COMPL__1D314762' is not a constraint.
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at net.sourceforge.jtds.jdbc.JtdsStatement.executeImpl(JtdsStatement.java:723)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at net.sourceforge.jtds.jdbc.JtdsStatement.executeUpdate(JtdsStatement.java:1166)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at net.sourceforge.jtds.jdbc.JtdsStatement.executeUpdate(JtdsStatement.java:1119)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at com.sygate.scm.server.upgrade.FilterTableUpgrader.CovertSQLServerDBNullableColumn(FilterTableUpgrader.java:166)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at com.sygate.scm.server.upgrade.FilterTableUpgrader.createNewPrimaryKey(FilterTableUpgrader.java:113)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at com.sygate.scm.server.upgrade.FilterTableUpgrader.doUpgrade(FilterTableUpgrader.java:57)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at com.sygate.scm.server.upgrade.UpgradeUtil.upgradeFilterTables(UpgradeUtil.java:1823)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at com.sygate.scm.server.upgrade.UpgradeUtil.upgradeFilterTables(UpgradeUtil.java:1765)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at com.sygate.scm.server.db.util.SqlDbHelper.upgrade(SqlDbHelper.java:828)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at com.sygate.scm.server.upgrade.Upgrade.upgradeDatabaseSchema(Upgrade.java:1738)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:484)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:94)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:131)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
    2012-10-23 11:16:15.175 THREAD 26 SEVERE: at java.lang.Thread.run(Thread.java:662)
    2012-10-23 11:16:15.191 THREAD 26 INFO: Upgrade call setBackMaxLogFileSize 
    2012-10-23 11:16:16.050 THREAD 26 INFO: Upgrade call setBackMaxLogFileSize done: 20000
    2012-10-23 11:16:16.050 THREAD 26 SEVERE: java.sql.SQLException: Failed to upgrade schema: java.sql.SQLException: 'DF__COMPLIANC__COMPL__1D314762' is not a constraint.
    2012-10-23 11:16:16.050 THREAD 26 SEVERE: at com.sygate.scm.server.db.util.SqlDbHelper.upgrade(SqlDbHelper.java:859)
    2012-10-23 11:16:16.050 THREAD 26 SEVERE: at com.sygate.scm.server.upgrade.Upgrade.upgradeDatabaseSchema(Upgrade.java:1738)
    2012-10-23 11:16:16.050 THREAD 26 SEVERE: at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:484)
    2012-10-23 11:16:16.050 THREAD 26 SEVERE: at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:94)
    2012-10-23 11:16:16.050 THREAD 26 SEVERE: at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:131)
    2012-10-23 11:16:16.050 THREAD 26 SEVERE: at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
    2012-10-23 11:16:16.050 THREAD 26 SEVERE: at java.lang.Thread.run(Thread.java:662)
    2012-10-23 11:16:16.050 THREAD 26 SEVERE: Upgrade.doUpgrade java.sql.SQLException: Failed to upgrade schema: java.sql.SQLException: 'DF__COMPLIANC__COMPL__1D314762' is not a constraint.
    2012-10-23 11:16:22.675 THREAD 21 INFO: UpgradeFinalPanel >> saveStage > Launching log file...
     


  • 2.  RE: Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema

    Posted Oct 25, 2012 09:53 AM

    See here:

    https://www.symantec.com/business/support/index?page=content&id=TECH174545

    ** Note: Migrations from the Symantec Endpoint Protection 11.x Manager to the 12.1 RU1 Manager are only supported for 11.0 RU7 and earlier. 11.0 RU7 MP1 and 11.0 RU7 MP2 do not contain a supported migration path to 12.1 RU1.

     

    Supported Upgrade paths to Symantec Endpoint Protection 12.1

    https://www.symantec.com/business/support/index?page=content&id=TECH163514



  • 3.  RE: Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema

    Posted Oct 25, 2012 09:55 AM

    How can I downgrade to 11.0 RU7 ?



  • 4.  RE: Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema

    Posted Oct 25, 2012 09:58 AM

    Symantec Endpoint Protection 11.x: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

    https://www.symantec.com/business/support/index?page=content&id=TECH102333

     

     

    Symantec Endpoint Protection 12.1: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

    https://www.symantec.com/business/support/index?page=content&id=TECH160736



  • 5.  RE: Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema

    Posted Oct 25, 2012 10:07 AM

    Hi, is there any additional job to do after restoring MS SQL database. All the setting on SEPM are correct, user name and password to MS SQL database OK, but SEPM's still cannot connect to database.



  • 6.  RE: Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema

    Trusted Advisor
    Posted Oct 25, 2012 10:37 AM

    Hello,

    Migrations from SEPM RU7 MP2 to all current versions of SEPM 12.1 are not supported.

    The 11.0 RU7, RU7 MP1, and RU7 MP2 SEPM contains SQL schema changes that are newer than the schema used by 12.1. For this reason, migrations from certain 11.0 RU7 to 12.1 versions are not supported.

    Future releases of SEPM 12.1 RU2 will contain the migration code necessary to update the newer database schema used by RU7 MP2.

    Symantec Endpoint Protection (SEP) clients can be migrated from RU7 MP2 to SEP 12.1, however, SEP 11 RU7 MP2 managers cannot manage SEP 12.1 clients

    Check this Article:

    Supported migration paths for Symantec Endpoint Protection Manager (SEPM) 11 Release Update 7 Maintenance Patch 2 (RU7 MP2) to SEPM 12.1

    http://www.symantec.com/business/support/index?page=content&id=TECH189972

    Hope that helps!!



  • 7.  RE: Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema

    Trusted Advisor
    Posted Oct 25, 2012 10:42 AM

    Hello,

    Here are the Public Documents available for SEP 12.1.2

    Symantec™ Endpoint Protection and Symantec Network Access Control 12.1.2 Installation and Administration Guide

    https://www.symantec.com/business/support/index?page=content&id=DOC6153

    Symantec™ Endpoint Protection and Symantec Network Access Control 12.1.2 Client Guide

    https://www.symantec.com/business/support/index?page=content&id=DOC3719

    Symantec™ Endpoint Protection 12.1.2 Getting Started Guide

    http://www.symantec.com/docs/DOC4322

    What's new in Symantec Endpoint Protection 12.1.2

    http://www.symantec.com/docs/HOWTO81091

    System Requirements for Symantec Endpoint Protection, Enterprise and Small Business Editions, and Network Access Control 12.1.2

    http://www.symantec.com/docs/TECH195325

    Symantec Endpoint Protection for Macintosh Frequently Asked Questions

    http://www.symantec.com/docs/TECH134203

    Upgrading or migrating to Symantec Endpoint Protection 12.1.2011 (RU2)

    http://www.symantec.com/docs/TECH197426

    Hope that helps!!



  • 8.  RE: Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema

    Posted Oct 25, 2012 12:01 PM

    No those documents do not help. After restoring MS SQL database, SEPM connections to database is lost and we cannot connect to it.

    Configration wizard is set with correct user name and password database port and address. But it still gives error: add server failed after Enter the SQL server name or its IP number

    We are following this guide:

    http://www.symantec.com/business/support/index?page=content&id=TECH134475&locale=en_US



  • 9.  RE: Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema

    Trusted Advisor
    Posted Oct 25, 2012 01:55 PM

    Hello,

    The article being refering above is for SEP 11.x.

    Are you restoring the SEP 11.x database on the SEPM 12.1 ?

    If yes, it is not supported as SEPM RU7 MP2 database schema as different from the SEPM 12.1 database schema.

    Secondly, Migrations from SEPM RU7 MP2 to all current versions of SEPM 12.1 are not supported.

    Check this Article:

    Supported migration paths for Symantec Endpoint Protection Manager (SEPM) 11 Release Update 7 Maintenance Patch 2 (RU7 MP2) to SEPM 12.1

    http://www.symantec.com/business/support/index?page=content&id=TECH189972

    Hope that helps!!



  • 10.  RE: Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema

    Posted Oct 25, 2012 03:23 PM

    After unsuccesful Uppgrade on the other SEPM we did stop the SEPM services on both SEPM's.

    Restored database to earlier SEP 11.x and downgraded manager to SEP 11.x.

    Now the database connection has been almost fixed. SEPM's can connect to database and clients can be searched from groups and client status are changed.

    But on the home page there is error:

    QUERY FAILED:

    This query could not be processed for one of the following reasons:

    1. The database query timed out. Try reducing the number of filters, or increasing the SQL Server query timeout value.

    2. An unexpected error occurred. Try running the query again by using default filter values.

    3. String encoding was possibly not UTF-8, and may result from copying and pasting data instead of typing data. Try typing data in the input fields.
     
    And when opening policies TAB:
    The object type is invalid [0x120a0000]
     

     



  • 11.  RE: Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema

    Posted Oct 25, 2012 03:38 PM

    upload scm0.log located at symante/SEPM/tomcat/logs



  • 12.  RE: Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema

    Posted Oct 25, 2012 04:32 PM

    2012-10-25 21:29:21.441 SEVERE: scm.server.version = 11.0.7000.975
    2012-10-25 21:29:24.086 SEVERE: ================== StartClientTransport ===================
    2012-10-25 21:29:25.035 SEVERE: Schedule is started!
    2012-10-25 21:30:07.017 SEVERE: Unknown Exception in: com.sygate.scm.server.consolemanager.requesthandler.GetRecordHandler
    java.sql.SQLException: Invalid object name 'V_SERVER_SYSTEM_LOG'.
        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.getMoreResults(TdsCore.java:632)
        at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:477)
        at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(JtdsPreparedStatement.java:776)
        at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
        at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
        at com.sygate.scm.server.db.schema.BaseTablePeer.get(BaseTablePeer.java:49)
        at com.sygate.scm.server.consolemanager.requesthandler.GetRecordHandler.handleRequest(GetRecordHandler.java:111)
        at com.sygate.scm.server.consolemanager.RequestHandler.handleRequest(RequestHandler.java:266)
        at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:80)
        at com.sygate.scm.server.servlet.ConsoleServlet.doPost(ConsoleServlet.java:79)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:470)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
        at java.lang.Thread.run(Thread.java:662)
    2012-10-25 21:30:07.900 SEVERE: Unknown Exception in: com.sygate.scm.server.consolemanager.requesthandler.GetRecordHandler
    java.sql.SQLException: Invalid object name 'V_SERVER_SYSTEM_LOG'.
        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.getMoreResults(TdsCore.java:632)
        at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:477)
        at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(JtdsPreparedStatement.java:776)
        at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
        at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
        at com.sygate.scm.server.db.schema.BaseTablePeer.get(BaseTablePeer.java:49)
        at com.sygate.scm.server.consolemanager.requesthandler.GetRecordHandler.handleRequest(GetRecordHandler.java:111)
        at com.sygate.scm.server.consolemanager.RequestHandler.handleRequest(RequestHandler.java:266)
        at com.sygate.scm.server.consolemanager.RequestHandler.<init>(RequestHandler.java:80)
        at com.sygate.scm.server.servlet.ConsoleServlet.doPost(ConsoleServlet.java:79)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:470)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
        at java.lang.Thread.run(Thread.java:662)



  • 13.  RE: Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema

    Posted Oct 30, 2012 05:24 PM

    Hi Meital Magid,

     

    Wait SEP 12.1 RU2 release and you will be able to migrate your SEPM from 11.0 RU7 MP2 to SEP 12.1 RU2.

    Database code used is the same so our customers would finally have the possibility to migrate from RU7 MP2 version to SEP 12.1.2.X

     

    Kind Regards,

    A. Wesker



  • 14.  RE: Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema

    Posted Dec 23, 2012 06:13 AM

    Hi,

    tried to upgeade to 12.1.2

    Still have the same problem with the database schema.

    do you have ant ideas?



  • 15.  RE: Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema

    Trusted Advisor
    Posted Dec 27, 2012 11:33 AM

    Hello,

    Please try this Article:

    Best practices for upgrading to Symantec Endpoint Protection 12.1.2

    http://www.symantec.com/business/support/index?page=content&id=TECH163700

    Hope that helps!!



  • 16.  RE: Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema

    Posted Jan 01, 2013 02:49 PM

    Well... we had this kind of problem earlier - when upgrading SEP11.0.7.x to SEP12 upgrade crash when it start making modifigations to schema (we use SQL db) - at same 3% state.

    We get SQL database back from backups - and try to get SEP11 working again - at this state don't get database working at all.

    After long investigation it shows us that somehow SQL database owner has been changed to wrong schema owner and connection to database is not working as it should be -  so our db admin made same changes to database.

    1) He change all symantec databases to correct (we had user "dbo" who owned schema on database) schema user account running following command using DB admin tools:

    exec sp_MSforeachtable "ALTER SCHEMA dbo TRANSFER ? PRINT '? modified' "

    2)

    After modifiying database schema owner rights - there's still problem with some db view rights.

    - this change's rights to "dbo" view

    (owner_name" must be the user who own view -sight, same who own tables)

     

    select 'execute sp_changeobjectowner '+ '''' + 'owner_name.'+name+''''+','+'''dbo''' from sysobjects where xtype = 'V'

    then he copy generated script and run it against symantec database.

    Databases work again after this.

    Then we try to upgrade SEP again - it goes with no problems (pfffff...)

    (I have to say that - what we had learned - ALLWAYS make sure that you had database backups - and if necessary - make sure you had SQL admin who knows what he does)

     

     



  • 17.  RE: Upgrade from 11.7 MP2 to 12.1 RU 1 failed to upgrade schema
    Best Answer

    Posted Jan 02, 2013 01:42 AM

    Yesterday I'v tried to upgrade again but in other way, after the last upgrade I had problems with logging in to sep and could't manage clients at all, so I installed new server with new database and with silyncdrop.exe moved my 3000 clients to the new sep(12.1.2) so I could finally manage them. with the old sep I did a bit critical move(I wanted to get all the info about clients and policies...)- I had restore of the before and restore of the sql database of before but they where not synced..so I'v uninsulated the old sep(11.7) after a snapshot of course and then installed new 11.7 sep with new database, restored the database from backup and restore wizard and only then I could upgrade- lame way and I know it.

     

    Anyways now i have sep 12.1.2 and I wish the next upgrade with be less painful!!!

     

    Than you all!