06-11-2013 05:28 PM
Have Sage ACT! Pro 2013 Version 22.214.171.124. Got recent message when starting Office Outlook 2007 did I want to share database. Have never seen screen before.Clicked Yes.
Since that event unable to backup. Get following message:
The following error occurred during backup. Backup Cancelled.
Cannot insert duplicate row key in object ‘sys.syscommittab’ with unique index ‘si_xdes_id’. The duplicate key value is (1094276). Failed to flush the commit table to disk in dbid 8 due to error 2601. Check the error log for more information.
BACKUP DATABASE terminating abnormally.
PRC_MAINT_Backup DB:_ERROR EXECUTING DB BACKUP STATEMENT
The statement has been terminated.
06-12-2013 07:02 AM
Try this kb article.
11-20-2013 02:28 PM
I have this problem too although I have more than one database and it only happens on one of them. If it is an SQL issue, and I only have the free version that shipped with ACT Pro 2013, shouldn't it happen with every database? I'm frankly a little afraid to install a service pack as I really don't know what back end Act is running and Act itself works fine except for back up. The same database also konks the the repair routine.
Am I safe, just copying the database files outside of the program or is that not a complete backup?
11-21-2013 11:28 AM
It looks like the link has moved to
There is also a Microsoft article at
I'm still not sure what to download though as I don't know what verison of SQL 2008 the Act software installed and there appear to be multiple hotfixes.
11-23-2013 10:54 AM
I have not solved the problem. The chaps at ACT (Swiftpage) told me that you have to open the SERVICES.MSC, and stop the ACT SQL from running, then copy the entire database (folder and subfolders) to another location. You have have ACT turned off at this time.
That seems like a pain, but if it ensures that the database is safe, it's worth looking into.
11-23-2013 11:04 AM
This link is good information to a point. For a non-technical person, the steps around the batch file are scary. I called ACT support and they fixed the problem. I followed the tech's verbal steps and, while I have some technical knowledge, I have no idea what we were doing. Bottom line - it worked.