January 27, 2017 at 8:00 am
Hi all,
I am in kind of a pickle and could use some help asap. I just started a job where transactional replication is set up. The data replicates from a data center through a private VPN to the subscriber. They are getting the common "Row not found at subscriber" error. I used sp_browsereplcmds and think I have found the error: an update/insert on 2 articles where I am assuming the row doesn't exist. Since no one at this company knows the replication passwords or currently has access to the subscriber database, I need to put skip errors in the agent. The distribution database is sql 2012. This is what I think I need to do: "The most common way to use the -SkipErrors parameter is to use the Distribution Agent profile titled Continue On Data Consistency Errors. The Distribution Agent will then skip errors 2601, 2627, and 20598 ."
This will be a work-around until I can resynch the subscription. Will this cause a password prompt (which we don't have)
Any help appreciated.
Thanks!
Kristina
January 30, 2017 at 12:56 am
Hi,
have you ever tried to skip the error in the replication monitor?
If you are on the server with an "sa" account, you should start the replication monitor and change the settings of the agent profile.
Kind regards,
Andreas
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply