Conflict resolver generating reconciler error

  • Hi all,

    I have a mssql 2005 with two tables. [Order] and orderrow. And I'm using sqlce 3.1 on pocket pc's.

    Order has a join-filter with another table (routs), and orderrow is joined on to [Order] with 3 columns (CustomerNo, LevDate and RoutNo).

    On [Order] and OrderRow I have declared a conflict resolver (latest wins), on a column called [timestamp].

    When testing this resolver everyting works fine until following case:

    Client A creating a order with 2 rows

    Client B creates same order with only one row.

    Client B syncronizes and the server gets one row in [Order] and one row in Orderrow

    Client A syncronizes and the server fetching one of the clients rows, now the server has one row in Order and two in OrderRow. Now I get the following error:

    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.}

    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.}

    The merge process was unable to update last synchronization information at the Publisher

    So everyting looks good on the server but the error i can not find a solution for....

    Can someone point me to a solution for this problem?

  • What I can see in the conflict log. It is when the changes is to be updated to the client. In this cast an insert is forced. But the row is llready on the client (other version of the row).

    I wonder how I can get this problem solved. It feels like merge replication should manage to create an update instead of an insert.

  • It's the same problem that is asked about here:

    http://www.dbtalk.net/microsoft-public-sqlserver-replication/merge-replication-later-wins-conflict-223622.html

    I can not register at this site..

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply