Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

renaming a server Expand / Collapse
Author
Message
Posted Wednesday, March 4, 2009 5:47 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 1:28 AM
Points: 1,673, Visits: 2,108
SELECT @@SERVERNAME AS 'Server Name' returns 'OldName'

I run

sp_dropserver [OldName]
GO
sp_addserver [NewName], local
GO

returns error

Msg 15190, Level 16, State 1, Procedure sp_dropserver, Line 56
There are still remote logins or linked logins for the server 'OldName'.
Msg 15028, Level 16, State 1, Procedure sp_MSaddserver_internal, Line 89
The server 'NewName' already exists.

I run

sp_dropremotelogin [OldName]
GO

returns error

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 'OldName'.

I think the server has been renamed by our network guys while replication is set up.

Can anyone advise me how to drop the remote logins or linked logins and rename the server

Thanks in advance
Post #668060
Posted Wednesday, March 4, 2009 6:08 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, October 15, 2010 8:23 AM
Points: 371, Visits: 437
I had an issue like this before so I did a quick search to find what helped me and I realized it was not the same. But I ended up here.

Check page 77

http://www.quest.com/quest_site_assets/whitepapers/sql_server_ebook_a_practical_guide_to_backup,_recovery,_and_troubleshooting_(part_2).pdf
Post #668082
Posted Wednesday, March 4, 2009 6:23 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 1:28 AM
Points: 1,673, Visits: 2,108
Thanks Jamie.

Trouble is the physical machine has been renamed.
when I try to disable replication I get the following error

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)
Post #668100
Posted Wednesday, March 4, 2009 6:30 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, October 15, 2010 8:23 AM
Points: 371, Visits: 437
I havn't run into this issue before so I'm not sure if I can provide any more help.. but the next things I would try is create an entry in the hosts file on the server with the old hostname and point it to localhost or the server IP. Then try and remove it in SSMS on the server.
Post #668109
Posted Thursday, March 5, 2009 4:47 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 1:28 AM
Points: 1,673, Visits: 2,108
I was unable to resolve this.
Ended up reinstalling SQLSever while nobody was looking, and restored the databases.
I was lucky this time, we had a maintenance window, but if anyone knows how it should be done I would be gratefull if you could share it with me.
Thanks
Ian
Post #669084
Posted Thursday, March 5, 2009 5:58 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, May 22, 2014 7:04 AM
Points: 1,688, Visits: 8,766
Was sql server restarted after the appserver command execution was done?

The local definition takes effect only after the server is shut down and restarted. Only one local server can be defined in each server.

http://msdn.microsoft.com/en-us/library/ms174411.aspx

MJ
Post #669127
Posted Thursday, March 5, 2009 7:41 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, January 7, 2010 2:19 PM
Points: 112, Visits: 66
MJ hit on it, after you rename SQL Server, you MUST restart the server.
Post #669223
Posted Thursday, March 5, 2009 2:23 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 1:28 AM
Points: 1,673, Visits: 2,108
The server was renamed months ago, the server has been shut down and restarted twice in Feb, so i would have to go with in this instance that is not the answer.
Thanks all the same.
Ian
Post #669686
Posted Wednesday, April 15, 2009 1:12 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, May 14, 2014 3:03 PM
Points: 100, Visits: 797
Hi, this is my first post. I have 15 days as a DBA.

I had the same issue and just solve it. I add the 'old server' alias in configuration manager, then disabled publication, and after that exec sp_dropserver and SP_ADDSERVER commands, drop 'old server' alias in configuration manager, and it worked. Sorry for my english. I hope this helps.

Post #697839
Posted Friday, April 17, 2009 9:19 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Today @ 1:28 AM
Points: 1,673, Visits: 2,108
Welcome to the group.
Thanks for the tip, I will keep it in mind if this reoccurs
Post #699515
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse