Hi,

We have an active/passive cluster which was running fine for months. Then
last week the SQL cluster failed over to the 2nd node - we established what
the error was and fixed it. But now when we try to fail back to the 1st node
SQL server fails. The errors we get in the application log are

1. Event id: 17052 - [sqsrvres] ODBC sqldriverconnect failed.

2. Event id: 17052 - [sqsrvres] checkODBCConnectError: sqlstate = 08001;
native error = b;
message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]General network
error.
Check your network documentation.

3. Event id: 17052 - [sqsrvres] ODBC sqldriverconnect failed.

4. Event id: 17052 - [sqsrvres] checkODBCConnectError: sqlstate = 01000;
native error = fffe;
message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
(PreLoginHandshake()).

I've checked the network and all is fine there. Nothing has been changed
recently.

Does anyone have any idea why SQL is failing on the 1st node.

Any help would be much appreciated.

What was explicitly the error that you've fixed?

I was getting similiar messages in the log after a SQL
Server 2000 install on a new cluster. After re-installing
several times I eventually found the problem.

On the node that was failing I had configured a DNS server
in the TCP/IP properties on the Public Network, but that
DNS server was not available at the time. Removing the DNS
server entry fixed the problem.

Probably what was happening was that it was takeing so
long for the DNS lookup to fail that the SQL Server ODBC
connection attempt timed out.

I would verify that your first node can resolve names
correctly i.e. ping the SQL Virtual Server by name

Kevin