Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2008 Forums
 Replication (2008)
 Unable to Remove Replication

Author  Topic 

seancw
Starting Member

2 Posts

Posted - 2009-09-16 : 02:22:28
I had a hardware failure of a distribution db and when the data was restored, the replication wasn't maintained.

Now I am trying to setup peer to peer replication and have the following issues:

1.) @@ServerName displays the OLD windows server name, not the new machine that the database runs on. I had to rename the machine, but I didn't rename the instance.
2.) sp_helpdistributor returns NULL values in fields
3.) sp_helpserver returns a list of servers that is no longer in use. Server id 0 is the same name as the @@ServerName, the OLD machine that the sqlserver was installed on. Server id 1 and 3 are replication servers that are no longer in service. id3 was the hardware that failed and id 1 was a virtual machine on that hardware.
4.) I tried everything listed here: http://support.microsoft.com/kb/324401 , to no avail.

I just need to remove any instances of replication. When I right click on the replication folder in SSMS, I get an error that says "cannot connect to <NEW SERVER>\Instance. Specify the actual server name '<OLD SERVER NAME>\INSTANCE (replication.utilities) .



dbcc = fail ?

dinakar
Master Smack Fu Yak Hacker

2507 Posts

Posted - 2009-09-17 : 15:57:16
(1) use sp_Dropserver and sp_Addserver to rename the servername correctly
(2) use sp_Removedbreplication on all databases that have orphaned replication objects
(3) check if the server names are correct
(4) re-implement replication.

Dinakar Nethi
************************
Life is short. Enjoy it.
************************
http://weblogs.sqlteam.com/dinakar/
Go to Top of Page

seancw
Starting Member

2 Posts

Posted - 2009-09-19 : 13:55:22
I already tried those commands, but they would fail because they say that the servers were publishers.

I ended up contacting MS support and they had to put n a non supported hack to remove the replication information from my master table.

dbcc = fail ?
Go to Top of Page
   

- Advertisement -