Folks,
I've been successfully using merge replication for probably 15 years.
However I've never had to set up a republisher scenario and I've hit a snag.
It's a pretty basic merge replication republisher. (2008 R2)
Server <> Republisher Server <> SQL Mobile client
Initial testing looked good but what's happened is the subscriber that successfully added and merged new records tried to sync 24 hours later and the 10 records previously synced have created a conflict. On attempting to resolve the conflict (submitting the loser) the error is an duplicate identity insert conflict.
Violation of PRIMARY KEY constraint 'PK_Observations'. Cannot insert duplicate key in object 'dbo.Observations'.
Which is true because it's the exact same record previously and successfully synced by the same subscriber.
The record made it's way all the way back to the Main Server so we know it's correct. it just appears as though the subscriber "forgot" it had already submitted these records and was attempting to submit them again.
I susupect a metadata issue.
Any thoughts on diagnosing the issue appreciated.