error with Transactional replication

[kodaksmile]

Hi all,

I received an error on transactional replication that has been set up for some time:

Cannot insert duplicate key row in object 'DirectoryWordLists' with unique index 'PK_DirectoryWordListEntries'

There are no duplicate entries in the table on the publisher nor on the subscriber. I am not sure what the issue is as if there are no duplicate records on the publisher it should not be pushing a duplicate row to the subscriber. Do I need to reinitialize? or tear out and rebuild replication?

Thanks for your help

 

[ptheriault]

I would reinitialize the subscription.

- Paul
- If at first you don't succeed, find out if the loser gets anything.

 

[SQLBill]

That error does NOT mean there is duplicate data. It means that there WILL be duplicate data if it replicates whatever it is trying to do. Two situations where this can occur:

It can mean that a row was sent from the publisher to the subscriber and then later on it tried to send the SAME row again for some reason.

It could also occur if someone need to do an insert and accidentally ran the insert command on both the publisher and the subscriber. Then when the publisher tried to replicate the command, the row already existed on the subscriber.

-SQLBill

Posting advice: FAQ481-4875

 

[kodaksmile]

Reinitializing and resynching resolved the issue - according to those who work on this system no one made any changes ( ) In theory they should not have since the issue occurred after a power down of all systems - there were no changes allowed during the 2 days prior or after. The data being replicated is configuration data only for a system but, the error says otherwise.

Thanks for the advise.