Symptom: When trying to back up, copy, repair, create a remote database, or synchronize a remote database in Act!, I am receiving the Error: "Cannot insert duplicate key row in object 'sys.syscommittab' with unique index 'si_xdes_id'... error 2601"
Product Details:
Product Family: Act!
Product: Act! Pro, Act! Premium
Version: 2012 or later
Environment:
Engine: Microsoft SQL Server 2008 R2, Microsoft SQL Server 2012, Microsoft SQL Server 2014
Third Party: Microsoft
Cause:
This error is caused by a known issue that Microsoft published for Microsoft SQL Server that causes backup and checkpoint operations on Microsoft SQL Server databases to fail due to a duplicate database table row that gets inserted into the back end of the database. This issue can occur in any version of Act! where SQL 2008 is installed. For more information, refer to the following knowledgebase article:
FIX: Backup operation fails in a SQL Server database after you enable change tracking
Solution:
Note: This information is provided as a convenience. Swiftpage does not provide support for Microsoft products or downloads. For assistance with applying these updates, contact Microsoft or an IT Professional.
Follow the instructions below that apply to your version of Microsoft SQL Server. If you are not sure which version of Microsoft SQL Server you are using with Act!, refer to the following knowledgebase for instructions on determining what version you are using:
How do I know what version of Microsoft SQL Server I am using with Act!?
Answer ID How do I know what version of Microsoft SQL Server I am using with Act!?
Microsoft SQL Server 2008 R2
Option 1 - Resolve using Act! Diagnostics (Microsoft SQL Server Express only)
Important Note: If this error is occurring on a database which is part of a remote synchronization environment, these steps need to be performed on the machine where the main database resides, as well as all machines that contain remote databases that synchronize back to the main database. The version of SQL Server should be verified on each machine to make sure the appropriate steps are followed
Act! users who are using Microsoft SQL Server Express can use Act! Diagnostics version 17.1 or later to automatically download and apply the Microsoft SQL Server 2008 R2 Service Pack 1 and CU 6, as well as automatically run a command against the affected database to repair it.
Note: If you have multiple affected databases, repeat these steps for each database to run the command against each affected database
Option 2: Applying Service Pack 3 to Microsoft SQL Server 2008 R2
Important Note: If this error is occurring on a database which is part of a remote synchronization environment, these steps need to be performed on the machine where the main database resides, as well as all machines that contain remote databases that synchronize back to the main database.
Act! users who are using Microsoft SQL Server Standard, or who were unsuccessful in resolving the issue through using Act! diagnostics commands must download and install Microsoft SQL Server 2008 R2 Service Pack 3, then run a batch file. See below for steps:
Note: If you have multiple affected databases, repeat steps 3 - 6 for each database to run the command against each affected database.
Click here only if you receive an error when trying to run the batch file
Microsoft SQL Server 2012, Microsoft SQL Server 2012 SP2, Microsoft SQL Server 2014, Microsoft SQL Server 2014 SP1
Important Note: If this error is occurring on a database which is part of a remote synchronization environment, these steps need to be performed on the machine where the main database resides, as well as all machines that contain remote databases that synchronize back to the main database. The version of SQL Server should be verified on each machine to make sure the appropriate steps are followed
In order to resolve this issue, it is necessary to make sure that your Microsoft SQL Server installation has the latest update applied to it. Once applied, it will be necessary to run one the appropriate batch file. See the steps below:
Note: If you have multiple affected databases, repeat steps 3 - 6 for each database to run the command against each affected database
Click here only if you receive an error when trying to run the batch file
Product Details:
Product Family: Act!
Product: Act! Pro, Act! Premium
Version: 2012 or later
Environment:
Engine: Microsoft SQL Server 2008 R2, Microsoft SQL Server 2012, Microsoft SQL Server 2014
Third Party: Microsoft
Cause:
This error is caused by a known issue that Microsoft published for Microsoft SQL Server that causes backup and checkpoint operations on Microsoft SQL Server databases to fail due to a duplicate database table row that gets inserted into the back end of the database. This issue can occur in any version of Act! where SQL 2008 is installed. For more information, refer to the following knowledgebase article:
FIX: Backup operation fails in a SQL Server database after you enable change tracking
Solution:
Note: This information is provided as a convenience. Swiftpage does not provide support for Microsoft products or downloads. For assistance with applying these updates, contact Microsoft or an IT Professional.
Follow the instructions below that apply to your version of Microsoft SQL Server. If you are not sure which version of Microsoft SQL Server you are using with Act!, refer to the following knowledgebase for instructions on determining what version you are using:
How do I know what version of Microsoft SQL Server I am using with Act!?
Answer ID How do I know what version of Microsoft SQL Server I am using with Act!?

Option 1 - Resolve using Act! Diagnostics (Microsoft SQL Server Express only)
Important Note: If this error is occurring on a database which is part of a remote synchronization environment, these steps need to be performed on the machine where the main database resides, as well as all machines that contain remote databases that synchronize back to the main database. The version of SQL Server should be verified on each machine to make sure the appropriate steps are followed
Act! users who are using Microsoft SQL Server Express can use Act! Diagnostics version 17.1 or later to automatically download and apply the Microsoft SQL Server 2008 R2 Service Pack 1 and CU 6, as well as automatically run a command against the affected database to repair it.
- Close Act! and any other applications which may use SQL Server, if applicable
- Download and save Act_Diagonstics_v17_2.exe from the File Attachments section at the bottom of this article
- Open the Act! Diagnostics v17.2, and click OK on the disclaimer
- Click Databases > Database list
- Select and highlight the affected database, then click Actions > Syscommittab Repair
- When the warning appears to notify you all applications that use SQLServer must be closed, click Yes to begin the update and repair process
- After the status bar and command windows close and Act! Diagnostics reopens, close Act! diagnostics
- Launch Act! and test using the function which was producing the error
Note: If you have multiple affected databases, repeat these steps for each database to run the command against each affected database
Option 2: Applying Service Pack 3 to Microsoft SQL Server 2008 R2
Important Note: If this error is occurring on a database which is part of a remote synchronization environment, these steps need to be performed on the machine where the main database resides, as well as all machines that contain remote databases that synchronize back to the main database.
Act! users who are using Microsoft SQL Server Standard, or who were unsuccessful in resolving the issue through using Act! diagnostics commands must download and install Microsoft SQL Server 2008 R2 Service Pack 3, then run a batch file. See below for steps:
- Close Act!
- Download and install Microsoft SQL Server 2008 R2 Service Pack 3. For information on downloading and installing this service pack, refer to the following Microsoft documentation:
SQL Server 2008 R2 Service Pack 3 release information
- Depending on whether you are using SQL Server Standard or Express, download one of the following files from the File Attachments section of this article at the bottom of the page:
- Microsoft SQL Server Standard: SQL_Standard_BackupFix.bat
- Microsoft SQL Server Express: SQL_Express_BackupFix.bat
- Right-click the downloaded file and select Run as administrator
Note: If you are using Windows XP/Server 2003, simply double click the file to run it.
- When prompted, type the name of the database which is experiencing the error, then press Enter
- Repeat steps 4 and 5 until 0 rows affected displays, waiting approximately 30 seconds between each time the file is run
- Open Act! and test the function which was producing the error
Note: If you have multiple affected databases, repeat steps 3 - 6 for each database to run the command against each affected database.

Note: The information below only applies if you receive an error when attempting to run either of the BackupFix.bat files. If you have not received an error when attempting to run this batch file, this information does not apply to you.
Option 1: Change Location of .Bat File
Option 2: Service SQL Server Browser Not Running
Option 3: Disable User Account Control (UAC) in Windows Vista and later
Option 4: Install from the Windows account that originally installed Microsoft SQL Server
Option 1: Change Location of .Bat File
- Copy the batch file you downloaded from this article.
- Open Windows® Explorer and browse to one of the following directories, depending on your operating system and SQL Server installation:
SQL Server (64-bit version) installed on a 64-bit operating system:
C:\Program Files\Microsoft SQL Server\100\Tools\Binn
SQL Server (32-bit version) installed on a 64-bit operating system:
C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn
SQL Server (32-bit version) installed on a 32-bit operating system:
C:\Program Files\Microsoft SQL Server\100\Tools\Binn - Paste the batch file in the "Binn" folder.
- Double-click the batch file to run it from this location. When prompted, you will type in the name of the database in which you are experiencing the error. If you do not know the name of your database, then open Act! in look in the upper left corner of the screen - the name of your database will be after the Act! product name.
Option 2: Service SQL Server Browser Not Running
- Open Windows Services
- Locate SQL Server Browser
- Right click service; select Start
- Attempt to run bat file
Option 3: Disable User Account Control (UAC) in Windows Vista and later
- Disable UAC. For information about UAC and how to disable it, refer to the following Microsoft documentation:
What are User Account Control Settings
- Double-click the .bat file and try to run it again
Option 4: Install from the Windows account that originally installed Microsoft SQL Server
- Login to the Windows account that was used to install Microsoft SQL Server
- Browse back to the location you put the batch file in in Option 1
- Attempt to run the batch file again

Important Note: If this error is occurring on a database which is part of a remote synchronization environment, these steps need to be performed on the machine where the main database resides, as well as all machines that contain remote databases that synchronize back to the main database. The version of SQL Server should be verified on each machine to make sure the appropriate steps are followed
In order to resolve this issue, it is necessary to make sure that your Microsoft SQL Server installation has the latest update applied to it. Once applied, it will be necessary to run one the appropriate batch file. See the steps below:
- Close Act!
- Download and install the update that applies to the version of Microsoft SQL Server you are using with Act!. To find the appropriate download link, refer to the following Microsoft documentation:
FIX: Backup operation fails in a SQL Server database after you enable change tracking
- Depending on whether you are using SQL Server Standard or Express, download one of the following files from the File Attachments section of this article at the bottom of the page:
- Microsoft SQL Server Standard: SQL_Standard_BackupFix.bat
- Microsoft SQL Server Express: SQL_Express_BackupFix.bat
- Right-click the downloaded file and select Run as administrator
- When prompted, type the name of the database which is experiencing the error, then press Enter
- Repeat steps 4 and 5 until 0 rows affected displays, waiting approximately 30 seconds between each time the file is run
- Open Act! and test the function which was producing the error
Note: If you have multiple affected databases, repeat steps 3 - 6 for each database to run the command against each affected database

Note: The information below only applies if you receive an error when attempting to run either of the BackupFix.bat files. If you have not received an error when attempting to run this batch file, this information does not apply to you.
Option 1: Change Location of .Bat File
Option 2: Service SQL Server Browser Not Running
Option 3: Disable User Account Control (UAC) in Windows Vista and later
Option 4: Install from the Windows account that originally installed Microsoft SQL Server
Option 1: Change Location of .Bat File
- Copy the batch file you downloaded from this article.
- Open Windows® Explorer and browse to one of the following directories, depending on your operating system and SQL Server installation:
SQL Server (64-bit version) installed on a 64-bit operating system:
C:\Program Files\Microsoft SQL Server\100\Tools\Binn
SQL Server (32-bit version) installed on a 64-bit operating system:
C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn
SQL Server (32-bit version) installed on a 32-bit operating system:
C:\Program Files\Microsoft SQL Server\100\Tools\Binn - Paste the batch file in the "Binn" folder.
- Double-click the batch file to run it from this location. When prompted, you will type in the name of the database in which you are experiencing the error. If you do not know the name of your database, then open Act! in look in the upper left corner of the screen - the name of your database will be after the Act! product name.
Option 2: Service SQL Server Browser Not Running
- Open Windows Services
- Locate SQL Server Browser
- Right click service; select Start
- Attempt to run bat file
Option 3: Disable User Account Control (UAC) in Windows Vista and later
- Disable UAC. For information about UAC and how to disable it, refer to the following Microsoft documentation:
What are User Account Control Settings
- Double-click the .bat file and try to run it again
Option 4: Install from the Windows account that originally installed Microsoft SQL Server
- Login to the Windows account that was used to install Microsoft SQL Server
- Browse back to the location you put the batch file in in Option 1
- Attempt to run the batch file again