views:

9

answers:

0

I have SQL Server 2005 running on a development machine that is administered by people rather far away, metaphorically speaking.

They decided it would be fun to change the Network Name/Computer Name/Hostname in command prompt of this machine from "OldName" to "NewName".

SQL Server was installed and distribution and publishing set up under "OldName". I can still get to the data in the databases there, but distribution and replication are quite messed up by this.

When I right-click on the Replication folder, and select any of the options to do with replication (aside from the Monitor), it gives me the following error:

SQL Server is unable to connect to server 'NewName'. SQL Server replication requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specify the actual server name, 'OldName'. (Replication.Utilities)

I did find a reference to "OldName" in the [msdb].[dbo].[MSdistpublishers] table, but changing the entry to "NewName" didn't do anything, even after I restarted SQL Server.

So, does anyone know of a way to fix this, short of reinstalling SQL Server, or trying to reason with the people who are far, far away?

Many thanks!