05-17-2014 10:53 AM
Got this error when attempting to do a backup.
This page provides how to fix it -- http://kb.swiftpage.com/app/answers/detail/a_id/28141
Step 3 requires the download of SQL2008R2_Express_BackupFix.bat
Where do I find this file - it is not obvious from the instructions where to locate this file.
Can anyone please help?
05-17-2014 01:10 PM
The link to download it is at the bottom of the KB article that you reference in your post.
05-17-2014 02:31 PM
Thank you - found the file and ran it but got this back - not sure what to make of it. I couldnt expand the window to get the full message.
05-17-2014 03:01 PM
The User Account Controls are likely interfering. Right-click and Run as Administrator should solve the problem.
06-10-2014 12:10 PM
The kb article says to run a file to fix this problem.
1. Can anyone tell me what the file does?
2. I assume this file should be run on the server, although it doesn't really say. Since, I'm having a sync problem, it sounds like maybe it should be run on the workstation.
01-20-2015 10:49 AM
I also have ACT 2012 and for whatever reason, when I try to backup my data I get the same error message, Cannot insert duplicate key row in object 'sys.syscommittab' with unique index 'si_xdes_id......Failed to flush the commit table to disk in dbid7 due to error 2601. I read some of the blogs and followed the quick fix instructions, which did not work. Ialso right clicked on as an administrator which still didn't work. I also and even reinstalled the ACT software and still get the same error message. Can anyone help?
01-12-2016 08:02 AM
I had the same problem., just started today and Service Pack 3 is currently installing. Does the machine need to be restarted to complete the update?
01-12-2016 08:08 AM
You don't need to reboot after installing SQL 2008 R2 SP3. You also need to run the macro that was included in the KB article. You won't need to reboot after running the macro either.
01-12-2016 08:56 AM
I had not run the batch file at first. The first time I ran it, it didn't fix it, but the second time it did.
Would anyone please explain why this error occurred all of a sudden. I've been doing weekly backups for several months.