FIX: Error message when you configure a transactional replication for a database in SQL Server 2008 or in SQL Server 2008 R2

Consider the following scenario in Microsoft SQL Server 2008 or in Microsoft SQL Server 2008 R2:

• You configure a transactional replication for a database.
• The database is configured by using the read_committed_snapshot option.
• The replication is configured to use the native sync_method. Then, the replication subscribers are initialized and a snapshot is generated for the replication.

In this scenario, the distribution agent fails and you may receive one of the following error messages:

• <Date Time> spid<ID> Replication-Replication Distribution
  Subsystem: agent <Agent Name> failed. The row was not found at the Subscriber when applying the replicated command.
• <Date Time> spid<ID> Error: 14151, Severity: 18, State: 1.
  <Date Time> spid<ID> Replication-Replication Distribution
  Subsystem: agent <Agent Name> failed. Violation of PRIMARY KEY constraint '<Primay key name>'. Cannot insert duplicate key in object '<table in subscriber>'.

This issue occurs because a lock is missing when the snapshot is generated for the replication.

Cumulative update information

SQL Server 2008 Service Pack 1

The fix for this issue was first released in Cumulative Update 9 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about SQL Server Replication, visit the following Microsoft Developer Network (MSDN) website: For more information about Snapshot Isolation, visit the following MSDN website: For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base: For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: