Endpoint Protection

We're migrating from 11.0.6300 to version 12.1. The installation of SEPM went without errors.

However on launching the db configuration, we got stuck at 3% and also this:

We tested using the port suggested and it proceeded to the next page only to stop again. But the upgrade stopped at 3% and an error SQL Invalid Column Name "IP_ADDR" and we already tried changing the access rights, running the upgrade.bat and also the dbvalidator of SEP 12.

Tried the procedures from this kb and it still did not work:

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

here's some additional screens:

You should raise a case with Symantec Tech Support... don't think your question can be answered here :(

Error No applications are using Tomcat Shutdown's configured port 8005 with a state of 'Listen'.
Error No applications are using Remote Console Logon's configured port 9090 with a state of 'Listen'.
Error No applications are using SqlServer's configured port 1433 with a state of 'Listen'.
Error No applications are using Client Communication's configured port 8014 with a state of 'Listen'.
Error No applications are using Reporting Console's configured port 8445 with a state of 'Listen'.
Error No applications are using Remote Management Console's configured port 8443 with a state of 'Listen'.
Error No applications are using Tomcat shutdown port's configured port 8765 with a state of 'Listen'.

Error Name:  Symantec Endpoint Protection Manager
Type:  Service
Depends on:  AFD Networking Support Environment, TCP/IP Protocol Driver, IPSEC driver
Status Setting Default Actual
Error State Running Stopped
Ok Start Type Auto Start Auto Start
Ok Log On As LocalSystem LocalSystem
Ok Exit Code  The operation completed successfully.

Thanks for the concern Matt.

We've already submitted a case to Symantec. The following threads will be more of an FYI for others who might have the same problems.

check this link

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

The following two options are known to resolve this issue:

• Grant the user performing the upgrade the necessary permissions to write to the SQL database.
• After the upgrade fails, manually launch the upgrade.bat file (located in C:\Program Files\Symantec\Symantec Endpoint Protection Manager\bin by default) as an Administrator

Yup. We also tried that.

Recent update: MS SQL server is stopped for no apparent reason.

Tech support is trying to check with the open ports.

I'm also wondering why the Support tool shows a lot of Tomcat errors.

We also checked the ODBC connection settings. Used to work. But with the SQL agent down. We can't.

from the 1st screen capture it shows the port is listening on 49274, which does not match with one you configured before.

On the sepm server, run the netstat -ab command to check the listening port of sql.

Also pass on the upgrade.log

I got the update log from : C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat\logs\

Here's the entries:

2012-01-27 14:16:33.571 THREAD 1 SEVERE: ================== Server Environment ===================
2012-01-27 14:16:33.572 THREAD 1 SEVERE: os.name = Windows Server 2008 R2
2012-01-27 14:16:33.573 THREAD 1 SEVERE: os.version = 6.1
2012-01-27 14:16:33.573 THREAD 1 SEVERE: os.arch = x86
2012-01-27 14:16:33.573 THREAD 1 SEVERE: java.version = 1.6.0_24
2012-01-27 14:16:33.573 THREAD 1 SEVERE: java.vendor = Sun Microsystems Inc.
2012-01-27 14:16:33.573 THREAD 1 SEVERE: java.vm.name = Java HotSpot(TM) Client VM
2012-01-27 14:16:33.573 THREAD 1 SEVERE: java.vm.version = 19.1-b02

....

2012-01-27 14:16:51.394 THREAD 26 INFO: Stop SemSrv done.
2012-01-27 14:16:51.395 THREAD 26 INFO: Action Start:1
2012-01-27 14:16:51.399 THREAD 26 INFO: initDataSource
2012-01-27 14:16:51.492 THREAD 26 INFO: createODBC: the SQL Server port number:49274
2012-01-27 14:16:51.557 THREAD 26 INFO: grantSEMUserPrivilege isDBowner true
2012-01-27 14:16:51.564 THREAD 26 INFO: Config schema format is upgraded from: 11.0.6.2
2012-01-27 14:16:51.568 THREAD 26 INFO: Max Log File Size from DB: 20000
2012-01-27 14:16:51.568 THREAD 26 INFO: Upgrade call setUnrestrictedLogFileSize
2012-01-27 14:16:51.568 THREAD 26 INFO: setTransactionLogSizeUnrestricted ALTER DATABASE sem5 MODIFY FILE ( NAME = sem5_log1, MAXSIZE = UNLIMITED )
2012-01-27 14:16:51.620 THREAD 26 INFO: Upgrade call setUnrestrictedLogFileSize done
2012-01-27 14:16:51.622 THREAD 26 INFO: Upgrade schema started ...
2012-01-27 14:16:51.633 THREAD 26 INFO: Process SQL script file:MSSQLServerLicense.sql
2012-01-27 14:16:51.664 THREAD 26 INFO: Process SQL script file:MSSQLServer12000Misc.sql
2012-01-27 14:16:51.852 THREAD 26 INFO: Process SQL script file:MSSQLServerAmberLicense.sql
2012-01-27 14:16:51.893 THREAD 26 INFO: Process SQL script file:MSSQLServerAmberMisc.sql
2012-01-27 14:18:16.160 THREAD 26 SEVERE: SQL Exception:

2012-01-27 14:18:16.160 THREAD 26 SEVERE: SQL Command: CREATE VIEW V_AGENT_BEHAVIOR_LOG as     SELECT *,     CAST((case when IP_ADDR < 0 then  0xFFFFFFFF + IP_ADDR else IP_ADDR end / 256 / 256 / 256) & 0xFF as VARCHAR) + '.' +     CAST((case when IP_ADDR < 0 then  0xFFFFFFFF + IP_ADDR else IP_ADDR end / 256 / 256) & 0xFF as VARCHAR) + '.' +     CAST((case when IP_ADDR < 0 then  0xFFFFFFFF + IP_ADDR else IP_ADDR end / 256) & 0xFF as VARCHAR) + '.' +     CAST( case when IP_ADDR < 0 then  0xFFFFFFFF + IP_ADDR else IP_ADDR end & 0xFF as VARCHAR) as IP_ADDR_TEXT FROM AGENT_BEHAVIOR_LOG_1     UNION ALL     SELECT *,     CAST((case when IP_ADDR < 0 then  0xFFFFFFFF + IP_ADDR else IP_ADDR end / 256 / 256 / 256) & 0xFF as VARCHAR) + '.' +     CAST((case when IP_ADDR < 0 then  0xFFFFFFFF + IP_ADDR else IP_ADDR end / 256 / 256) & 0xFF as VARCHAR) + '.' +     CAST((case when IP_ADDR < 0 then  0xFFFFFFFF + IP_ADDR else IP_ADDR end / 256) & 0xFF as VARCHAR) + '.' +     CAST( case when IP_ADDR < 0 then  0xFFFFFFFF + IP_ADDR else IP_ADDR end & 0xFF as VARCHAR) as IP_ADDR_TEXT FROM AGENT_BEHAVIOR_LOG_2
2012-01-27 14:18:16.160 THREAD 26 SEVERE: SQLState:  42S22
2012-01-27 14:18:16.160 THREAD 26 SEVERE: Message:  Invalid column name 'IP_ADDR'.
2012-01-27 14:18:16.160 THREAD 26 SEVERE: Vendor:  207
2012-01-27 14:18:16.161 THREAD 26 SEVERE: java.sql.SQLException: Invalid column name 'IP_ADDR'.

2012-01-27 14:18:16.160 THREAD 26 SEVERE: Vendor:  207
2012-01-27 14:18:16.161 THREAD 26 SEVERE: java.sql.SQLException: Invalid column name 'IP_ADDR'.
2012-01-27 14:18:16.161 THREAD 26 SEVERE:     at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
2012-01-27 14:18:16.161 THREAD 26 SEVERE:     at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
2012-01-27 14:18:16.161 THREAD 26 SEVERE:     at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
2012-01-27 14:18:16.161 THREAD 26 SEVERE:     at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)
2012-01-27 14:18:16.161 THREAD 26 SEVERE:     at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584)
2012-01-27 14:18:16.161 THREAD 26 SEVERE:     at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546)
2012-01-27 14:18:16.161 THREAD 26 SEVERE:     at net.sourceforge.jtds.jdbc.JtdsStatement.executeImpl(JtdsStatement.java:723)
2012-01-27 14:18:16.162 THREAD 26 SEVERE:     at net.sourceforge.jtds.jdbc.JtdsStatement.execute(JtdsStatement.java:1160)
2012-01-27 14:18:16.162 THREAD 26 SEVERE:     at com.sygate.scm.server.db.util.DatabaseUtilities.execCommandFromScript(DatabaseUtilities.java:2032)
2012-01-27 14:18:16.162 THREAD 26 SEVERE:     at com.sygate.scm.server.db.util.DbHelper.execCommandFromScript(DbHelper.java:191)
2012-01-27 14:18:16.162 THREAD 26 SEVERE:     at com.sygate.scm.server.db.util.SqlDbHelper.upgrade(SqlDbHelper.java:735)
2012-01-27 14:18:16.162 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.Upgrade.upgradeDatabaseSchema(Upgrade.java:1573)
2012-01-27 14:18:16.162 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:468)
2012-01-27 14:18:16.162 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:94)
2012-01-27 14:18:16.162 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:131)
2012-01-27 14:18:16.162 THREAD 26 SEVERE:     at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
2012-01-27 14:18:16.163 THREAD 26 SEVERE:     at java.lang.Thread.run(Thread.java:662)
2012-01-27 14:19:22.736 THREAD 26 SEVERE: java.sql.SQLException: java.sql.SQLException: Invalid column name 'IP_ADDR'.
2012-01-27 14:19:22.737 THREAD 26 SEVERE:     at com.sygate.scm.server.db.util.DatabaseUtilities.execCommandFromScript(DatabaseUtilities.java:2042)
2012-01-27 14:19:22.737 THREAD 26 SEVERE:     at com.sygate.scm.server.db.util.DbHelper.execCommandFromScript(DbHelper.java:191)
2012-01-27 14:19:22.737 THREAD 26 SEVERE:     at com.sygate.scm.server.db.util.SqlDbHelper.upgrade(SqlDbHelper.java:735)
2012-01-27 14:19:22.737 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.Upgrade.upgradeDatabaseSchema(Upgrade.java:1573)
2012-01-27 14:19:22.737 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:468)
2012-01-27 14:19:22.738 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:94)
2012-01-27 14:19:22.739 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:131)
2012-01-27 14:19:22.739 THREAD 26 SEVERE:     at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
2012-01-27 14:19:22.739 THREAD 26 SEVERE:     at java.lang.Thread.run(Thread.java:662)
2012-01-27 14:19:22.745 THREAD 26 INFO: Upgrade call setBackMaxLogFileSize
2012-01-27 14:19:27.302 THREAD 26 INFO: Upgrade call setBackMaxLogFileSize done: 20000
2012-01-27 14:19:27.303 THREAD 26 SEVERE: java.sql.SQLException: Failed to upgrade schema: java.sql.SQLException: java.sql.SQLException: Invalid column name 'IP_ADDR'.
2012-01-27 14:19:27.303 THREAD 26 SEVERE:     at com.sygate.scm.server.db.util.SqlDbHelper.upgrade(SqlDbHelper.java:817)
2012-01-27 14:19:27.303 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.Upgrade.upgradeDatabaseSchema(Upgrade.java:1573)
2012-01-27 14:19:27.303 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:468)
2012-01-27 14:19:27.303 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:94)
2012-01-27 14:19:27.303 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:131)
2012-01-27 14:19:27.303 THREAD 26 SEVERE:     at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
2012-01-27 14:19:27.303 THREAD 26 SEVERE:     at java.lang.Thread.run(Thread.java:662)
2012-01-27 14:19:27.303 THREAD 26 SEVERE: Upgrade.doUpgrade java.sql.SQLException: Failed to upgrade schema: java.sql.SQLException: java.sql.SQLException: Invalid column name 'IP_ADDR'.
2012-01-27 14:19:50.927 THREAD 21 INFO: UpgradeFinalPanel >> saveStage > Launching log file...

yes, from logs

 createODBC: the SQL Server port number:49274

was this port configured earlier?

run the upgrade.bat again and try.

Yes, we tried matching the port with that as also suggested in the alert which led us to the migration stuck at 3%. We are currently checking with Sym Support on this and one of the troubleshooting done was to make sure that the original port 1433 is open and listening. And support ran the upgrade.bat via WebEx. Ran it as admin. Seems like a new or different problem that just popped up.

SQLServer server name is:[server_name]\[server_name]
SQLServer host name is=[server_name]  instance name is=[server_name]
SQLServer detected port is=1433
SQLServer detected port is=1433  but user inputted port is=1433
JDBC Driver checked, URL= jdbc:jtds:sqlserver://[server_name]:1433;instance=[server_name] Driver class= net.sourceforge.jtds.jdbc.Driver
getDatabaseConnectionWithNTLMv2Retry isWinAuth : false
getDatabaseConnectionWithNTLMv2Retry trying jdbcURL : jdbc:jtds:sqlserver://[server_name]:1433;instance=[server_name]
Package converting thread >> waiting package loading finished...
Debug Timer: Starting task: method configureDB() at 2012-01-30 16:30:36
Executing command - stop semsrv
The Symantec Endpoint Protection Manager service is not started.

can you please post the new upgrade.log?

reconfiger you SQL database.

2012-01-30 17:42:29.949 THREAD 1 SEVERE: ================== Server Environment ===================
2012-01-30 17:42:29.951 THREAD 1 SEVERE: os.name = Windows Server 2008 R2
2012-01-30 17:42:29.951 THREAD 1 SEVERE: os.version = 6.1
2012-01-30 17:42:29.951 THREAD 1 SEVERE: os.arch = x86
2012-01-30 17:42:29.951 THREAD 1 SEVERE: java.version = 1.6.0_24
2012-01-30 17:42:29.952 THREAD 1 SEVERE: java.vendor = Sun Microsystems Inc.
2012-01-30 17:42:29.952 THREAD 1 SEVERE: java.vm.name = Java HotSpot(TM) Client VM
2012-01-30 17:42:29.952 THREAD 1 SEVERE: java.vm.version = 19.1-b02
2012-01-30 17:42:29.952 THREAD 1 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jre
2012-01-30 17:42:29.952 THREAD 1 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
2012-01-30 17:42:29.952 THREAD 1 SEVERE: java.user = null
2012-01-30 17:42:29.952 THREAD 1 SEVERE: user.language = en
2012-01-30 17:42:29.952 THREAD 1 SEVERE: user.country = PH
2012-01-30 17:42:29.953 THREAD 1 SEVERE: scm.server.version = 12.1.671.4971
2012-01-30 17:42:29.953 THREAD 1 INFO: Main>> Main> Upgrade parameters
2012-01-30 17:42:29.953 THREAD 1 INFO: Main>> Main> Upgrade args length = 0
2012-01-30 17:42:29.953 THREAD 1 INFO: Main>> Main> Server Home: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat
2012-01-30 17:42:31.512 THREAD 1 INFO: Main>> Main> You are using MSSQL server.
2012-01-30 17:42:31.708 THREAD 1 INFO: Has valid SAV license
2012-01-30 17:42:31.708 THREAD 1 INFO: Info>> No SNAC license file in C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\license
2012-01-30 17:42:33.212 THREAD 1 INFO: Main>> executePreLaunchSteps> Config schema format is upgraded from (schema version from db): 11.0.6.2
2012-01-30 17:42:33.295 THREAD 1 INFO: Saving disaster recovery data to: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\..\Server Private Key Backup\recovery_2012-01-30-17-42-33.zip
2012-01-30 17:42:33.337 THREAD 1 INFO: Main>> executePreLaunchSteps> DbVersion: 11.0.6.2 schemaVersionFromDB: 11.0.6.2 isSpm51Mr7: false hasOtherOSAgents: false dbcompanySize: 0 dbConnected: true
2012-01-30 17:42:33.337 THREAD 1 INFO: Main>> checkUpgradeFeasibility> Checking for upgrade feasibility, current schema version = 12.1.0.3, schema version from db = 11.0.6.2
2012-01-30 17:42:33.342 THREAD 1 INFO: Main>> displayOnlineServerListIfAny> Checking online servers... siteId = 21F11A82A9FE5F78019342E77CB1B145
2012-01-30 17:42:33.345 THREAD 1 INFO: SELECT CONTENT FROM SYSTEM_STATE WHERE OWNER = '007489A0A9FE5F78000AC259390D8D62'
2012-01-30 17:42:33.353 THREAD 1 INFO: SYSOUT : Checking onlist status for server SEPMNS4SP
2012-01-30 17:42:33.353 THREAD 1 INFO: SYSOUT : Not checking status. offline status detected
2012-01-30 17:42:33.353 THREAD 1 INFO: SYSOUT : [name=SEPMNS4SP,id=007489A0A9FE5F78000AC259390D8D62] is offline
2012-01-30 17:42:33.353 THREAD 1 INFO: Main>> displayOnlineServerListIfAny> Checking online servers... exclude local server id = 007489A0A9FE5F78000AC259390D8D62
2012-01-30 17:42:33.354 THREAD 1 INFO: Main>> displayOnlineServerListIfAny> Online servers:[]
2012-01-30 17:42:33.354 THREAD 1 INFO: Main>> launchMainFrame> Launching the UI
2012-01-30 17:42:33.541 THREAD 1 INFO: isDefaultWebSite: null
2012-01-30 17:42:33.541 THREAD 1 INFO: iisPort: 8014
2012-01-30 17:42:33.541 THREAD 1 INFO: bReplaceIISwithApache: true
2012-01-30 17:42:33.565 THREAD 1 INFO: isLicenseInstallationValid:  sep.slf =true  OD file=true
2012-01-30 17:42:41.269 THREAD 21 INFO: scm.webserver.http.port is not found in conf.properties
2012-01-30 17:42:41.269 THREAD 21 INFO: scm.webserver.https.port is not found in conf.properties
2012-01-30 17:42:41.269 THREAD 21 INFO: scm.shutdown.port is not found in conf.properties
2012-01-30 17:42:41.269 THREAD 21 INFO: scm.iis.https.port is not found in conf.properties
2012-01-30 17:42:41.269 THREAD 21 INFO: scm.iisproxy.http.port is not found in conf.properties
2012-01-30 17:42:41.269 THREAD 21 INFO: scm.iisproxy.https.port is not found in conf.properties
2012-01-30 17:42:42.271 THREAD 21 INFO: scm.webserver.http.port is not found in conf.properties
2012-01-30 17:42:42.271 THREAD 21 INFO: scm.webserver.https.port is not found in conf.properties
2012-01-30 17:42:42.271 THREAD 21 INFO: scm.shutdown.port is not found in conf.properties
2012-01-30 17:42:42.272 THREAD 21 INFO: scm.iis.https.port is not found in conf.properties
2012-01-30 17:42:42.272 THREAD 21 INFO: scm.iisproxy.http.port is not found in conf.properties
2012-01-30 17:42:42.272 THREAD 21 INFO: scm.iisproxy.https.port is not found in conf.properties
2012-01-30 17:43:03.753 THREAD 26 INFO: Initializing ...
2012-01-30 17:43:03.760 THREAD 26 INFO: Executing command - stop semsrv
2012-01-30 17:43:03.826 THREAD 26 INFO: The Symantec Endpoint Protection Manager service is not started.
2012-01-30 17:43:03.826 THREAD 26 INFO:
2012-01-30 17:43:03.827 THREAD 26 INFO: More help is available by typing NET HELPMSG 3521.
2012-01-30 17:43:03.827 THREAD 26 INFO:
2012-01-30 17:43:03.827 THREAD 26 INFO: Waiting for service termination: semsrv
2012-01-30 17:43:03.827 THREAD 26 INFO: Checking whether the service is running semsrv
2012-01-30 17:43:03.890 THREAD 26 INFO: Service is not running.
2012-01-30 17:43:03.890 THREAD 26 INFO: Executing command - stop semwebsrv
2012-01-30 17:43:03.953 THREAD 26 INFO: The service name is invalid.
2012-01-30 17:43:03.954 THREAD 26 INFO:
2012-01-30 17:43:03.954 THREAD 26 INFO: More help is available by typing NET HELPMSG 2185.
2012-01-30 17:43:03.954 THREAD 26 INFO:
2012-01-30 17:43:03.954 THREAD 26 INFO: Stop SemSrv done.
2012-01-30 17:43:03.954 THREAD 26 INFO: Action Start:0
2012-01-30 17:43:03.959 THREAD 26 INFO: initDataSource
2012-01-30 17:43:04.053 THREAD 26 INFO: createODBC: the SQL Server port number:1433
2012-01-30 17:43:04.114 THREAD 26 INFO: grantSEMUserPrivilege isDBowner true
2012-01-30 17:43:04.121 THREAD 26 INFO: Config schema format is upgraded from: 11.0.6.2
2012-01-30 17:43:04.125 THREAD 26 INFO: Max Log File Size from DB: 20000
2012-01-30 17:43:04.125 THREAD 26 INFO: Upgrade call setUnrestrictedLogFileSize
2012-01-30 17:43:04.125 THREAD 26 INFO: setTransactionLogSizeUnrestricted ALTER DATABASE sem5 MODIFY FILE ( NAME = sem5_log1, MAXSIZE = UNLIMITED )
2012-01-30 17:43:04.165 THREAD 26 INFO: Upgrade call setUnrestrictedLogFileSize done
2012-01-30 17:43:04.167 THREAD 26 INFO: Upgrade schema started ...
2012-01-30 17:43:04.178 THREAD 26 INFO: Process SQL script file:MSSQLServerLicense.sql
2012-01-30 17:43:04.215 THREAD 26 INFO: Process SQL script file:MSSQLServer12000Misc.sql
2012-01-30 17:43:04.406 THREAD 26 INFO: Process SQL script file:MSSQLServerAmberLicense.sql
2012-01-30 17:43:04.448 THREAD 26 INFO: Process SQL script file:MSSQLServerAmberMisc.sql
2012-01-30 17:44:27.812 THREAD 26 SEVERE: SQL Exception:
2012-01-30 17:44:27.812 THREAD 26 SEVERE: SQL Command: CREATE VIEW V_AGENT_BEHAVIOR_LOG as     SELECT *,     CAST((case when IP_ADDR < 0 then  0xFFFFFFFF + IP_ADDR else IP_ADDR end / 256 / 256 / 256) & 0xFF as VARCHAR) + '.' +     CAST((case when IP_ADDR < 0 then  0xFFFFFFFF + IP_ADDR else IP_ADDR end / 256 / 256) & 0xFF as VARCHAR) + '.' +     CAST((case when IP_ADDR < 0 then  0xFFFFFFFF + IP_ADDR else IP_ADDR end / 256) & 0xFF as VARCHAR) + '.' +     CAST( case when IP_ADDR < 0 then  0xFFFFFFFF + IP_ADDR else IP_ADDR end & 0xFF as VARCHAR) as IP_ADDR_TEXT FROM AGENT_BEHAVIOR_LOG_1     UNION ALL     SELECT *,     CAST((case when IP_ADDR < 0 then  0xFFFFFFFF + IP_ADDR else IP_ADDR end / 256 / 256 / 256) & 0xFF as VARCHAR) + '.' +     CAST((case when IP_ADDR < 0 then  0xFFFFFFFF + IP_ADDR else IP_ADDR end / 256 / 256) & 0xFF as VARCHAR) + '.' +     CAST((case when IP_ADDR < 0 then  0xFFFFFFFF + IP_ADDR else IP_ADDR end / 256) & 0xFF as VARCHAR) + '.' +     CAST( case when IP_ADDR < 0 then  0xFFFFFFFF + IP_ADDR else IP_ADDR end & 0xFF as VARCHAR) as IP_ADDR_TEXT FROM AGENT_BEHAVIOR_LOG_2
2012-01-30 17:44:27.812 THREAD 26 SEVERE: SQLState:  42S22
2012-01-30 17:44:27.812 THREAD 26 SEVERE: Message:  Invalid column name 'IP_ADDR'.
2012-01-30 17:44:27.813 THREAD 26 SEVERE: Vendor:  207
2012-01-30 17:44:27.813 THREAD 26 SEVERE: java.sql.SQLException: Invalid column name 'IP_ADDR'.
2012-01-30 17:44:27.813 THREAD 26 SEVERE:     at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
2012-01-30 17:44:27.813 THREAD 26 SEVERE:     at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
2012-01-30 17:44:27.813 THREAD 26 SEVERE:     at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
2012-01-30 17:44:27.813 THREAD 26 SEVERE:     at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)
2012-01-30 17:44:27.813 THREAD 26 SEVERE:     at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584)
2012-01-30 17:44:27.814 THREAD 26 SEVERE:     at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546)
2012-01-30 17:44:27.814 THREAD 26 SEVERE:     at net.sourceforge.jtds.jdbc.JtdsStatement.executeImpl(JtdsStatement.java:723)
2012-01-30 17:44:27.814 THREAD 26 SEVERE:     at net.sourceforge.jtds.jdbc.JtdsStatement.execute(JtdsStatement.java:1160)
2012-01-30 17:44:27.814 THREAD 26 SEVERE:     at com.sygate.scm.server.db.util.DatabaseUtilities.execCommandFromScript(DatabaseUtilities.java:2032)
2012-01-30 17:44:27.814 THREAD 26 SEVERE:     at com.sygate.scm.server.db.util.DbHelper.execCommandFromScript(DbHelper.java:191)
2012-01-30 17:44:27.814 THREAD 26 SEVERE:     at com.sygate.scm.server.db.util.SqlDbHelper.upgrade(SqlDbHelper.java:735)
2012-01-30 17:44:27.814 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.Upgrade.upgradeDatabaseSchema(Upgrade.java:1573)
2012-01-30 17:44:27.814 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:468)
2012-01-30 17:44:27.814 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:94)
2012-01-30 17:44:27.814 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:131)
2012-01-30 17:44:27.815 THREAD 26 SEVERE:     at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
2012-01-30 17:44:27.815 THREAD 26 SEVERE:     at java.lang.Thread.run(Thread.java:662)
2012-01-30 17:45:32.676 THREAD 26 SEVERE: java.sql.SQLException: java.sql.SQLException: Invalid column name 'IP_ADDR'.
2012-01-30 17:45:32.676 THREAD 26 SEVERE:     at com.sygate.scm.server.db.util.DatabaseUtilities.execCommandFromScript(DatabaseUtilities.java:2042)
2012-01-30 17:45:32.676 THREAD 26 SEVERE:     at com.sygate.scm.server.db.util.DbHelper.execCommandFromScript(DbHelper.java:191)
2012-01-30 17:45:32.676 THREAD 26 SEVERE:     at com.sygate.scm.server.db.util.SqlDbHelper.upgrade(SqlDbHelper.java:735)
2012-01-30 17:45:32.676 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.Upgrade.upgradeDatabaseSchema(Upgrade.java:1573)
2012-01-30 17:45:32.676 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:468)
2012-01-30 17:45:32.677 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:94)
2012-01-30 17:45:32.678 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:131)
2012-01-30 17:45:32.678 THREAD 26 SEVERE:     at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
2012-01-30 17:45:32.678 THREAD 26 SEVERE:     at java.lang.Thread.run(Thread.java:662)
2012-01-30 17:45:32.684 THREAD 26 INFO: Upgrade call setBackMaxLogFileSize
2012-01-30 17:45:37.848 THREAD 26 INFO: Upgrade call setBackMaxLogFileSize done: 20000
2012-01-30 17:45:37.848 THREAD 26 SEVERE: java.sql.SQLException: Failed to upgrade schema: java.sql.SQLException: java.sql.SQLException: Invalid column name 'IP_ADDR'.
2012-01-30 17:45:37.849 THREAD 26 SEVERE:     at com.sygate.scm.server.db.util.SqlDbHelper.upgrade(SqlDbHelper.java:817)
2012-01-30 17:45:37.849 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.Upgrade.upgradeDatabaseSchema(Upgrade.java:1573)
2012-01-30 17:45:37.849 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:468)
2012-01-30 17:45:37.849 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:94)
2012-01-30 17:45:37.849 THREAD 26 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:131)
2012-01-30 17:45:37.849 THREAD 26 SEVERE:     at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:145)
2012-01-30 17:45:37.849 THREAD 26 SEVERE:     at java.lang.Thread.run(Thread.java:662)
2012-01-30 17:45:37.849 THREAD 26 SEVERE: Upgrade.doUpgrade java.sql.SQLException: Failed to upgrade schema: java.sql.SQLException: java.sql.SQLException: Invalid column name 'IP_ADDR'.
2012-01-30 17:46:14.108 THREAD 21 INFO: UpgradeFinalPanel >> saveStage > Launching log file...

OS is Windows 2008 and db is MS SQL 2008 R2.

Service packs are applied. No hot fixes.

Check the port on which the SQL database is configured

Regards

can you try steps as highlighted by Sean?

Hi pete,We've already escalated this to Support and we can't perform that DR practice mentioned at the moment while they're troubleshooting for probable causes and solution. I'll update this as soon as there's any progress.

Right now, we're sending some logs to Symantec's backend. This could be a little complicated. :(

Support checked the database. Found 2 to exist. db0 and sem5. I wasn't sure if this was an issue before. This is a replication of a main site and was initially configured as its own site and was then re-configured as a replication of the other one. So, this probably caused the confusion.

Anyway, we're fixing the database so that only one db will be up. And remove the other one which is not in use.

great news! do let community know the steps taken to resolve the issue.

The problem was caused by multiple instances on the database having similar schemas that the installer is having problems in identifying which.

So we uninstalled SEPM, then reinstalled version 11.0.06300 and then restored the database from the backup using DR procedures.

From here, we just migrated it to version 12.1 without any problems.

awesome news, thanks for the update.