FIX: The Distribution Agent fails when you perform DML operations in a publication article and a concurrent snapshot is created in SQL Server 2005 or in SQL Server 2008

Article translations Article translations
Article ID: 960571 - View products that this article applies to.
Bug #: 50003722 (SQL Hotfix)
Microsoft distributes Microsoft SQL Server 2005 or SQL Server 2008 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 or SQL Server 2008 fix release.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • In Microsoft SQL Server 2005 or in Microsoft SQL Server 2008, you have a table that contains a computed column.
  • The table has a composite primary key that contains the computed column.
  • You set up a replication, and then add the table as an article to the publication.
In this scenario, when you perform Data Manipulation Language (DML) operations in the article and a concurrent snapshot is created, the Distribution Agent fails. Additionally, error messages that resemble the following appear in the Distribution Agent log:
<DateTime> Parameterized values for above command(s): {{67, 'aaa', '62', 'Test2', 'Mrs', 'F'}}
<DateTime> Agent message code 201. Procedure or function 'sp_MSins_dbo<TableName>_msrepl_ccs' expects parameter '@c7', which was not supplied.
<DateTime> ErrorId = 11, SourceTypeId = 0
ErrorCode = '201'
ErrorText = 'Procedure or function 'sp_MSins_dbo<TableName>_msrepl_ccs' expects parameter '@c7', which was not supplied.'
<DateTime>  Adding alert to msdb..sysreplicationalerts: ErrorId = 11, 
Transaction Seqno = 0000004500000086000500000000, Command ID = 2
Message: Replication-Replication Distribution Subsystem: agent <Distribution Agent> failed. Procedure or function 'sp_MSins_dbo<TableName>_msrepl_ccs' expects parameter '@c7', which was not supplied.ErrorId = 11, SourceTypeId = 1
ErrorCode = ''
ErrorText = 'if @@trancount > 0 rollback tran'
<DateTime> Category:COMMAND
Source: Failed Command
Number: 
Message: if @@trancount > 0 rollback tran
<DateTime> ErrorId = 11, SourceTypeId = 0
ErrorCode = '201'
ErrorText = 'Procedure or function 'sp_MSins_dbo<TableName>_msrepl_ccs' expects parameter '@c7', which was not supplied.'
<DateTime> Category:NULL
Source: Microsoft SQL Native Client
Number: 201
Message: Procedure or function 'sp_MSins_dbo<TableName>_msrepl_ccs' expects parameter '@c7', which was not supplied.
<DateTime> OLE DB Subscriber '<Subscriber>': exec dbo.sp_MSupdatelastsyncinfo N'<publisher>',N'<publish_db>', N'<publication>', 0, 6, N'Procedure or function ''sp_MSins_dbo<TableName>_msrepl_ccs'' expects parameter ''@c7'', which was not supplied.'

CAUSE

In the scenario that the "Symptoms" section describes, when a concurrent DML statement is pending and a snapshot is being created, a specific stored procedure that is named sp_MSins_dbo<TableName>_msrepl_ccs is created to propagate the DML statement. This stored procedure requires the primary key to be passed as a parameter. However, because of a bug, the primary key is not passed if the key contains the computed column. This causes the problem that the "Symptoms" section describes.

RESOLUTION

Cumulative update information

SQL Server 2005 Service Pack 2

Important You must use this fix if you are running SQL Server 2005 Service Pack 2.

The fix for this issue was first released in Cumulative Update 11 for SQL Server 2005 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:
958735 Cumulative update package 11 for SQL Server 2005 Service Pack 2
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 2005 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:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2005 Service Pack 3

Important You must use this fix if you are running SQL Server 2005 Service Pack 3.

The fix for this issue was also later released in Cumulative Update 1 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
959195 Cumulative update package 1 for SQL Server 2005 Service Pack 3
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 2005 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:
960598 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 Service Pack 3. 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

The fix for this issue was first released in Cumulative Update 3. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
960484 Cumulative update package 3 for SQL Server 2008
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:
956909 The SQL Server 2008 builds that were released after SQL Server 2008 was released

STATUS

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

MORE INFORMATION

SQL Server 2005

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
958735 Cumulative update package 11 for SQL Server 2005 Service Pack 2

SQL Server 2008

For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
960484 Cumulative update package 3 for SQL Server 2008

REFERENCES

For more information about the list of builds that are available after SQL Server Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
937137 List of the builds that are available after SQL Server 2005 Service Pack 2 was released
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:
935897 An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
913089 How to obtain the latest service pack for SQL Server 2005
For more information about the new features and the improvements in SQL Server 2005 Service Pack 2, visit the following Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=71711
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:
822499 New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 960571 - Last Review: January 19, 2009 - Revision: 3.0
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Workgroup Edition
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Workgroup
Keywords: 
kbhotfixrollup kbsurveynew kbqfe kbexpertiseadvanced kbfix KB960571

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com