Server renamed > big problems

[MBreve]

We had a problem free SQL Server 200 running on a machine call OLD with the instance of SLIM.

I could connect the enterprise manager to OLD\SLIM and everything worked fine.

The the name OLD was changed to NEW and the problems began.

The server is still running and users can connect without problem.

But, In the Enterprise manager, I can only connect to OLD\SLIM. But in the SQL Server servicemanager it does list the OLD\SLIM name but can't connect to it. It also shows the NEW\SLIM name and I can connect to this one and it shows to be running.

So, in the Enterprise manager OLD\SLIM is running, but in the service manager NEW\SLIM is running.

In Computer Management (MMC) it lists NEW\SLIM but can't connect to it.

The main problem is the SQL Server Agent won't run! It can't connect to NEW\SLIM.

Any idea why it is still showing its old name?

I'm using Windows authentication to connect to the server.

 

[Corran007]

did you rerun the server install? when you change the name you should rerun the server so it changes the name for sqlserver. in eithe this or the sql programming forum there was a discusion on this if you need more info

 

[MBreve]

Re-installing is not my favorite option. The I would go back 3 servicepacks and then re-apply the servicepack.

My current strategy is nog to modify the registry by hand to replace all occurrences of OLD to NEW. There are still quite a few entries referring to the old name.

I have no idea if this will work but I prefer this to a re-installation.

 

[Corran007]

it doesnt really reintall it though, it just syncs it up the names correctly.

 

[MBreve]

I don't get this.

Re-installing doesn't really re-install?

I could imagine an intelligent installation that doesn't overwrite same or newer files. But since a servicepack is applied to the original installation I doubt if this will work well?

But then again, if syncing the name is all it does I guess I can do that by hand just as well.

The only proble I see is when the old name is stored sowhery encrypted or coded which would result in an error.

Another detail is that the physical server is 100 miles away from here. So for a re-installation I have to drive back and forth.

 

[JamesLean]

What Corran007 is referring to is simply to rerun the setup program. If it detects the machine name has changed then it will make the necessary changes and then quit without actually "reinstalling" anything.

Alternatively look up sp_addserver and sp_dropserver in BOL for information on how to set the local server name after a machine name change.

--James

 

[Corran007]

ya thats what i meant. its to early...

you should also thing about having a remote viewing software on your database servers for times like this.

 

[MBreve]

>>sp_addserver and sp_dropserver <<

I'm not sure but I think this is what got me into this trouble.

I simulated a server rename at home and all went well. But in production, a colleague ran these two SP's and after that, the trouble began.

>>If it detects the machine name has changed then it will make the necessary changes and then quit without actually &quot;reinstalling&quot; anything.<<

Sounds interesting enough to try. I think I'll try this if the registry edit doesn't work.

 

[SQLBill]

Re-running the install disk is causing it to do a 'repair' not a true reinstall.


-SQLBill

 

[MBreve]

Spend 8 hours last firday to get this server up & running again.

Modifying the registry went well but didn't solve the problem.

So I tried the re-install option but that reulted in a error and after that I couldn't get the server online again.

No other option than to hop in the car and drive the 100 miles to this machine.

I did get the machine running again but could not connect to it with the Enterprise Manager.

In a final desperate attempt we renamed the server to the OLD name and everything worked again!

Retried to rename the server again but with the same result, no connection.

The server is currently running under it's OLD name and we plan to rebuild the server from scratch with the NEW name.

 

[Corran007]

before you do that, try this again. you may have to do it at the physical server.

dicon it from the domain.
rename server and reboot
rerun sqlserver setup so it recognizes the new name
readd to domain.

those are the steps we have followd for renaming a system and they have worked well. for us anyhow.

 

[SQLBill]

One other thing to think about...

you said

free SQL Server 200

Are you using an evaluation copy? With no licenses? You may have run out of time on the evaluation. Or renaming the server may be a no-no with an evaluation copy.

-SQLBill