A SQL Server cluster resource goes to a "failed" state when you try to bring the resource online in SQL Server 2005 or in SQL Server 2000 (883732)


The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard Edition
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS


When you try to bring a SQL Server cluster resource online for a virtual instance of Microsoft SQL Server 2005 or of Microsoft SQL Server 2000, you may notice the following behavior:
  • The SQL Server cluster resource goes to a "failed" state and does not come online.
  • You receive a combination of the following error messages on the computer that owns the SQL Server cluster resource.

    Error message 1

    An event that is similar to the following is in the system event log:


    Date: 08/05/2004
    Time: 1:11:19 AM
    Source: ClusSvc
    Category: Failover Mgr
    Type: Error
    Event ID: 1069
    User: N/A
    Computer: <Computer Name>

    Description:
    Cluster resource 'SQL Server (<SQL Server instance name>)' in Resource Group '<Cluster group name>' failed.

    Error message 2

    An error message that is similar to the following is in the Cluster log file:

    00000644.00000944::2003/11/30-18:11:30.360 SQL Server <SQLServer>: [sqsrvres] Unable to read the 'VirtualServerName' property. Error: d.

    00000644.00000944::2003/11/30-18:11:30.360 SQL Server <SQLServer>: [sqsrvres] OnlineThread: Error d bringing resource online.


    Error message 3

    Error messages that are similar to the following are in the SQL Server error log file:

    2003-11-30 17:00:37.27 server Error: 17826, Severity: 18, State: 1
    2003-11-30 17:00:37.27 server Could not set up Net-Library 'SSNETLIB'..
    2003-11-30 17:00:37.27 spid13 Starting up database 'SPB'.
    2003-11-30 17:00:37.27 spid12 Starting up database 'BD_MTA'.
    2003-11-30 17:00:37.27 spid14 Starting up database 'BD_SPF'.
    2003-11-30 17:00:37.27 server Error: 17059, Severity: 18, State: 0
    2003-11-30 17:00:37.27 server Operating system error -1073723998: ..
    2003-11-30 17:00:37.27 server Unable to load any netlibs.
    2003-11-30 17:00:37.27 server SQL Server could not spawn FRunCM thread.

CAUSE

The resource-specific registry keys that correspond to the SQL Server cluster resource that you are trying to bring online are missing. This problem also occurs if the values that correspond to the resource-specific registry keys are not correct.

RESOLUTION

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this problem, you must manually re-create the resource-specific registry keys that correspond to the SQL Server cluster resource. To do this, follow these steps:

  1. Click Start, click Run, type Regedit, and then click OK.
  2. In Registry Editor, locate and select the following registry key:

    HKEY_LOCAL_MACHINE\Cluster\Resources\<GUID>\Parameters
  3. Create the following registry values in the Parameters registry key:

    For a default instance of SQL Server:
    • InstanceName

      Value Name: InstanceName
      Value Type: REG_SZ
      Value Data: MSSQLSERVER
    • VirtualServerName

      Value Name: VirtualServerName
      Value Type: REG_SZ
      Value Data: <Name of the virtual SQL server>
    For a named instance of SQL Server:
    • InstanceName

      Value Name: InstanceName
      Value Type: REG_SZ
      Value Data: <SQL Server instance name corresponding to the virtual server>
    • VirtualServerName

      Value Name: VirtualServerName
      Value Type: REG_SZ
      Value Data: <Name of the virtual SQL server>
  4. Quit Registry Editor.
After you create the resource-specific registry keys, you can bring the SQL Server cluster resource online successfully.

If you notice that a SQL Server Agent cluster resource cannot be brought online, you must create the same set of resource-specific keys that correspond to the SQL Server Agent cluster resource.

MORE INFORMATION

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

810056 You must use resouce-specific registry keys for SQL Server cluster resouces

Modification Type:MajorLast Reviewed:4/6/2006
Keywords:kbsql2005cluster kbRegistry kbtshoot kbResource kberrmsg kbEvent kbClustering kbprb KB883732 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.