FIX: The row of data on the publisher and the row of data on the subscriber may be inconsistent in a merge publication after synchronization has occurred in SQL Server 2005

This article describes the following about this hotfix release:

• The issues that are fixed by this hotfix package
• The prerequisites for installing the hotfix package
• Whether you must restart the computer after you install the hotfix package
• Whether the hotfix package is replaced by any other hotfix package
• Whether you must make any registry changes
• The files that are contained in the hotfix package

Consider the following scenario:

• A merge publication contains an article.
• A business logic handler for conflict resolution is defined for the article.
• The business logic implements the UpdateConflictsHandler handler.
• The UpdateConflictsHandler handler returns the AcceptCustomConflictData member in the ActionOnUpdateConflict enumeration.
• Updates are applied to the same row of data in the article.
• The updates are applied on the publisher and on the subscriber.

In this scenario, the row of data on the publisher and the row of data on the subscriber may be inconsistent after synchronization has occurred.

During the upload phase, an updated copy of the publisher causes a conflict, and the original copy of the publisher is used to resolve the conflict. However, during the download phase, the customDataSet object is not used to update the subscriber, and the Merge Agent reports no changes. Therefore, the two rows of data are inconsistent.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have SQL Server 2005 Service Pack 1 installed. For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix is not replaced by any other hotfixes.

Registry information

You do not have to change the registry.

File information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

SQL Server 2005, x86-based versions

SQL Server 2005, x64-based versions

SQL Server 2005, Itanium architecture versions

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

For more information about the naming schema for Microsoft 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: