FIX: Merge Replication Reports Misleading Conflict When Using Horizontal Filtering

Article translations Article translations
Article ID: 277737 - View products that this article applies to.
This article was previously published under Q277737
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 58299 (SQLBUG_70)
Expand all | Collapse all

SYMPTOMS

For merge replication with a horizontal filter specified, if a row that does not meet the filtering criteria is inserted into the subscriber table, it is replicated to the publisher, but deleted on the subscriber, during the synchronization process. When you attempt to delete the same row from the publisher, the following conflict is reported:
The row was deleted at Publisher but could not be deleted at Subscriber. Unknown error.

WORKAROUND

This conflict should not be reported, because the row was deleted from the subscriber during the synchronization process. You can ignore this conflict by clicking the Resolve button in the Conflict Viewer, without affecting the successful operation of the merge agent.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
274799 INF: How to Obtain Service Pack 3 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.

Properties

Article ID: 277737 - Last Review: February 28, 2014 - Revision: 5.1
APPLIES TO
  • Microsoft SQL Server 7.0 Service Pack 2
Keywords: 
kbnosurvey kbarchive kbbug kbfix KB277737

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com