The Symantec Endpoint Protection Manager [SEPM] upgrade failed at 3% when the Configuration wizard started upgrading the Database Schema.
Upgrade-0.log
SEM_COMPUTER WHERE DELETED=0
2022-07-01 10:26:23.890 THREAD 41 SEVERE: SQLState: S0001
2022-07-01 10:26:23.890 THREAD 41 SEVERE: Message: There is already an object named 'V_SEM_COMPUTER' in the database.
2022-07-01 10:26:23.890 THREAD 41 SEVERE: Vendor: 2714
2022-07-01 10:26:23.890 THREAD 41 SEVERE: com.microsoft.sqlserver.jdbc.SQLServerException: There is already an object named 'V_SEM_COMPUTER' in the database.
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:262)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1632)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:872)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:767)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7375)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:3206)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:247)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:222)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(SQLServerStatement.java:743)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.sygate.scm.server.db.util.DatabaseUtilities.execCommandFromScript(DatabaseUtilities.java:2508)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.sygate.scm.server.db.util.DbHelper.execCommandFromScript(DbHelper.java:306)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.sygate.scm.server.db.util.SqlDbHelper.upgradeDatabaseSchema(SqlDbHelper.java:1070)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.sygate.scm.server.db.util.SqlDbHelper.upgrade(SqlDbHelper.java:891)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.sygate.scm.server.upgrade.Upgrade.upgradeDatabaseSchema(Upgrade.java:3185)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:653)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:156)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:249)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:151)
2022-07-01 10:26:23.890 THREAD 41 SEVERE: at java.base/java.lang.Thread.run(Thread.java:829)
2022-07-01 10:26:23.890 THREAD 41 WARNING: java.sql.SQLException: com.microsoft.sqlserver.jdbc.SQLServerException: There is already an object named 'V_SEM_COMPUTER' in the database.
at com.sygate.scm.server.db.util.DatabaseUtilities.execCommandFromScript(DatabaseUtilities.java:2533)
at com.sygate.scm.server.db.util.DbHelper.execCommandFromScript(DbHelper.java:306)
at com.sygate.scm.server.db.util.SqlDbHelper.upgradeDatabaseSchema(SqlDbHelper.java:1070)
at com.sygate.scm.server.db.util.SqlDbHelper.upgrade(SqlDbHelper.java:891)
at com.sygate.scm.server.upgrade.Upgrade.upgradeDatabaseSchema(Upgrade.java:3185)
at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:653)
at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:156)
at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:249)
at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:151)
at java.base/java.lang.Thread.run(Thread.java:829)
2022-07-01 10:26:23.906 THREAD 41 FINE: ========== Rollback transtraction ============
2022-07-01 10:26:23.906 THREAD 41 FINE: Rolling back the connection.
2022-07-01 10:26:23.906 THREAD 41 FINE: set autocommit to true on the connection.
Run SQL query "Drop VIEW V_SEM_COMPUTER "
Cannot drop the view 'V_SEM_COMPUTER' because it is being used for replication.
Upgrade SEPM from 14.3 Ru3 to 14.3 Ru5
During the upgrade, the SEPM DB View "V_SEM_COMPUTER" is getting dropped and then gets re-created however the table was not getting deleted because SQL DB replication was enabled.
Follow the below steps:
1. Disabled and removed SQL replication.
2. Run upgrade.bat located at %System%\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\bin