Cluster resource ‘SQL Server ()’ in Resource Group ‘‘ failed!

While investigating a cluster resource offline issue, came across following three errors in windows system event log, cluster log and SQL error log respectively,

Error message 1

Source: ClusSvc
Category: Failover Mgr
Type: Error
Event ID: 1069
User: N/A
Computer: < Computer Name >

Cluster resource ‘SQL Server ()’ in Resource Group ‘‘ failed.

Error message 2

Error 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

< Date Time > server Error: 17826, Severity: 18, State: 1
< Date Time > server Could not set up Net-Library ‘SSNETLIB’..
< Date Time > spid13 Starting up database ‘< db_name >‘.
< Date Time > server Error: 17059, Severity: 18, State: 0
< Date Time > server Operating system error -1073723998: ..
< Date Time > server Unable to load any netlibs.
< Date Time > server SQL Server could not spawn FRunCM thread.

To fix this, found following link: http://support.microsoft.com/kb/883732 , it is exactly the resolution of issue which I faced,

Resolution which I applied:

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:

Create the following registry values in the
registry key:

For a default instance of SQL Server: InstanceName

Value Name: InstanceName
Value Type: REG_SZ

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 >

Value Name: VirtualServerName
Value Type: REG_SZ
Value Data: < Name of the virtual SQL server >

Quit Registry Editor.

After doing above, when I tried to bring SQL cluster services online, it came online and issue resolved.

Useful article on how to create a registry key: http://support.microsoft.com/kb/810056
Clustered SQL Server do’s, don’ts, and basic warnings: http://support.microsoft.com/kb/254321

Once above is done, make sure that FTE services, etc are running fine, because sometime other tools like legato backup depends upon MSSEARCH services which are inturn depend on MSFTE services to determine SQL server state, if those registries are also missing then fix at that instant only otherwise it may lead to complex situations of backups not working (happened in my case and we need to change the backup methodology because resolution was to rebuild Cluster which was not possible in my case due to critical environment).

Link on resolving the Full text error issue,

Error: SQL Cluster Resource ‘Full Text’ failed

Solution: http://support.microsoft.com/kb/304282 , http://support.microsoft.com/kb/810056

As per Microsoft:

If you have an issue that requires you to rebuild or reinstall Full text search on a SQL Server 2000 failover cluster instance or on a SQL Server 2005 failover cluster instance, a complete uninstall and reinstall of the SQL Server failover cluster instance is the only supported recovery method.

Final Verdict: When such registry error occurs, examine the state of all SQL registries and fix at same time instead of later experiencing issues, it is utmost important that end to end fix of problem should be done.

Download PDF

Related Posts

About the Author: Nitin Garg

Indian born, trekker, biker, photographer, lover of monsoons... I love to blog the topics I research and find useful for self or online community to save time and energy :) Everything you read on my blog is my own personal opinion!

Leave a comment

Subscribe to this blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 264 other subscribers

Translate this blog!



January 2021
« Nov    

View Post by Categories

%d bloggers like this: