Problem : 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
Problem Description
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:
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:
SQL Server <SQLServer>: [sqsrvres] Unable to read the ‘VirtualServerName’ property. Error: d.
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:
server Error: 17826, Severity: 18, State: 1
server Could not set up Net-Library ‘SSNETLIB’..
spid13 Starting up database ‘DB1′.
spid12 Starting up database ‘DB2′.
spid14 Starting up database ‘DB3′.
server Error: 17059, Severity: 18, State: 0
server Operating system error -1073723998: ..
server Unable to load any netlibs.
server SQL Server could not spawn FRunCM thread.
Problem Resolution
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:
- Click Start, click Run, type regedit, and then click OK.
- In Registry Editor, locate and select the following registry key: HKEY_LOCAL_MACHINE\Cluster\Resources\<GUID>\Parameters
- 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
- For a default instance of SQL Server: 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>
- For a named instance of SQL Server: VirtualServerName
- Value Name: VirtualServerName
- Value Type: REG_SZ
- Value Data: <Name of the virtual SQL server>
- 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.
Related Posts
- Error while installing the SQL Server 2000 Virtual Instance
- Cannot install SQL Server cluster on a computer that runs Microsoft Windows Server 2003
- SQL Server 2000 Maintenance Jobs Failed with Error 22029
- Consistency Errors in MS SQL Server 2000
- Transactions in SQL- Server 2008
Tags: sql server 2000, SQL Server 2005, SQL Server Cluster Error, SQL Server Cluster Resource Failed




