We did an in-place upgrade and everything seems to be working fine except the single distribution to another (also 2014) server has a replication error on the snapshot agent. The error is "Invalid object name MSredirected_publishers" which is strange because no redirection has been set up and there is no such table in the distribution database. Deleting and recreating the publication (from the generated script) makes no difference. Any suggestions?
from what I've read, you need to script out your publications and subscriptions then - here's the uncomfortable bit, disable replication, DELETE the distribution database , then rebuild the distributor (through the wizard)
then you can re-apply your pubs and subs
to be honest , I've never really been a fan of in-place upgrades, they cause lots of problems like this (mostly around sql agent)
MVDBA
March 12, 2020 at 11:03 pm
Great suggestions, replication is now working. The only issue I had was disabling distribution in the first place, because the distribution database was still in use. Identifying and killing the process using it (from the Activity Monitor) allowed the 'Disable Publishing and Distribution Wizard' to delete the database, and from there I could configure distribution again and restore the publication.
March 13, 2020 at 8:39 am
don't forget to put your alerts back on the replication jobs 🙂
MVDBA
March 15, 2020 at 10:54 pm
Mike,
Sorry to be ignorant, but what are the relevent errors should I configure alerts for?
Thanks,
David
March 16, 2020 at 9:08 am
firstly go to sql agent and put an alert on any replication job that fails
secondly - go into replication monitor, expand the publisher and right click on the publisher name - (not the top level, there is a publisher name under the server name)
click on "configure replication alerts"
you choose what you want to monitor
MVDBA
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply