February 18, 2002 at 3:51 pm
Hey all,
Our Systems guys ran into a problem that they thought they would solve by renaming the NT Computer Name for the box one of our SQL Servers sits on.
Naturally, now the SQL service can't start. I ran into this once before and I thought there was a relatively easy work around, but can't find anything right now.
Any tips? Links? suggestions?
Thanks,
JasonL
JasonL
February 18, 2002 at 4:44 pm
The SQL Server will need to be "renamed" in order for everything to be in order. However, unless I'm mistaken, the SQL Server service should still start, because the steps require SQL Server to be running. Have you looked at the service account which the service is running under? Perhaps it was running under a local user account (say OldComputerName\User) and that is the cause?
As for getting everything back in sync... In Books Online, there is information for renaming a server:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_afterinstall_5r8f.asp
If you look in the BOL that shipped with SQL Server (as opposed to Microsoft's web site), there is a mistake. It's covered by this knowledge base article:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q303774
Hope that helps.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
February 19, 2002 at 7:03 am
Thanks guys,
Yeah, I just panicked a little (didn't want to be here all night).
So far it just appears to an NT glitch - someone gave a new workstation the same name as our db server - this replaced our server registration in WINS and essentially kicked the server off of the domain.
It's not back up yet (waiting for the Net guys to get it back on the domain!) but I think Brian's right, since the server isn't on the domain any longer the service (most likely running under a domain user account - I should know ... but I'm new here!) probably can't log on. At least I hope it's that simple.
Thanks again,
JasonL
JasonL
February 19, 2002 at 7:42 am
If it's not on the domain, this is probably the issue. I'll keep my fingers crossed that it is as simple as this.
K. Brian Kelley
http://www.sqlservercentral.com/columnists/bkelley/
K. Brian Kelley
@kbriankelley
February 19, 2002 at 8:45 am
Ahhhh ... life is good.
Everything is back up, all just fine.
Yikes, did my heart skip a beat though when the systems guy came up to me last night and said "sorry, we corrupted your database, it's saying we have to re-install. Can I have the CD?" Handing the SQL CD's off to someone to re-install my server ... scary!
I had the vague recollection that renaming a server wasn't as bad as it seemed even on SQL 7. Once I read those links (Brian Knight's article was dead-on, rename the server and SQL 7.0 pops up a scary message saying the database is corrupt - re-run setup -- sounds worse than it is) , I was able to convice the systems guys they didn't need the SQL CD's - just get the server back to it's original name and re-registered on the domain/network.
Once the server was re-named back to it's original name, SQL (7.0) stopped squawking. The real problem was NT. First they had to get the name conflict flushed, then get the server re-registered on the domain. Then they had a real fun time getting WINS flushed and the server registered with WINS (apparently they'd renamed the two machines several times round-robin and piled up a dozen conflicting entries in WINS)
Thanks again.
JasonL
February 19, 2002 at 9:59 am
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply