SQL Server Performance

Failover fails -> sqldriverconnect failed

Discussion in 'SQL Server Clustering' started by acki4711, May 9, 2007.

  1. acki4711 Member

    Hi all,<br />Have just installed sql2k + sp4 on a 2 node a/p scenario.<br />All worked fine exept the failover :-(<br />Getting 8 entries in application log with same EventID & source:<br /><br />EventID: 17052<br />Source: MSSQLSERVER<br />1)[sqsrvres] StartResourceService: OpenService (MSSQLSERVER) failed. Error: 0<br />2)[sqsrvres] ODBC sqldriverconnect failed<br />3) [sqsrvres] checkODBCConnectError: sqlstate = 08001; native error = 11; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.<br />4) [sqsrvres] checkODBCConnectError: sqlstate = 01000; native error = 2; message = [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).<br />5) [sqsrvres] ConnectToSQL: service stopped while trying to connect to server.<br />6) [sqsrvres] OnlineThread: Error connecting to SQL Server.<br />7) [sqsrvres] OnlineThread: service stopped while waiting for QP.<br /><img src='/community/emoticons/emotion-11.gif' alt='8)' /> [sqsrvres] OnlineThread: Error 1 bringing resource online.<br /><br />What's going wrong here ??<br />TIA<br />acki<br />
  2. satya Moderator

    See whether you are trying the following:
    You are connecting to a SQL Server named instance by using TCP/IP sockets.
    IPSec policy is enabled on the client domain.
    IPSec policy is not enabled on the server domain.


    Ensure alias has been defined for that virtual server instance,http://www.sql-server-performance.com/sqlserver2000_clustering_install_part3.asp fyi.

    Satya SKJ
    Microsoft SQL Server MVP
    Writer, Contributing Editor & Moderator
    http://www.SQL-Server-Performance.Com
    This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
  3. acki4711 Member

    satya,
    If sql server (default instance) runs on node 1 both nodes (1+2) can connect.
    If I failover to node 2 sql server fails to come online (errors below).
    So I think it has nothing to do with named instance or IPSec.

    acki
  4. satya Moderator

    Have you checked the ALIAS on node 2 to connect?

    Satya SKJ
    Microsoft SQL Server MVP
    Writer, Contributing Editor & Moderator
    http://www.SQL-Server-Performance.Com
    This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
  5. acki4711 Member

    satya,
    if you mean with ALIAS the sql server cluster name (that's the name I'm using during installation (not nt cluster name)) it works on both notes.
  6. satya Moderator

    Ok, I still see problem on the second node and this might happen if the MDAC version mismatches, also ensure the service pack installation has been succeeded on both the nodes. KBAhttp://support.microsoft.com/kb/254321 fyi

    Satya SKJ
    Microsoft SQL Server MVP
    Writer, Contributing Editor & Moderator
    http://www.SQL-Server-Performance.Com
    This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
  7. acki4711 Member

    The following steps resolved the problem:

    - deinstalling sql
    - deinstalling cluster on both nodes
    - reinstalling cluster
    - reinstalling sql + sp

    HTH
    acki

  8. MohammedU New Member

    Thanks for sharing your solution...

    You did all over again except the OS intallation....

    MohammedU.
    Moderator
    SQL-Server-Performance.com

    All postings are provided “AS IS” with no warranties for accuracy.
  9. acki4711 Member

    MohammedU
    Yes I did all over again exept OS installation.
    After deinstalling sql server I did some manual cleanup in the registry as well.
    (deleting all keys deinstaller did not removed)

    HTH
    acki
  10. satya Moderator

    If the uninstall operation hasn't removed the registry they might be during the reboot, even though if they exists then its an existing problem when installed previously, anyway you have resolved the issue this is not any more.

    Satya SKJ
    Microsoft SQL Server MVP
    Writer, Contributing Editor & Moderator
    http://www.SQL-Server-Performance.Com
    This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.

Share This Page