April 5, 2016 at 8:50 am
Hi everyone.
I just rebuilt all Peer to Peer replication on 4 servers.
BR - Originator ID = 91,
NO – Originator ID = 81
SH – Originator ID = 71
HO – Originator ID = 61
Replication is setup between BR and the other three.
I am getting these messages on the last three serves.
NO
A conflict of type 'Update-Update' was detected at peer 81 between peer 91 (incoming), transaction id 0x000000001d245751 and peer 157 (on disk), transaction id 0x000000001cfa6c1f
SH
A conflict of type 'Update-Update' was detected at peer 71 between peer 91 (incoming), transaction id 0x000000001d24530b and peer 157 (on disk), transaction id 0x000000001cfa6bbe
HO
A conflict of type 'Update-Update' was detected at peer 61 between peer 91 (incoming), transaction id 0x000000001d245987 and peer 157 (on disk), transaction id 0x000000001cfa6c27
Peer 157 does not exist anymore. It was the BR node before I rebuilt all replication. The “MSpeer_originatorid_history” table does not have the 157 peer.
Anyone know what is happening? How can it detect a conflict with a non-existed node?
Thanks,
C.J.
April 5, 2016 at 10:38 am
Should i just not ask why and delete all replication, disable replication and then recreate?
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply