The problem is that we have a Named instance of SQL Server 2005 in a 2 node cluster. While trying to bring the SQL Services online we get these error messages in the Application Event Log.
Application Event Log:
Event Type: Error
Event Source: MSSQL$SQL2k5
Event Category: (3)
Event ID: 19019
Date: 7/17/2009
Time: 7:12:00 AM
User: N/A
Computer: BLRS2R17-3
Description:
[sqsrvres] ODBC sqldriverconnect failed
Event Type: Error
Event Source: MSSQL$SQL2k5
Event Category: (3)
Event ID: 19019
Date: 7/17/2009
Time: 7:12:00 AM
User: N/A
Computer: BLRS2R17-3
Description:
[sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = ffffffff; message = [Microsoft][SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].
Event Type: Error
Event Source: MSSQL$SQL2k5
Event Category: (3)
Event ID: 19019
Date: 7/17/2009
Time: 7:12:00 AM
User: N/A
Computer: BLRS2R17-3
Description:
[sqsrvres] ODBC sqldriverconnect failed
Event Type: Error
Event Source: MSSQL$SQL2k5
Event Category: (3)
Event ID: 19019
Date: 7/17/2009
Time: 7:12:00 AM
User: N/A
Computer: BLRS2R17-3
Description:
[sqsrvres] checkODBCConnectError: sqlstate = HYT00; native error = 0; message = [Microsoft][SQL Native Client]Login timeout expired
Cause:
The cluster service is not able to Connect with Clustered Named instance of SQL Server. SQL Browser even though running is not actually listening for requests.
Note: The SQL Server Browser program runs as a Windows service. SQL Server Browser listens for incoming requests for Microsoft SQL Server resources and provides information about SQL Server instances installed on the computer.
Resolution:
We restarted the SQL Server Browser Service on both the nodes and after that SQL resource came online in cluster. :)
No comments:
Post a Comment