Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Cleaning up Replication Monitor


Cleaning up Replication Monitor

Author
Message
Chris Wasser
Chris Wasser
Grasshopper
Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)

Group: General Forum Members
Points: 10 Visits: 3
I have sucessfully removed an old publication and it subscriptions, but I am still seeing references to it in the Replication Monitor under Publishers, Snapshot Agents, and Distribution Agents. When I try to delete the listing under Publishers I get an error message that states the following:
Error 21776:[SQL-DMO] The name 'Publication1' was not found in the TransPublications collection. If the name is a qualified name, use{} to separate various parts of the name and try again.

When I try to look at the properties of the agents I get the following error message:
Error 14262: The specified @job_id('xxxyyyzzz') does not exist.

So it appears that the old publication and its components are in fact gone (or at least to SQL Server they cannot be found), but these error messages are still there and I cannot remove them. While this is not affecting any functionality, it "looks" like something is wrong when viewed through SQL-EM.

I am using SQL_EM to manage these replication services, but can run procs through Query Analyzer if that will help.

Any help or direction would be greatly appreciated.

-Chris
TriggerMe
TriggerMe
SSC Eights!
SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)SSC Eights! (874 reputation)

Group: General Forum Members
Points: 874 Visits: 328
You may have to refersh the JOBS window to reflect the changes.


Kindest Regards,



Bas Schouten
Bas Schouten
SSC Journeyman
SSC Journeyman (86 reputation)SSC Journeyman (86 reputation)SSC Journeyman (86 reputation)SSC Journeyman (86 reputation)SSC Journeyman (86 reputation)SSC Journeyman (86 reputation)SSC Journeyman (86 reputation)SSC Journeyman (86 reputation)

Group: General Forum Members
Points: 86 Visits: 1

I'v encountered the same problems with a replication, When the publication was removed it didnt get totally deleted from the publication server. It all happend some time ago so I don't quite know anymore how I solved it, but I do remember that it made a difference how I removed the publication: by unchecking the database in published databases via the tools menu, or by removing the publication in the Replication tree from Enterprise manager

I think it is a glitch in SQL ...






Bas Schouten

CBIS BV
Chris Wasser
Chris Wasser
Grasshopper
Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)

Group: General Forum Members
Points: 10 Visits: 3
Turns out I was able to clear everything out by disabling replication (luckily it was on the test server ) and then re-enabling it.

I also needed to run sp_MSLoad_replication_status to clear out the error marks in replication monitor. I have also heard that rebooting achieves the same result, bu this was not an option for me.

-Chris
nuwins
nuwins
Forum Newbie
Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)

Group: General Forum Members
Points: 5 Visits: 1

I've come across this problem several times and I'm still not sure what causes it. Previously the only solution I had was to disable replication and re-create all the subscriptions (by scripting the replication before deleting it of course).

However the last time this happened I created a new subscription with the same name as the subscription that was causing the problem and SQL Server let me do it! If you then go on to delete the subscription that replication shows is in error and refresh replication, both the new subscription and the old one have gone and replication shows no errors!





David Poluxt
David Poluxt
SSC Rookie
SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)

Group: General Forum Members
Points: 43 Visits: 95

What nuwins suggested worked!

I had a nasty red X in replication monitor for a publication that I had long ago deleted. So I just made a quick publication with the same name (it allowed me to do this!), and then the red X went away. Then I deleted the publication normally and the problem was solved!


Darin-394772
Darin-394772
Forum Newbie
Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: General Forum Members
Points: 3 Visits: 1
Brilliant, that worked exactly perfectly for me, too. Thanks!
MohammedU
MohammedU
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1198 Visits: 812

Another solution for this will be cleanup table in MSDB.



MohammedU
Microsoft SQL Server MVP
Wired-528862
Wired-528862
Grasshopper
Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)Grasshopper (16 reputation)

Group: General Forum Members
Points: 16 Visits: 56
This worked great nuwins. I didn't have to remove all publications, just create one with the EXACT same name as the one your are trying to delete. Then delete the publication and it will be gone from the replication monitor. You're kind of "tricking" SQL. Thanks for the help.
Adrian Robertson
Adrian Robertson
SSC Rookie
SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)SSC Rookie (25 reputation)

Group: General Forum Members
Points: 25 Visits: 107
What if your subscription is on a machine that is no longer available?
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search