Microsoft KB Archive/931932

From BetaArchive Wiki

Article ID: 931932

Article Last Modified on 11/2/2007


  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Personal Edition

Bug: #50000740 (SQL Hotfix)

Microsoft distributes Microsoft SQL Server 2000 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 2000 fix release.


This article describes the following about this hotfix release:

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


When you use merge replication that uses a custom resolver, the merge agent fails intermittently after you install Microsoft SQL Server 2000 Service Pack 4. When this problem occurs, you receive a message that resembles the following in the merge agent history log:

Processing article '<ArticleName>'
The step did not generate any output. The step failed. The job failed.
The Job was invoked by User <username>. The last step to run was step 1 (Run agent).

This failure may be preceded by a primary key violation or by another constraint violation that causes an error during synchronization.
Additionally, when you use the Replication Monitor to view the subscription merge agent history, you may see several actions listed. However, the Last Action Message of Session box is blank. Next to each action, you see a red x that indicates failure.


This problem occurs because the custom resolver code is not correctly invoked when errors occur during merge synchronization. These errors occur because of constraint violations, such as primary key conflicts or foreign key conflicts.


The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:

  • The system uses the Advanced Micro Devices (AMD) AMD64 processor architecture or the Intel Extended Memory 64 Technology (EM64T) processor architecture.

Note This issue does not occur on systems that use the Intel Itanium processor architecture.

  • The system is running a 64-bit version of the Microsoft Windows Server operating system.
  • The system is running a 32-bit version of SQL Server 2000.

We have corrected this installation issue in later builds of SQL Server 2000, starting with version 8.00.2244. When a customer who is running SQL Server 2000 on an x64-based system requests this hotfix, we will provide a build that includes this hotfix and that can be installed correctly on an x64-based system. The build that we provide will be version 8.00.2244 or a later version.

Hotfix information

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

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

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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.


You must have Microsoft SQL Server 2000 Service Pack 4 (SP4) installed to apply this hotfix.

For more information about how to obtain SQL Server 2000 Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:

290211 How to obtain the latest SQL Server 2000 service pack

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 2000, 32-bit x86 versions
File name File version File size Date Time Platform
Dtsui.dll 2000.80.2238.0 1,593,344 24-Jan-2007 16:43 x86
Impprov.dll 2000.80.2238.0 102,400 24-Jan-2007 16:43 x86
Msgprox.dll 2000.80.2238.0 94,208 24-Jan-2007 16:43 x86
Msrpjt40.dll 4.10.9424.0 188,473 24-Jan-2006 08:13 x86
Mssdi98.dll 8.11.50523.0 239,104 06-Jun-2005 22:46 x86
Ntwdblib.dll 2000.80.2238.0 290,816 24-Jan-2007 16:43 x86
Odsole70.dll 2000.80.2238.0 69,632 24-Jan-2007 16:43 x86
Osql.exe 2000.80.2238.0 57,344 24-Jan-2007 08:18 x86
Pfclnt80.dll 2000.80.2238.0 430,080 24-Jan-2007 16:43 x86
Qrdrsvc.exe 2000.80.2238.0 192,512 24-Jan-2007 08:22 x86
Replmerg.exe 2000.80.2238.0 163,840 24-Jan-2007 08:27 x86
Replprov.dll 2000.80.2238.0 237,568 24-Jan-2007 16:43 x86
Replrec.dll 2000.80.2238.0 315,392 24-Jan-2007 16:43 x86
Replsub.dll 2000.80.2238.0 270,336 24-Jan-2007 16:43 x86
Rinitcom.dll 2000.80.2238.0 278,528 24-Jan-2007 16:43 x86
Semexec.dll 2000.80.2238.0 856,064 24-Jan-2007 16:43 x86
Snapshot.exe 2000.80.2238.0 61,440 24-Jan-2007 08:32 x86
Sqlagent.exe 2000.80.2238.0 323,584 24-Jan-2007 08:04 x86
Sqldiag.exe 2000.80.2238.0 118,784 24-Jan-2007 08:54 x86
Sqldmo.dll 2000.80.2238.0 4,362,240 24-Jan-2007 16:43 x86
Sqlfth75.dll 2000.80.2238.0 102,400 24-Jan-2007 08:17 x86
Sqlservr.exe 2000.80.2238.0 9,175,040 24-Jan-2007 09:52 x86
Sqlsort.dll 2000.80.2238.0 589,824 24-Jan-2007 16:43 x86
Stardds.dll 2000.80.2238.0 176,128 24-Jan-2007 16:43 x86
Svrnetcn.dll 2000.80.2238.0 110,592 24-Jan-2007 16:43 x86
Ums.dll 2000.80.2238.0 35,328 24-Jan-2007 16:43 x86
Xpstar.dll 2000.80.2238.0 311,296 24-Jan-2007 16:43 x86


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


For more information about all publicly released SQL Server 2000 post-service pack hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

894905 Cumulative list of the hotfixes that are available for SQL Server 2000 Service Pack 4

For more information, 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

Keywords: kbhotfixserver kbqfe kbpubtypekc KB931932