Article ID: 883732 - Last Review: April 6, 2006 - Revision: 2.3 A SQL Server cluster resource goes to a "failed" state when you try to bring the resource online in SQL Server 2005 or in SQL Server 2000SYMPTOMSWhen you try to bring a SQL Server cluster resource online for a virtual instance of Microsoft SQL Server 2005 or of Microsoft SQL Server 2000, you may notice the following behavior:
CAUSEThe 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. RESOLUTIONImportant This section, method, or task contains steps that tell you how to modify the registry. 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. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756
(http://support.microsoft.com/kb/322756/
)
How to back up and restore the registry in Windows 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:
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. MORE INFORMATION For additional information, click the following article
number to view the article in the Microsoft Knowledge Base: 810056
(http://support.microsoft.com/kb/810056/
)
You must use resouce-specific registry keys for SQL Server cluster resouces
| Article Translations
|
Back to the top
