FIX: Merge Agent Failure That Occurs with SQL Server Initial Snapshot Delivery Is Not Recognized in Subsequent Run of the Merge Agent (299539)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
This article was previously published under Q299539
BUG #: 450049 (SHILOH_BUGS)
SYMPTOMS
The Merge Agent of a Pull subscriber to a merge publication may report the following error message during the initial synchronization process:
The remote procedure call failed and did not execute. The step failed.
SQL Server Agent could not access the replication agent. Use the DCOMCNFG utility to confirm that the SQL Server Agent Windows account has permissions to launch the replication agent. The step failed.
When you restart the Merge Agent, SQL Server may not recognize that the snapshot application failed and starts merging incremental changes if any.
CAUSE
The error messages listed in the "Symptoms" section may occur if the Subscriber loses its network connection intermittently during the application of the initial snapshot. After the network connection is lost, the Merge Agent does not restart the initial snapshot. Because the snapshot is not restarted, the Subscriber may become unsynchronized with the Publisher.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 2.
| Modification Type: | Major | Last Reviewed: | 10/16/2003 |
|---|
| Keywords: | kbbug kbfix kbQFE KB299539 |
|---|
|