FIX: Merge Replication Non-Convergence Occurs When You Use the "Subscriber Always Wins Conflict Resolver" Option (327651)


The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)
This article was previously published under Q327651
BUG #: 361678 (SHILOH_BUGS)

SYMPTOMS

Under some circumstances, you may find that changes do not replicate properly to some replicas in a merge replication topology, a state known as non-convergence.

Non-convergence can occur if both the following conditions are true:

  • The article that is experiencing non-convergence is configured for column-level conflict detection.

  • The article that is experiencing non-convergence is configured to use the Microsoft SQL Server Subscriber Always Wins Conflict Resolver option.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack


NOTE: The following hotfix was created before the release of Microsoft SQL Server 2000 Service Pack 3.

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft SQL Server 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) 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 tool in Control Panel. 
   Date       Time      Version    Size           File name
   --------------------------------------------------------

   8/7/2002   8:50:42   8.00.676   29 kilobytes   Ssrpub.dll
NOTE: Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.


WORKAROUND

To work around this problem, you can configure problem articles to use row-level conflict tracking. You can request row-level conflict tracking on an article by article basis when you first create the publication. You can also set row-level conflict tracking by modifying the properties of an existing publication; however, this requires all subscriptions to the publication to be reinitialized.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 3.

MORE INFORMATION

You must install this fix to the Publisher, Distributor and Subscribers that are susceptible to the conditions listed in the "Symptoms" section of this article.
Modification Type:MinorLast Reviewed:10/11/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbSQLServ2000preSP3fix kbSQLServ2000sp3fix KB327651
©2004 Microsoft Corporation. All rights reserved.