Microsoft KB Archive/277737

From BetaArchive Wiki
Knowledge Base


FIX: Merge Replication Reports Misleading Conflict When Using Horizontal Filtering

Article ID: 277737

Article Last Modified on 3/14/2006



APPLIES TO

  • Microsoft SQL Server 7.0 Service Pack 2



This article was previously published under Q277737

BUG #: 58299 (SQLBUG_70)

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.

Keywords: kbbug kbfix KB277737