March 1, 2012 at 4:03 pm
Hi there!
Situation:
Old server named "TRANSIT" has been cloned in VMWare to a new server named "TRAFIC".
Server has been configured and has started up. Everything looks fine but:
SELECT @@SERVERNAME
> TRANSIT
We have searched MSDN and have found a document (http://msdn.microsoft.com/en-us/library/ms143799.aspx) which describes a procedure of changing a server name. The problem is - it does not work in our case:
sp_dropserver "TRANSIT"
GO
> Msg 15190, Level 16, State 1, Procedure sp_dropserver, Line 56
There are still remote logins or linked logins for the server 'TRANSIT'.
So we have tried:
sp_dropremotelogin old_name
GO
> Msg 15185, Level 16, State 1, Procedure sp_dropremotelogin, Line 68
There is no remote user '(null)' mapped to local user '(null)' from the remote server 'TRANSIT'.
or even
sp_dropremotelogin "TRANSIT\TRANSIT"
sp_dropremotelogin "local\TRANSIT"
GO
and any other combinations - same problem:
>Msg 15185, Level 16, State 1, Procedure sp_dropremotelogin, Line 68
There is no remote user '(null)' mapped to local user '(null)' from the remote server 'TRANSIT'.
>Msg 15190, Level 16, State 1, Procedure sp_dropserver, Line 56
There are still remote logins or linked logins for the server 'TRANSIT'.
Any idea how to change SQL SERVER 2008 instance name? Without this changed, we are unable to use Replication Services. Every time we try to edit, remove or even display properties of Replication -> Local Publications we get:
SQL Server is unable to complete the operation.
Additional information:
An error occurred connecting to Publisher 'TRAFIC'. (Subscription Properties)
SQL replication requires the actual server name to make a connection to the server.
Connection through a server alias, IP address, or any other alternative name are not supported.
Specify the actual server name, "TRANSIT".(Replication.Utilities)
and that is the dead end...
Anybody could help, please?
March 1, 2012 at 4:09 pm
March 1, 2012 at 4:13 pm
That is exactly what we tried. The problems described in my post.
I have tried the approach they describe upon the website you gave me:
To disable replication using the SQL Server Enterprise Manager
Expand a server group, and then expand the Distributor (the server that contains the distribution database).
Right-click the Replication folder, and then click Disable Publishing.
Complete the steps in the Disable Publishing and Distribution Wizard.
But as soon an I do the part "Right-click the Replication folder, and then click Disable Publishing", I get:
SQL Server is unable to complete the operation.
Additional information:
An error occurred connecting to Publisher 'TRAFIC'. (Subscription Properties)
SQL replication requires the actual server name to make a connection to the server.
Connection through a server alias, IP address, or any other alternative name are not supported.
Specify the actual server name, "TRANSIT".(Replication.Utilities)
Any other suggestions? Help? Suicide booths locations?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply