Article ID: 925678 - View products that this article applies to.
Bug #: 50000218 (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:
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:
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:
The process could not enumerate changes at the 'Subscriber'. (Source: Merge Replication Provider (Agent); Error number: -2147200999)
Transaction (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)
(http://support.microsoft.com/kb/810185/ )SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a
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 restart the job if one of the following conditions is true:
The installer does not install this hotfix correctly on x64-based systems. This installation issue occurs when the following conditions are true:
Hotfix informationA 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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
Restart informationYou do not have to restart the computer after you apply this hotfix.
Registry informationYou do not have to change the registry.
Hotfix file informationThis 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 2000 32-bit version
Collapse this tableExpand this table
SQL Server 2000 Itanium architecture version
Collapse this tableExpand this table
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.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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:
822499For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/ )New naming schema for Microsoft SQL Server software update packages
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 925678 - Last Review: October 8, 2011 - Revision: 2.0