![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a problem with my SQL cluster. One Windows 2000 server had a disk crash recently so I decided to reinstall it all under Windows 2003. So now I have the new Windows 2003 server and the good old Windows 2000 server. Let's call my servers SQL1 (Windows 2003) and SQL2 (Windows 2000). I installed the new node on my 2003 server and applied SP3a patch. But now I am unable to failover to SQL1 (Physical Disk, IP Address and Network Name transfer, but SQL Server will not transfer). The Quorum resources transfer without problem. I closely followed the required network configuration at http://support.microsoft.com/?id=258750 but it does not help. All servers rebooted will not help either. SP3 has been applied on both servers. A re-install of the SQL node on SQL1 has been attempted with no luck... 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 could be wrong with the 2003 server? Thanks! Paul |
![]() |
| Thread Tools | |
| Display Modes | |
| |