I am having a problem failing over in my SQL cluster. One node is running Windows 2000 and the other (the new one) is running Windows 2003.
Both are running SQL 2000 SP3. I am unable to fail over one instance. It gives the following errors:

Let's call my servers SQL1 (Windows 2003) and SQL2 (Windows 2000).

On SQL1, in my Application Log: I see this when I try to fail from
SQL2 to SQL1:

Event ID: 17052
Description: [sqsrvres] ODBC sqldriverconnect failed

then

Event ID: 17052
Description: [sqsrvres] checkODBCConnectError: sqlstate = 08001;
native error = 6; message = [Microsoft][ODBC SQL Server Driver][TCP/IP
Sockets] Specified SQL server not found.

then

Event ID: 17052
Description: [sqsrvres] ODBC sqldriverconnect failed

then

Event ID: 17052
Description: [sqsrvres] checkODBCConnectError: sqlstate = 01000;
native error = 2afc; message = [Microsoft][ODBC SQL Server
Driver][TCP/IP Sockets] Specified SQL server not found.

then some more of the same errors when retrying before it aborts and
revert back to SQL2.

What do you suggest? These are test servers. I can do almost anything
I want on them, but I need to be able to have an efficient upgrade
plan when I'll do this on my production servers (that is with very few
downtime).

Thanks!

How did you regain your lost node (Your question below)?

HTH
is running Windows 2003.

If you didn't properly evict the node from SQL (not just from Windows)
before readding it, you could have problems with old regkeys interfering.
But you should also check the aliases, you may have added a named pipes
alias to complete the install on the Win03 node that needs to be removed.

Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.