FIX: Conflicts are not logged when you use the Microsoft SQL Server Subscriber Always Wins Conflict Resolver for an article in a merge replication in Microsoft SQL Server 2005

Article translations Article translations
Article ID: 944677 - View products that this article applies to.
Bug: #50001986 (SQL Hotfix)
Notice
Microsoft distributes Microsoft SQL Server 2005 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 fix release.
Expand all | Collapse all

On This Page

SUMMARY

This article describes the following about this hotfix release:
  • The issues that are fixed by the 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

SYMPTOMS

Consider the following scenario. You configure a merge replication in SQL Server 2005. You add an article to the publication. You specify the article to use the Microsoft SQL Server Subscriber Always Wins Conflict Resolver. When you make some changes to the article on a subscriber, those changes may be undone during later synchronizations. However, you cannot find any conflict in Replication Monitor or in the conflict table.

CAUSE

This issue occurs because the conflict is not logged in Replication Monitor or in the conflict table. SQL Server does not log a conflict when the last change is not made on the publisher. For example, if two subscribers update the same row while they are offline, the first subscriber successfully uploads the change to the publisher. When the second subscriber uploads the change to the publisher, SQL Server detects a conflict. However, SQL Server does not log the conflict because last change is not made on the publisher when you use Microsoft SQL Server Subscriber Always Wins Conflict Resolver.

RESOLUTION

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:
http://support.microsoft.com/contactus/?ws=support
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

  • SQL Server 2005 Service Pack 2

    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

Restart information

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

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of 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 32-bit version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Bcp.exe2005.90.3206.068,63202-Nov-200722:32x86
Chsbrkr.dll12.0.7822.01,684,84022-Jun-200709:22x86
Chtbrkr.dll12.0.7822.06,112,61622-Jun-200709:22x86
Databasemailprotocols.dll9.0.3206.046,10402-Nov-200722:32x86
Distrib.exe2005.90.3206.070,68002-Nov-200722:32x86
Dts.dll2005.90.3206.01,102,36002-Nov-200722:32x86
Dtsconn.dll2005.90.3206.0250,39202-Nov-200722:32x86
Dtspipeline.dll2005.90.3206.0605,20802-Nov-200722:32x86
Fteref.dll12.0.7822.0446,46422-Jun-200709:22x86
Infosoft.dll12.0.7822.0468,32822-Jun-200709:22x86
Instorcl.sqlNot applicable153,77924-Oct-200713:43Not applicable
Korwbrkr.dll12.0.7822.071,01622-Jun-200709:22x86
Langwrbk.dll12.0.7822.0136,55222-Jun-200709:22x86
Mergetxt.dll2005.90.3206.032,28002-Nov-200722:32x86
Microsoft.analysisservices.dll9.0.3206.01,217,56002-Nov-200722:32x86
Microsoft.sqlserver.connectioninfo.dll9.0.3206.0156,69602-Nov-200722:32x86
Microsoft.sqlserver.dtstransferprovider.dll9.0.3206.0115,73602-Nov-200722:32x86
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3206.0295,96002-Nov-200722:32x86
Microsoft.sqlserver.replication.dll2005.90.3206.01,627,16002-Nov-200722:32x86
Microsoft.sqlserver.servicebrokerenum.dll9.0.3206.042,00802-Nov-200722:32x86
Microsoft.sqlserver.smo.dll9.0.3206.01,606,68002-Nov-200722:32x86
Microsoft.sqlserver.smoenum.dll9.0.3206.0222,23202-Nov-200722:32x86
Microsoft.sqlserver.sqlenum.dll9.0.3206.0898,07202-Nov-200722:32x86
Msfte.dll12.0.7822.02,430,31222-Jun-200709:22x86
Msftefd.exe12.0.7822.066,92022-Jun-200709:22x86
Msftepxy.dll12.0.7822.095,59222-Jun-200709:22x86
Msftesql.exe12.0.7822.095,59222-Jun-200709:22x86
Msir5jp.dll5.0.2130.03,159,91222-Jun-200709:22x86
Mssqlsystemresource.ldfNot applicable524,28802-Nov-200717:20Not applicable
Mssqlsystemresource.mdfNot applicable40,239,10402-Nov-200717:20Not applicable
Nlhtml.dll12.0.7822.0124,26422-Jun-200709:22x86
Nls400.dll5.0.4217.012,240,74422-Jun-200709:22x86
Odsole70.dll2005.90.3206.058,90402-Nov-200722:32x86
Osql.exe2005.90.3206.053,27202-Nov-200722:32x86
Query9x.dll12.0.7822.048,48822-Jun-200709:22x86
Rdistcom.dll2005.90.3206.0644,63202-Nov-200722:32x86
Replmerg.exe2005.90.3206.0320,53602-Nov-200722:32x86
Replprov.dll2005.90.3206.0549,91202-Nov-200722:32x86
Replrec.dll2005.90.3206.0784,92002-Nov-200722:32x86
Sac.exe9.0.3206.082,96802-Nov-200722:32x86
Sbmsmdlocal.dll9.0.3206.015,955,99202-Nov-200722:32x86
Sqlaccess.dll2005.90.3206.0350,23202-Nov-200722:32x86
Sqladhlp.exe2005.90.3206.047,12802-Nov-200722:33x86
Sqlagent90.exe2005.90.3206.0349,72002-Nov-200722:33x86
Sqlbrowser.exe2005.90.3206.0242,71202-Nov-200722:33x86
Sqlcmd.exe2005.90.3206.0143,38402-Nov-200722:33x86
Sqldiag.exe2005.90.3206.01,074,20002-Nov-200722:33x86
Sqldumper.exe2005.90.3206.068,63202-Nov-200722:33x86
Sqlmaint.exe2005.90.3206.077,84802-Nov-200722:33x86
Sqlsac.exe2005.90.3206.01,246,23202-Nov-200722:33x86
Sqlservr.exe2005.90.3206.029,211,16002-Nov-200722:33x86
Sqlsqm.exe9.0.3206.0128,02402-Nov-200722:33x86
Sqlwep.dll2005.90.3206.090,64802-Nov-200722:33x86
Sqlwtsn.exe9.0.3206.099,35202-Nov-200722:33x86
Sqsrvres.dll2005.90.3206.070,16802-Nov-200722:33x86
Ssradd.dll2005.90.3206.042,52002-Nov-200722:33x86
Ssravg.dll2005.90.3206.043,03202-Nov-200722:33x86
Ssrmax.dll2005.90.3206.040,98402-Nov-200722:33x86
Ssrmin.dll2005.90.3206.040,98402-Nov-200722:33x86
Ssrpub.dll2005.90.3206.030,23202-Nov-200722:33x86
Sysdbupg.sqlNot applicable510,62204-Sep-200716:26Not applicable
Tablediff.exe9.0.3206.087,06402-Nov-200722:33x86
Thawbrkr.dll12.0.7822.0206,18422-Jun-200709:22x86
Xmlfilt.dll12.0.7822.0197,99222-Jun-200709:22x86
Xpadsi90.exe2005.90.3206.050,71202-Nov-200722:33x86
Xpstar90.dll2005.90.3206.0298,52002-Nov-200722:33x86
SQL Server 2005 x64-based version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Bcp.exe2005.90.3206.088,08802-Nov-200722:28x64
Chsbrkr.dll12.0.7822.01,694,05622-Jun-200710:51x64
Chtbrkr.dll12.0.7822.06,109,03222-Jun-200710:51x64
Databasemailprotocols.dll9.0.3206.046,10402-Nov-200722:28x86
Distrib.exe2005.90.3206.086,55202-Nov-200722:28x64
Dts.dll2005.90.3206.01,892,88802-Nov-200722:28x64
Dtsconn.dll2005.90.3206.0408,08802-Nov-200722:28x64
Dtspipeline.dll2005.90.3206.01,065,49602-Nov-200722:28x64
Fteref.dll12.0.7822.0433,15222-Jun-200710:51x64
Infosoft.dll12.0.7822.0621,41622-Jun-200710:51x64
Instorcl.sqlNot applicable153,77924-Oct-200713:43Not applicable
Korwbrkr.dll12.0.7822.0101,73622-Jun-200710:51x64
Langwrbk.dll12.0.7822.0236,90422-Jun-200710:51x64
Mergetxt.dll2005.90.3206.037,91202-Nov-200722:28x64
Microsoft.analysisservices.dll9.0.3206.01,217,56002-Nov-200722:32x86
Microsoft.sqlserver.connectioninfo.dll9.0.3206.0156,69602-Nov-200722:28x86
Microsoft.sqlserver.dtstransferprovider.dll9.0.3206.0115,73602-Nov-200722:28x86
Microsoft.sqlserver.maintenanceplantasks.dll9.0.3206.0295,96002-Nov-200722:32x86
Microsoft.sqlserver.replication.dll2005.90.3206.01,832,98402-Nov-200722:28x64
Microsoft.sqlserver.servicebrokerenum.dll9.0.3206.042,00802-Nov-200722:28x86
Microsoft.sqlserver.smo.dll9.0.3206.01,606,68002-Nov-200722:28x86
Microsoft.sqlserver.smoenum.dll9.0.3206.0222,23202-Nov-200722:28x86
Microsoft.sqlserver.sqlenum.dll9.0.3206.0898,07202-Nov-200722:28x86
Msfte.dll12.0.7822.03,808,10422-Jun-200710:51x64
Msftefd.exe12.0.7822.099,17622-Jun-200710:51x64
Msftepxy.dll12.0.7822.0127,33622-Jun-200710:51x64
Msftesql.exe12.0.7822.0158,56822-Jun-200710:51x64
Msir5jp.dll5.0.2130.03,421,54422-Jun-200710:51x64
Mssqlsystemresource.ldfNot applicable524,28802-Nov-200717:20Not applicable
Mssqlsystemresource.mdfNot applicable40,239,10402-Nov-200717:20Not applicable
Nlhtml.dll12.0.7822.0191,84822-Jun-200710:51x64
Nls400.dll5.0.4217.014,101,35222-Jun-200710:51x64
Odsole70.dll2005.90.3206.090,13602-Nov-200722:28x64
Osql.exe2005.90.3206.085,52802-Nov-200722:28x64
Query9x.dll12.0.7822.068,45622-Jun-200710:51x64
Rdistcom.dll2005.90.3206.0828,44002-Nov-200722:28x64
Replmerg.exe2005.90.3206.0417,30402-Nov-200722:28x64
Replprov.dll2005.90.3206.0747,03202-Nov-200722:28x64
Replrec.dll2005.90.3206.01,012,24802-Nov-200722:28x64
Sac.exe9.0.3206.082,96802-Nov-200722:32x86
Sbmsmdlocal.dll9.0.3206.015,955,99202-Nov-200722:32x86
Sqlaccess.dll2005.90.3206.0357,40002-Nov-200722:28x86
Sqladhlp.exe2005.90.3206.066,07202-Nov-200722:28x64
Sqlagent90.exe2005.90.3206.0429,08002-Nov-200722:28x64
Sqlbrowser.exe2005.90.3206.0242,71202-Nov-200722:33x86
Sqlcmd.exe2005.90.3206.0338,45602-Nov-200722:28x64
Sqldiag.exe2005.90.3206.01,247,76802-Nov-200722:28x64
Sqldumper.exe2005.90.3206.083,99202-Nov-200722:28x64
Sqldumper.exe2005.90.3206.068,63202-Nov-200722:33x86
Sqlmaint.exe2005.90.3206.092,69602-Nov-200722:28x64
Sqlsac.exe2005.90.3206.01,246,23202-Nov-200722:33x86
Sqlservr.exe2005.90.3206.039,567,38402-Nov-200722:28x64
Sqlsqm.exe9.0.3206.0128,02402-Nov-200722:28x86
Sqlsqm.exe9.0.3206.0128,02402-Nov-200722:33x86
Sqlwep.dll2005.90.3206.0123,41602-Nov-200722:28x64
Sqlwep.dll2005.90.3206.090,64802-Nov-200722:33x86
Sqlwtsn.exe9.0.3206.099,35202-Nov-200722:28x86
Sqlwtsn.exe9.0.3206.099,35202-Nov-200722:33x86
Sqsrvres.dll2005.90.3206.082,96802-Nov-200722:28x64
Ssradd.dll2005.90.3206.050,71202-Nov-200722:28x64
Ssravg.dll2005.90.3206.051,73602-Nov-200722:28x64
Ssrmax.dll2005.90.3206.048,15202-Nov-200722:28x64
Ssrmin.dll2005.90.3206.048,15202-Nov-200722:28x64
Ssrpub.dll2005.90.3206.034,84002-Nov-200722:28x64
Sysdbupg.sqlNot applicable510,62204-Sep-200716:26Not applicable
Tablediff.exe9.0.3206.087,06402-Nov-200722:28x86
Thawbrkr.dll12.0.7822.0209,76822-Jun-200710:51x64
Xmlfilt.dll12.0.7822.0271,20822-Jun-200710:51x64
Xpadsi90.exe2005.90.3206.069,14402-Nov-200722:28x64
Xpstar90.dll2005.90.3206.0549,91202-Nov-200722:28x64

STATUS

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

MORE INFORMATION

After you apply this hotfix, conflicts are logged correctly when the Microsoft SQL Server Subscriber Always Wins Conflict Resolver is used and when the last change is not made on the publisher.

Steps to reproduce this issue

  1. In SQL Server 2005, create a publication of a merge replication.
  2. Add an article to the publication. Specify Microsoft SQL Server Subscriber Always Wins Conflict Resolver for the article.
  3. Create two subscribers for the publication. Name the subscribers Sub1 and Sub2.
  4. Change some data in a row on Sub1.
  5. Synchronize data between the publisher and Sub1.
  6. Change some data in the same row on Sub2.
  7. Synchronize data between the publisher and Sub2.
When you examine the data on the publisher, you find that the changes that you made on Sub1 are lost. However, the conflict is not logged.

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: 944677 - Last Review: October 8, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
Keywords: 
kbautohotfix kbsql2005repl kbexpertiseadvanced kbfix kbqfe kbHotfixServer KB944677

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