02-04-2015 12:19 PM
I'm receiving this error when trying to do complete a back up on a 2008 Server R2 Standard SP1 on Act! Premium 188.8.131.52
The following error occurred during backup. The backup was cancelled.
Cannot insert duplicate key row in object 'sys.syscommittab' with unique index 'si_xdes_id'. The duplicate key value is (5820541). Failed to flush the commit table to disk in dbid 9 due to error 2601.
Check the error log for more information.
BACKUP DATABASE is terminating abnormally.
PRC_MAINT_BACKUPDB: ERROR EXECUTING DATABASE BACKUP STATEMENT
The statement has been terminated.
Any idea? Please Help!
02-06-2015 08:35 AM - edited 02-06-2015 08:36 AM
You can resolve this issue following the instructions below
This is an error associated with Microsoft® SQL Server® 2008 R2. You can resolve this issue by applying Cumulative Update 6 (or later) for SQL Server 2008 R2 Service Pack 1, then running the batch file provided in this article to fix the issue in your database(s). Please close Act! and follow the exact steps below:
Note: The information below is provided as a convenience. Swiftpage does not provide support for Microsoft products and downloads. For further assistance, please see the following KB article on Microsoft.com: 2682488.
Option 1: Download and run the DBFixer available here: http://dlm.act.origin.swiftpage.com/3271/syscommittab_dbfixersilent.exe. This will update your SQL Server 2008 R2 to SP1 CU6 and attempt to fix any database errors caused by this issue. Depending on computer speed, database size, amount of errors, and other factors this might take a long time to finish running.
Option 2: As a temporary fix, run the attached batch file on all databases
Run the batch file for your version of SQL Server found in the File Attachments section of this article to resolve the issue in the databases.
If you are using SQL Server 2008 R2 Express, use SQL2008R2_Express_BackupFix.bat
If you are using SQL Server 2008 R2 Standard, use SQL2008R2_Standard_BackupFix.bat
Click HERE for instructions to determine your version of SQL Server.
Important Note for Remote Database Users:
If you are experiencing this error during remote database synchronization, you will need to run the batch file on all remote databases and the main database. No users should attempt to sync until all databases have successfully run the batch file.
To download and run the file: