Select the product you need help with
FIX: Error message when you try to synchronize a SQL Server 2005 Compact Edition subscription again: "The common generation watermark is invalid at this replica since it does not exist"Article ID: 938050 - View products that this article applies to. Bug #: 50001335 (SQL Hotfix) On This PageSYMPTOMSConsider the following scenario. You synchronize a Microsoft SQL Server 2005 Compact Edition (SQL Server Compact Edition) subscription to a Microsoft SQL Server 2005 publication. During the synchronization, you disconnect the subscriber. In this scenario, you receive the following error message when you try to synchronize the SQL Server Compact Edition subscription again: System.Data.SqlServerCe.SqlCeError: A call to SQL Server Reconciler failed. Try to resynchronize. The merge process failed because it detected a mismatch between the replication metadata of the two replicas, such that some changes could be lost leading to non-convergence. This could be due to the subscriber not having synchronized within the retention period, or because of one of the replicas being restored to a backup older than retention period, or because of the publisher performing more aggressive cleanup on articles of type download-only and articles with partition_options = 3. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199363) The common generation watermark is invalid at this replica since it does not exist or metadata for changes not yet propagated may have been cleaned up. (Source: MSSQLServer, Error number: 21800)
CAUSEThis problem occurs because the merge replication metadata at the publisher differs from the merge replication metadata at the subscriber. When you try to synchronize the SQL Server Compact Edition subscription again, the merge replication process detects the difference. Therefore, you receive the error message. RESOLUTIONCumulative update informationTo resolve this problem, install SQL Server 2005 Service Pack 2. Then, install cumulative update package 2 for SQL Server 2005 Service Pack 2 (build 3175). This problem is resolved in cumulative update package 2 for SQL Server 2005 Service Pack 2 (build 3175).For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base: 913089
For more information about how to obtain cumulative hotfix package 2 for SQL Server 2005 Service Pack 2 (build 3175), click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/913089/
)
How to obtain the latest service pack for SQL Server 2005
936305
(http://support.microsoft.com/kb/936305/
)
Cumulative update package 2 for SQL Server 2005 Service Pack 2 is available
WORKAROUNDTo work around this problem, set the partition options property to the 1 value or to the 2 value. STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. REFERENCESFor more information about the partition options property, see the "To set filtering options" section of the following Microsoft Developer Network (MSDN) Web site: http://msdn2.microsoft.com/en-us/library/ms152478(SQL.90).aspx
(http://msdn2.microsoft.com/en-us/library/ms152478(SQL.90).aspx)
PropertiesArticle ID: 938050 - Last Review: November 20, 2007 - Revision: 1.2 APPLIES TO
|


Back to the top








