July 7, 2014 at 9:01 am
Server 1: SEP (distribution)
Source database 1: CM
Publication 1: CM_PUB
Source database 2: APPS
Publication 2: APPS_PUB
Server 2: RPT
Destination database 1: CM
Destination database 2: APPS
Server 3: DEV4 - random. Shouldn't even be included in this replication set.
Transactional replication
Both servers are 2008 R2
I needed to completely remove replication from the environment. I did the "Disable Publishing and Distribution" thing and it failed. I manually deleted the subscriptions and agent jobs and tried again. It still failed. It let me manually delete the CM_PUB publication, but not the APPS_PUB publication.
So, now when I try to run Disable Publishing and Distribution, I get the following error:
SQL Server could not disable publishing and distribution on SEP
DEV4 is not defined as a Subscriber for CM
Could not update the distribution database subscription table. The subscription status could not be changed.
When I try to delete the APPS_PUB publication:
Could not delete publication APPS_PUB
DEV4 is not defined as a Subscriber for CM
Could not update the distribution database subscription table. The subscription status could not be changed.
When I try to delete the subscription to APPS_PUB without connecting to DEV4:
Could not delete the subscription at Subscriber DEV4 in database APPS
DEV4 is not defined as a Subscriber for CM.
Could not update the distribution database subscription table. The subscription status could not be changed.
So clearly, someone mistakenly pointed the publication at the wrong server. How do I make this all go away?
To complicate things, DEV4 does get replicated from a server named DEV3. Do I need to kill replication there too and rebuild it?
July 7, 2014 at 10:18 am
First off, I want to be clear that I haven't had to deal with this issue, but a quick search showed this page in BOL, http://technet.microsoft.com/en-us/library/ms152757(v=SQL.105).aspx which has this note at the top:
NoteNote
If you are unable to remove a replication component using the method provided, execute the stored procedure sp_removedbreplication (Transact-SQL) on the appropriate database(s).
Which may help in you situation.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
July 7, 2014 at 12:28 pm
I ran sp_removedbreplication and it ran successfully, but the errant replication artifacts are still hanging there causing errors.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply