24
2011
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 >
Description:
Cluster resource ‘SQL Server (
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:HKEY_LOCAL_MACHINE\Cluster\Resources\
\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
VirtualServerNameValue 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 >
VirtualServerNameValue 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.

Related Posts
Leave a comment
Subscribe to this blog via Email
Old Posts
- November 2017 (3)
- October 2017 (4)
- September 2017 (2)
- May 2017 (1)
- April 2017 (1)
- July 2016 (3)
- May 2016 (1)
- April 2016 (1)
- February 2016 (2)
- January 2016 (1)
- October 2015 (1)
- September 2015 (1)
- August 2015 (1)
- July 2015 (2)
- June 2015 (3)
- April 2015 (1)
- March 2015 (1)
- December 2014 (1)
- September 2014 (2)
- April 2014 (1)
- January 2014 (3)
- October 2013 (2)
- September 2013 (2)
- August 2013 (4)
- July 2013 (1)
- June 2013 (2)
- May 2013 (5)
- April 2013 (3)
- March 2013 (1)
- February 2013 (9)
- January 2013 (11)
- December 2012 (14)
- November 2012 (3)
- October 2012 (4)
- July 2012 (2)
- June 2012 (3)
- May 2012 (2)
- April 2012 (8)
- March 2012 (6)
- February 2012 (3)
- January 2012 (1)
- December 2011 (5)
- November 2011 (8)
- October 2011 (5)
- September 2011 (3)
- August 2011 (3)
- July 2011 (3)
- May 2011 (1)
- November 2010 (1)
Tags
Calender
M | T | W | T | F | S | S |
---|---|---|---|---|---|---|
« Nov | ||||||
1 | 2 | 3 | ||||
4 | 5 | 6 | 7 | 8 | 9 | 10 |
11 | 12 | 13 | 14 | 15 | 16 | 17 |
18 | 19 | 20 | 21 | 22 | 23 | 24 |
25 | 26 | 27 | 28 | 29 | 30 | 31 |
View Post by Categories
Recent Articles
- Setting up Always ON Availability Group in Multi Subnet Cluster – Recommendations
- Configuring Replication with Always ON Availability Group
- Login failed for user ‘DOMAIN\COMPUTER$’. Reason: Could not find a login matching the name provided. [CLIENT: ]
- Modern Servicing Model (Service Pack and Cumulative Updates) for SQL Server 2017 and onwards
- Fix: SSMS 2012 opening Debug window when pressing F5