Hello @SQLServerBro
The resource-specific registry keys that correspond to the SQL Server cluster resource that you are trying to bring online are missing. This problem also occurs if the values that correspond to the resource-specific registry keys are not correct.
However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.
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:
1.Click Start, click Run, type Regedit, and then click OK.
2.In Registry Editor, locate and select the registry key: HKEY_LOCAL_MACHINE\Cluster\Resources\<GUID>\Parameters.
3.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
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>
VirtualServerName
Value Name: VirtualServerName
Value Type: REG_SZ
Value Data: <Name of the virtual SQL server>
4.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.
Hope this answers all your queries, if not please do repost back.
If an Answer is helpful, please click "Accept Answer" and upvote it : )