SQL Server Forums
Profile | Register | Active Topics | Members | Search | Forum FAQ
 
Register Now and get your question answered!
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2005 Forums
 Replication (2005)
 Cannot drop Publications
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

jpotucek
Constraint Violating Yak Guru

USA
273 Posts

Posted - 06/28/2012 :  15:27:29  Show Profile  Send jpotucek an AOL message  Reply with Quote
I am running

Microsoft SQL Server 2005 - 9.00.4226.00 (X64) SQL Server 2005 Standard

I had a working transactional replication publication set up and it was working. I needed to restore the database that was acting as publisher and then change who the subscriber was so what I did was drop the subscription, drop the publication, restored the database (to a new name) and then rebuilt the publication and added the new subscriber.

I must have done something out of order because I created the new publication and then added the new subscriber and I cannot get it to work.

These are the type of errors I am getting in the log:
(note Server names have been changed to Serverx (Publisher) and ServerY (Suscriber))

Replication-Replication Transaction-Log Reader Subsystem: agent Serverx-1 failed. The process could not execute 'sp_repldone/sp_replcounters' on 'Serverx'.
______________
Replication-Replication Distribution Subsystem: agent Serverx-ServerY-8 failed. The process could not access database 'Test' on server 'ServerY

Basically TEST database is the OLD original subscriber and that database has been dropped.

I tried recreating it and that didn't help

now I am just attempting to drop the new publication that I created and it hangs and then crashes Management studio.

Not really sure where to go from here.. can anyone help?



Edited by - jpotucek on 06/22/2013 02:50:53

jpotucek
Constraint Violating Yak Guru

USA
273 Posts

Posted - 06/28/2012 :  16:46:41  Show Profile  Send jpotucek an AOL message  Reply with Quote
I got this cleaned up by going in through Management studio and DISABLING Replication - this seemed to cleanup what I messed up and allowed me to re-do the whole thing.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.08 seconds. Powered By: Snitz Forums 2000