SQL SERVER 2005 Resource Fails to come online on cluster after SQL Resource removed and re-added in cluster group

In my case System admin accidently deleted SQL Server 2005 SQL Service resource from SQL cluster group (when trying to remove a disk from cluster) and re-added again but after re-adding SQL server failed to come up and following error noted in SQL Error log,


Error: 26054, Severity: 16, State: 1.

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.

Error: 17182, Severity: 16, State: 1.

TDSSNIClient initialization failed with error 0x103, status code 0xa.

Error: 17182, Severity: 16, State: 1.

TDSSNIClient initialization failed with error 0x103, status code 0x1.

Error: 17826, Severity: 18, State: 3.

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.

Error: 17120, Severity: 16, State: 1.

SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.



After initial investigation found a useful link on msft blogs, http://blogs.msdn.com/b/sqlserverfaq/archive/2009/01/13/sql-server-2005-resource-fails-to-come-online-on-cluster-after-changing-the-san-drive-to-add-more-disk-space.aspx and issue found to be same i.e. registries were missing,


When checked found following registries missing,


Note: Before doing any changes to registries, please backup all registries using registry export functionality and remember if something wrongly done then it may crash your installation too which require you to reinstall SQL Server, so change options wisely and only if similar situation occurs to you, refer MSDN link shared above for further details.


Registry Location:


InstanceName and VirtualServerName values are missing from the following Registry keys:

HKLM\Cluster\Resources\<SQL Server GUID>\Parameters

HKLM\Cluster\Resources\<SQL Agent GUID>\Parameters


Also Regsync Key and all values present inside found to be missing from following registry key,

HKLM\Cluster\Resources\<SQL Server GUID>\


These registry keys are used by the cluster administrator to connect and start the sql server service. So the Cluster Administrator was not able to connect and start the sql server resource and hence we receive the above error,


To fix the issue, add following registry values in the Parameters registry key:

For a named instance of SQL Server:

• InstanceName

Value Name: InstanceName

Value Type: REG_SZ

Value Data: <instance name of the named instance>


• VirtualServerName

Value Name: VirtualServerName

Value Type: REG_SZ

Value Data: <Virtual server name of the instance>


Once registry keys are added, we were able to bring the sql server online on Node1; similarly added for SQL Server agent services.


But on failing instance over to Node2 the above registry keys found to be missing, so we added missing keys and rebooted both the servers of the clusters. After rebooting the server the sql server resources came online fine without any errors


Apart from this found RegSync keys also to be missing (first created RegSync key and then added all values inside on both Node1 and Node2), so added all of them manually based on instance, please find screenshots below which are taken after fixing the issue, will give you some idea.


Note: To identify SQL Server GUID you need to look into all registry folders, and from TYPE value you can distinguish if it is SQL Server Services key or SQL Server Agent Key, for e.g.


Below is ideal situation when all keys are present,


Value in Parameters Key,


Values in RegSync Key,


Note: In your case, you can identify MSSQL.1 or MSSQL.2 by going to following registry, (in your case, .<int> will vary, identify and fill appropriately)

HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL.1




For SQL Server agent, keys are found as, (it doesn’t have RegSync Key),



Parameter values,



Final outcome was SQL services are online and it is advisable that never remove SQL services from cluster group unless you are planning to reinstall the product. Moreover, if you are planning to remove any SQL Services dependent resources (like SAN disk) then do remove dependencies first and then only remove resource from cluster else Cluster will prompt you to remove all dependencies and if accidentally selected yes then you may become victim of above.

Suppose you need to remove Disk R: from cluster then remove dependency first by going to cluster admin > Cluster group > Select SQL Server resource > right click properties > Select dependencies tab > Modify > Move disk R from right pane to left pane> Ok > OK


It may prompt you with error saying resource is online hence unable to remove resource, so stop service first and then remove dependency resource.


Hope it helps!


Some other troubleshooting links (may work if you see any one of error instead of all in your sql error log),






Download PDF

About the Author: Nitin G

Indian born, trekker, biker, photographer, lover of monsoons. I've been working full time with SQL Server since year 2005 and blogs to post the content aquired during my research on new topics or fixing issues faced by me as a DBA while working in different kind of projects, hope some of my posts may helps others in SQLDBA community. Everything you read on my blog is my own personal opinion and any code is provided "AS-IS" with no warranties!

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 254 other subscribers

Translate this blog!



August 2020
« Nov    

View Post by Categories

%d bloggers like this: