We have a merge replication topology set up between a SQL Server 2008 instance, and multiple SQL CE 3.5 subscribers. We have begun seeing the following error on the subscriber machine while synchronizing:
"A Subscriber Row failed to apply at the Publisher"
Also, we see the following error in Conflict Viewer:
"A row insert at [Subscription Name] could not be propagated to [ServerDatabaseName]. This failure can be caused by a constraint violation. Violation of PRIMARY KEY constraint [PrimaryKeyName]. Cannot insert duplicate key in object [ObjectName]. The duplicate key value is (5ef97fc3-e5e2-42b8-905d-2807687855e8)."
I've verified that a row with that PK value (the GUID in the error above) exists on the server (publisher), yet the subscriber seems to be trying to send another insert of the row with the same PK value. To make things even weirder, the PK constraints also exist on the subscription CE databases, so how would a new insert with the same PK value even be allowed on the subscriber to prompt an Insert command to be uploaded at all?
There are no Foreign Key's on the publisher or subscriber, and I'd be happy to provide more info if needed.
Has anyone experience this before? Thanks!
Clint