We have a SQL Server 2005 cluster with two nodes, one active and the other passive. We had to remove an 1 TB storage volume from the cluster and release it to the storage pool.
Before removing any cluster resource we need to remove the dependencies. To remove this drive we have to remove the dependency of this drive from SQL Server service. Here are the steps:
1. Open cluster administrator
2. Right click SQL Service and select Properties
3. Click Modify and remove the resource from Modify Dependencies window
4. Now we can go back to Cluster Administrator and delete the resource/drive volume.
If we delete the drive or resource without removing the dependency, the SQL Service might fail to start. The following errors might occur:
TDSSNIClient initialization failed with error 0x103, status code 0x1.
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.
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
The cause is that certain registry values that got deleted. In our case it was "parameters" and "RegSync" values that got deleted from the HKEY_LOCAL_MACHINE\Cluster\Resources\
For more information refer to this excellent post:
http://social.msdn.microsoft.com/Forums/en-US/sqldisasterrecovery/thread/af054e22-4b36-4793-a87d-120002ae215f
Before removing any cluster resource we need to remove the dependencies. To remove this drive we have to remove the dependency of this drive from SQL Server service. Here are the steps:
1. Open cluster administrator
2. Right click SQL Service and select Properties
3. Click Modify and remove the resource from Modify Dependencies window
4. Now we can go back to Cluster Administrator and delete the resource/drive volume.
If we delete the drive or resource without removing the dependency, the SQL Service might fail to start. The following errors might occur:
TDSSNIClient initialization failed with error 0x103, status code 0x1.
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.
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
The cause is that certain registry values that got deleted. In our case it was "parameters" and "RegSync" values that got deleted from the HKEY_LOCAL_MACHINE\Cluster\Resources\
For more information refer to this excellent post:
http://social.msdn.microsoft.com/Forums/en-US/sqldisasterrecovery/thread/af054e22-4b36-4793-a87d-120002ae215f
Comments