I don't have access to "my" SQL Servers right now, but my initial guess is that this is caused by a conflict. Open the conflict viewer and check. Also, what does the Conflict column in Replication Monitor say?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply