Microsoft KB Archive/925678

= FIX: Error message when you schedule a Replication Merge Agent job to run after you install SQL Server 2000 Service Pack 4: &quot;The process could not enumerate changes at the 'Subscriber'&quot; =

Article ID: 925678

Article Last Modified on 11/2/2007

-

APPLIES TO


 * Microsoft SQL Server 2000 Enterprise Edition 64-bit
 * Microsoft SQL Server 2000 Desktop Engine (Windows)
 * Microsoft SQL Server 2000 Developer Edition
 * Microsoft SQL Server 2000 Enterprise Edition
 * Microsoft SQL Server 2000 Personal Edition
 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 2000 Workgroup Edition
 * Microsoft SQL Server 2000 Developer Edition

-



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.



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. 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:

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)

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:

810185 SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a



CAUSE
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:
 * 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.



RESOLUTION
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, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone 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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
 SQL Server 2000 Service Pack 4

For more information about 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 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 Itanium architecture version


WORKAROUND
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.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
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.</li> Click the Steps tab, and then double-click Run Agent.</li> In the Command box, add the following command-line parameter:

-T 120

</li> Click OK, and then close all the dialog boxes.</li> If the Replication Merge Agent is running, stop and then restart the Replication Merge Agent to enable the trace flag and the hotfix.</li></ol>

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

Keywords: kbtshoot kbbug kbfix kbqfe kbpubtypekc kbexpertiseadvanced kbhotfixserver KB925678

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.