Error Renaming Server with SQL Server 2005 CTP December 2004
I have just recovered from an interesting error with SQL Server 2005 CTP December 2004. Part of the project at a customer is to "Smoke Test" the in-house applications against SQL Server 2005 as-is. To do this, we built a SQL Server 2005 server to be identical to an existing non-production SQL2000 server, swapped servers(rename), and re-pointed the applications for testing.
While renaming servers I ran into a problem where SQL Server 2005 would start, would not allow user connections of any kind, and quickly stopped. The only way I found to recover from it was to move the databases out of the install path and reinstall.
The error reported by SQL Server was TDSSNICLIENT INITIALIZATION FAILURE. Error: 17182, Severity: 16, State: 1. There were subsequent errors, but this was the first in the chain.
I could find no documentation on the error on the net or the documentation with the Beta. To recover, I reinstalled and moved the databases (master and all) into the install path and restarted SQL Server. I then performed the usual sp_dropserver/sp_addserver steps of renaming a server.
All is well, but I thought I would post this just in case anyone else runs across it.
Jon Baker
While renaming servers I ran into a problem where SQL Server 2005 would start, would not allow user connections of any kind, and quickly stopped. The only way I found to recover from it was to move the databases out of the install path and reinstall.
The error reported by SQL Server was TDSSNICLIENT INITIALIZATION FAILURE. Error: 17182, Severity: 16, State: 1. There were subsequent errors, but this was the first in the chain.
I could find no documentation on the error on the net or the documentation with the Beta. To recover, I reinstalled and moved the databases (master and all) into the install path and restarted SQL Server. I then performed the usual sp_dropserver/sp_addserver steps of renaming a server.
All is well, but I thought I would post this just in case anyone else runs across it.
Jon Baker

0 Comments:
Post a Comment
<< Home