none
SQL 2005 Clustering Issues

    Question

  • Hi all,

    I'm having issues with my SQL 2005 SP5, CU5 cluster.  I swapped out a clustered disk and restarted SQL and now it's unable to come back up.  The errors that I'm getting are:


    2008-06-13 20:21:25.82 Server      Error: 26054, Severity: 16, State: 1.
    2008-06-13 20:21:25.82 Server      Could not find any IP address that this SQL Server instance depends upon.  Make sure that the cluster service is running, that the dependency relationship between SQL Server and Network Name resources is correct, and that the IP addresses on which this SQL Server instance depends are available.  Error code: 0x103.
    2008-06-13 20:21:25.84 Server      Error: 17182, Severity: 16, State: 1.
    2008-06-13 20:21:25.84 Server      TDSSNIClient initialization failed with error 0x103, status code 0xa.
    2008-06-13 20:21:25.84 Server      Error: 17182, Severity: 16, State: 1.
    2008-06-13 20:21:25.84 Server      TDSSNIClient initialization failed with error 0x103, status code 0x1.
    2008-06-13 20:21:25.84 Server      Error: 17826, Severity: 18, State: 3.
    2008-06-13 20:21:25.84 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2008-06-13 20:21:25.84 Server      Error: 17120, Severity: 16, State: 1.
    2008-06-13 20:21:25.84 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.



    I've Googled around and was unable to find another.  VIA is disabled (fairly common suggestion when Googling) and I have my clustered SQL Server resource dependent upon the network name.  The name/ip/disks are fine, but SQL refuses to start.  I'm not really sure what do to other than reroll the default instance.

    Any help would be much appreciated.  Thanks!
    Saturday, June 14, 2008 12:40 AM

Answers

  • OK, I have a fix.  When the SQL Server and Agent resources were added back in to the cluster it missed out the registry keys below.  You'll have to update the highlighted parts to match your servers:

     

    [HKEY_LOCAL_MACHINE\Cluster\Resources\xxxxxxxx-nnnn-nnnn-nnnn-xxxxxxxxxx111\Parameters]
    "VirtualServerName"="VirtualServerName"
    "InstanceName"="InstanceName"

     

    [HKEY_LOCAL_MACHINE\Cluster\Resources\xxxxxxxx-nnnn-nnnn-nnnn-xxxxxxxxx222\Parameters]
    "VirtualServerName"="VirtualServerName"
    "InstanceName"="InstanceName"

    "VerboseLogging"=dword:00000000
    "SqlDumperDumpFlags"=dword:00000000
    "SqlDumperDumpPath"=""
    "SqlDumperDumpTimeOut"=dword:00000000

     

    [HKEY_LOCAL_MACHINE\Cluster\Resources\xxxxxxxx-nnnn-nnnn-nnnn-xxxxxxxxx222\RegSync]
    "00000007"="Software\\Microsoft\\Microsoft SQL Server\\MSSQL.2\\CPE"
    "00000001"="Software\\Microsoft\\Microsoft SQL Server\\MSSQL.2\\Replication"
    "00000002"="Software\\Microsoft\\Microsoft SQL Server\\MSSQL.2\\SQLserverAgent"
    "00000003"="Software\\Microsoft\\Microsoft SQL Server\\MSSQL.2\\Cluster"
    "00000004"="Software\\Microsoft\\Microsoft SQL Server\\MSSQL.2\\MSSQLSERVER"
    "00000005"="Software\\Microsoft\\Microsoft SQL Server\\MSSQL.2\\PROVIDERS"
    "00000006"="Software\\Microsoft\\Microsoft SQL Server\\MSSQL.2\\SQLServerSCP"

    where

    xxxxxxxx-nnnn-nnnn-nnnn-xxxxxxxxxx111 is the key for SQL Agent for your instance

    xxxxxxxx-nnnn-nnnn-nnnn-xxxxxxxxxx222 is the key for SQL Server for your instance

    MSSQL.2 is the instances folder - this relates to the registry key under HKLM - MSSQL.2 as this was the second instance on this cluster.

     

    Once I had added these keys back into the registry on both nodes SQL started correctly and failed over properly.

    Hope this is a help to anyone else with the same problem.

    Friday, June 20, 2008 12:08 PM

All replies

  • Same problem here.  Removed the SQL and disk Resources from the cluster and then added them back in (to pick up new disk id).  Everything comes up fine except the SQL Server and SQL Agent.  I checked all the dependancies against another clustered SQL server and they are the same.  Error log has the same codes as above.  Any ideas?

     

    Sunday, June 15, 2008 7:23 PM
  • OK, I have a fix.  When the SQL Server and Agent resources were added back in to the cluster it missed out the registry keys below.  You'll have to update the highlighted parts to match your servers:

     

    [HKEY_LOCAL_MACHINE\Cluster\Resources\xxxxxxxx-nnnn-nnnn-nnnn-xxxxxxxxxx111\Parameters]
    "VirtualServerName"="VirtualServerName"
    "InstanceName"="InstanceName"

     

    [HKEY_LOCAL_MACHINE\Cluster\Resources\xxxxxxxx-nnnn-nnnn-nnnn-xxxxxxxxx222\Parameters]
    "VirtualServerName"="VirtualServerName"
    "InstanceName"="InstanceName"

    "VerboseLogging"=dword:00000000
    "SqlDumperDumpFlags"=dword:00000000
    "SqlDumperDumpPath"=""
    "SqlDumperDumpTimeOut"=dword:00000000

     

    [HKEY_LOCAL_MACHINE\Cluster\Resources\xxxxxxxx-nnnn-nnnn-nnnn-xxxxxxxxx222\RegSync]
    "00000007"="Software\\Microsoft\\Microsoft SQL Server\\MSSQL.2\\CPE"
    "00000001"="Software\\Microsoft\\Microsoft SQL Server\\MSSQL.2\\Replication"
    "00000002"="Software\\Microsoft\\Microsoft SQL Server\\MSSQL.2\\SQLserverAgent"
    "00000003"="Software\\Microsoft\\Microsoft SQL Server\\MSSQL.2\\Cluster"
    "00000004"="Software\\Microsoft\\Microsoft SQL Server\\MSSQL.2\\MSSQLSERVER"
    "00000005"="Software\\Microsoft\\Microsoft SQL Server\\MSSQL.2\\PROVIDERS"
    "00000006"="Software\\Microsoft\\Microsoft SQL Server\\MSSQL.2\\SQLServerSCP"

    where

    xxxxxxxx-nnnn-nnnn-nnnn-xxxxxxxxxx111 is the key for SQL Agent for your instance

    xxxxxxxx-nnnn-nnnn-nnnn-xxxxxxxxxx222 is the key for SQL Server for your instance

    MSSQL.2 is the instances folder - this relates to the registry key under HKLM - MSSQL.2 as this was the second instance on this cluster.

     

    Once I had added these keys back into the registry on both nodes SQL started correctly and failed over properly.

    Hope this is a help to anyone else with the same problem.

    Friday, June 20, 2008 12:08 PM
  • This seems to be the solution to my problem, but how do you find the correct GUID for the Agent/Service for the specific instance?   Is this obvious?
    --You bet I ate it--
    Monday, October 11, 2010 4:38 AM
  • Got it sometime in the night.   After reading through the contents of the KEY/GUIDs there is one for SQL AGent and one for SQL Server.   Makes sense.   Thanks!
    --You bet I ate it--
    Monday, October 11, 2010 12:55 PM
  • Hi, Saw your post on the KEY/GUIDs of SQl Server and Agent. Just wondering how were you able to get/generate the said keys... Thanks in advance.
    Thursday, April 28, 2011 2:41 AM
  • I am having the same Sitution. I am installing SQL Server 2005 on Windows Server 2008 R2. I am having the same issue as mentioned above.

    Your help is highly appreciated.


    Hema
    Wednesday, November 23, 2011 10:08 PM
  • Very old thread but i would like to add how I got it fixed for me.

    'SQL server service'  resource in failover cluster manager - Right click - Properties - Dependency -  SQL Instance IP was mentioned instead of SQL instance network name. Changed it to network name, and voila! service was up and I was wondering i couldn't find it before. Why i wasted my couple of hours.

    Regards

    Ganesh

    Tuesday, September 20, 2016 5:39 PM