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.
If you are a Small Business customer, find additional troubleshooting and learning resources at the Support for Small Business site.
Consider the following scenario. In Microsoft SQL Server 2000, you have a Replication Merge Agent job. You install SQL Server 2000 Service Pack 4 (SP4). Then, you schedule the job to run. In this scenario, the job may not run successfully. When you use
Replication Monitor to view the error message for the job, the error message resembles the following:
process could not enumerate changes at the 'Subscriber'. (Source: Merge
Replication Provider (Agent); Error number: -2147200999)
(Process ID 83) was deadlocked on lock resources with another process and has
been chosen as the deadlock victim. Rerun the transaction. (Source: AP291998
(Data source); Error number: 1205)
For a list of all publicly
released SQL Server 2000 post-Service Pack 3a hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
This problem occurs when a deadlock condition occurs during the Merge Agent's execution of the sp_MSenumchanges stored procedure. This deadlock condition causes the job to fail. No logic exists to restart the Replication Merge Agent. Therefore, you must manually
job if one of the following conditions is true:
In the Schedule type list, you click Start automatically when SQL Server Agent starts for the job.
You use the Continuous argument for the Replication Merge Agent.
If you click Recurring in the Schedule type list, the
job starts again based on the job schedule.
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.
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.
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, submit a request to 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:
How to obtain the latest SQL
Server 2000 service pack
You do not have to restart the computer after you apply this
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 all the
files that you must have to fully update a product to the latest
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.
To work around this problem, click Recurring in the Schedule type list for the job. Then, schedule the job to run every minute. When you do this, the latency is
longer than when you use the Continuous argument for the Replication Merge Agent. However, the job restarts within a minute if a deadlock condition causes the
job to fail.
To enable this hotfix, you must use a trace flag. If you apply this hotfix and you do not use the trace flag, a deadlock condition may still cause the
job to fail.
To enable this hotfix, add
trace flag 120 as a Replication Merge Agent command-line parameter. Do this for every
instance of the Replication Merge Agent that is configured to synchronize with your
publication. To do this, follow these steps:
In SQL Server Enterprise Manager, locate
Management, expand SQL Server Agent,
and then expand Jobs.
In the right pane, double-click the
job in the Jobs list.
Click the Steps tab, and then double-click
In the Command box, add the following command-line parameter:
Click OK, and then close all the dialog boxes.
If the Replication Merge Agent is running, stop and then restart
the Replication Merge Agent to enable the trace flag and the hotfix.
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: