Windows 2000/2003 cluster problem

From: Paul Dube (pdube_at_clic.net)
Date: 04/02/04

  • Next message: frankm: "Services login policies and rights question" 
    Date: Fri, 02 Apr 2004 15:09:26 -0500

    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!

  • Next message: frankm: "Services login policies and rights question"

    Relevant Pages

    • SQL 2005 beta 2 SCSI HDD error
      ... I have a test box running windows 2003. ... installed SQL 2005 beta 2 on that same box without error. ... the SQL 2005 install is completed the first reboot after the install gives a ...
      (microsoft.public.sqlserver.setup)
    • RE: Cannot connect to Named Instance
      ... They have bounced around from it being a SQL Problem, to a network problem, ... > I'm having trouble connecting to a named instance on a SQL 2000 EE cluster ... > the problem only arises with remote clients. ... > from is running Windows XP SP2, ...
      (microsoft.public.sqlserver.clustering)
    • Re: Cannot Generate SSPI Context
      ... Sounds like you have a Kerberos issue at the domain level more than a SQL ... I can connect normally to SQL Server (running Windows ... Server 2003) from my PC (running Windows XP SP2) for around half to one ...
      (microsoft.public.sqlserver.connect)
    • Unable to Re-install SQL Reporting Services
      ... Running Windows ... Server 2003, SQL Server 2000 SP3, Windows Sharepoint ... Now it won't install back. ...
      (microsoft.public.sqlserver.server)
    • Re: Accessing SQL 2K from SQL 7
      ... I think) don't understand named instances. ... try creating an alias that includes specifying the port number. ... > We added a new SQL instance of SQL 2K - name XXX\AB ... > "Specified SQL Server not found" ...
      (microsoft.public.sqlserver.security)