Failed Symantec Endpoint Protection Manager upgrade - Error: "Incorrect syntax near '\'"
search cancel

Failed Symantec Endpoint Protection Manager upgrade - Error: "Incorrect syntax near '\'"

book

Article ID: 257421

calendar_today

Updated On:

Products

Endpoint Protection

Issue/Introduction

After upgrading the Symantec Endpoint Protection Manager (SEPM) from 14.3 RUx to 14.3 RUx, the services will not start.

Upgrade-0.log (default location is: C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\logs), contains the following:

2022-12-15 09:53:49.963 THREAD 95 SEVERE: SQL Exception:
2022-12-15 09:53:49.963 THREAD 95 SEVERE: SQL Command:  BEGIN     DECLARE @sql_alter NVARCHAR(MAX)     DECLARE @name_schema VARCHAR(256)     DECLARE @name_table VARCHAR(256)      DECLARE cursor_all_table CURSOR         FOR SELECT schema_name(tab.schema_id), tab.name         FROM sys.tables tab         WHERE NOT EXISTS(             SELECT t.name AS tablename, i.name AS indexname, p.data_compression_desc             FROM sys.tables AS t             INNER JOIN sys.indexes AS i ON t.object_id = i.object_id             INNER JOIN sys.partitions AS p ON i.object_id = p.object_id AND i.index_id = p.index_id             where p.data_compression_desc ='PAGE'             AND T.NAME = TAB.name         )         ORDER BY tab.name      OPEN cursor_all_table;     FETCH NEXT FROM cursor_all_table INTO @name_schema,@name_table     WHILE @@FETCH_STATUS = 0         BEGIN             SELECT @sql_alter = 'ALTER TABLE ' + @name_schema + '.' + @name_table + ' REBUILD PARTITION = ALL WITH (DATA_COMPRESSION = PAGE)'             EXEC SP_EXECUTESQL @sql_alter              FETCH NEXT FROM cursor_all_table INTO @name_schema,@name_table         END      CLOSE cursor_all_table;      DEALLOCATE cursor_all_table; END
2022-12-15 09:53:49.963 THREAD 95 SEVERE: SQLState:  S0001
2022-12-15 09:53:49.963 THREAD 95 SEVERE: Message:  Incorrect syntax near '\'.
2022-12-15 09:53:49.963 THREAD 95 SEVERE: Vendor:  102
2022-12-15 09:53:49.963 THREAD 95 SEVERE: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near '\'.
2022-12-15 09:53:49.963 THREAD 95 SEVERE:     at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:262)
2022-12-15 09:53:49.963 THREAD 95 SEVERE:     at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1632)
2022-12-15 09:53:49.963 THREAD 95 SEVERE:     at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:872)
2022-12-15 09:53:49.963 THREAD 95 SEVERE:     at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:767)
2022-12-15 09:53:49.963 THREAD 95 SEVERE:     at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7375)
2022-12-15 09:53:49.963 THREAD 95 SEVERE:     at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:3206)
2022-12-15 09:53:49.963 THREAD 95 SEVERE:     at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:247)
2022-12-15 09:53:49.963 THREAD 95 SEVERE:     at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:222)
2022-12-15 09:53:49.963 THREAD 95 SEVERE:     at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(SQLServerStatement.java:743)
2022-12-15 09:53:49.963 THREAD 95 SEVERE:     at com.sygate.scm.server.db.util.DatabaseUtilities.execCommandFromScript(DatabaseUtilities.java:2521)
2022-12-15 09:53:49.963 THREAD 95 SEVERE:     at com.sygate.scm.server.db.util.DbUtil.enableDbDataCompression(DbUtil.java:3674)
2022-12-15 09:53:49.963 THREAD 95 SEVERE:     at com.sygate.scm.server.db.util.DbUtil.enableDbDataCompression(DbUtil.java:3633)
2022-12-15 09:53:49.963 THREAD 95 SEVERE:     at com.sygate.scm.server.upgrade.Upgrade.doUpgrade(Upgrade.java:674)
2022-12-15 09:53:49.963 THREAD 95 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeTask.go(UpgradeTask.java:156)
2022-12-15 09:53:49.963 THREAD 95 SEVERE:     at com.sygate.scm.server.upgrade.ui.UpgradeProgressPanel$2.construct(UpgradeProgressPanel.java:249)
2022-12-15 09:53:49.963 THREAD 95 SEVERE:     at com.sygate.scm.util.SwingWorker$2.run(SwingWorker.java:147)
2022-12-15 09:53:49.963 THREAD 95 SEVERE:     at java.base/java.lang.Thread.run(Thread.java:829)
2022-12-15 09:53:49.963 THREAD 95 SEVERE: Upgrade.doUpgrade com.sygate.scm.server.util.ServerException: Unexpected server error.

Environment

14.3 RU2 or later

Cause

An SQL table name or schema used by a table contains a backslash "\".

Resolution

Run the following query to locate the Tables or schemas that contains a backslash

SELECT schema_name(tab.schema_id) 'Schema', tab.name             
FROM sys.tables tab         
WHERE NOT EXISTS(             
SELECT t.name AS tablename, i.name AS indexname, p.data_compression_desc             
FROM sys.tables AS t             
INNER JOIN sys.indexes AS i ON t.object_id = i.object_id             
INNER JOIN sys.partitions AS p ON i.object_id = p.object_id AND i.index_id = p.index_id             
where p.data_compression_desc ='PAGE'             
AND T.NAME = TAB.name         
)          
ORDER BY tab.name 

If the results show a TABLE_NAME that contains a "\"

  • If the table is no longer required (e.g., created for troubleshooting), delete it.
  • If the table is required, contact Symantec Support.

If the results show a TABLE_SCHEMA that contains a "\"

  • Edit the table properties to change the schema to dbo.
Powered by Wolken Software