Article ID: 2479589 - View products that this article applies to.
Consider the following scenario:
A call to SQL Server Reconciler failed. Try to resynchronize.
HRESULT 0x80004005 (29006)
An error occurred while reading the .bcp data file for the 'MSmerge_rowtrack' article. If the .bcp file is corrupt, you must regenerate the snapshot before initializing the Subscriber.HRESULT 0x8004563C (0)
The merge process was unable to deliver the snapshot to the Subscriber. If using Web synchronization, the merge process may have been unable to create or write to the message file. When troubleshooting, restart the synchronization with verbose history logging and specify an output file to which to write.
HRESULT 0x80045017 (0)
This issue occurs because an error occurs in a merge insert trigger. When a join filter is applied between two articles, a row is inserted incorrectly into the "MSmerge_contents" table. The inserted row has a lineage attribute set to 0x00.
Note The merge insert trigger is generated when the merge publication is created.
The hotfix that resolves this problem is included in cumulative update package 3 for SQL Server Compact 3.5 Service Pack 2.
For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2489362/EN-US/ )Cumulative Update 3 for SQL Server Compact 3.5 Service Pack 2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To work around this issue, follow these steps:
For more information about how to filter published data for merge replication, visit the following Microsoft Developer Network (MSDN) website:
How to filter published data for merge replication
Article ID: 2479589 - Last Review: February 14, 2011 - Revision: 3.0