Get help: http://help/MSSQL_REPL-2147199401
This issue may occur for multiple reasons. These include many reasons that are expected under certain circumstances. To determine whether you have encountered this error unexpectedly, examine the metadata details that are described in the "Cause" section.
Make sure that the merge agent is no longer synchronizing. Then, run the following query, and examine the results:
The sentgen column marks the oldest group of changes that the subscriber sent to the publisher. If multiple values are returned, examine the other columns in the dbo.sysMergeSubscriptions table to make sure that you are viewing the metadata for the correct publication. Next, use the value that this query returns in the following query:
You may encounter the error unexpectedly when all the following conditions are true:
- The value in the generation column in the first row is slightly greater than the sentgen value in the previous query.
- The value in the genstatus column is 4.
- The value in the changecount column is 0.
Note The value of the coldate column of the first row is also typically much older than the value of that column in the other rows.
In some scenarios, you may be able to resolve this problem without a complete reinitialization. Contact Microsoft Customer Support Services for information about a possible workaround.
To prevent future occurrences of this problem, apply one of the following fixes, depending on your version of SQL Server.