Rule "SQL Server Database Services feature state" failed

Question

I'm trying to do a SQL 2008 cluster installation.
I installed one node and now I'm trying to add a failover cluster node.

in the "add Node Rules" I get following message:

---------------------------
Rule Check Result
---------------------------
Rule "SQL Server Database Services feature state" failed.

The SQL Server Database Services feature failed when it was initially installed. The feature must be removed before the current scenario can proceed.
---------------------------
OK  
---------------------------


Can anyone help me?

Answer 1

This error means the initial first node installation failed and addnode  is now blocked. You should go to the first node and check setup log files to see if the installation succeeded or failed. If the first node failed you would need to uninstall it and try the installation again. Then you should be able to add addition nodes.

---

This posting is provided "AS IS" with no warranties, and confers no rights.

Answer 2

I am getting the same error, But when I tried to un-install the first failed installation. the wizard gives me error .

UninstallClusterBlockCheck

Checks whether the selected instance is clustered and can be removed as specified.

Failed

The selected instance is clustered and cannot be removed as specified. To remove the selected instance, select "Remove Node" on the Installation Center or specify /Action=RemoveNode from the command-line.

can someone give my code for un-installing node

i used the following code

Setup /ACTION=RemoveNode /INSTANCENAME=MSSQLSERVER /INDICATEPROGRESS /Q

Kindly Suggest

 

Thanks & Regards

Shashi Kant Chauhan

 

---

Victory Rajput

Answer 3

Hi All,

Using the following command, I successfully able to Un-install my SQL failed installation.

Setup /ACTION=RemoveNode /INSTANCENAME=MSSQLSERVER /INDICATEPROGRESS /Q

Thanks & Regards

Shashi Kant Chauhan

---

Victory Rajput

Answer 4

Milos

I have the same failure and the reason was due to the SQL Server Agent domain account not having the correct permissions on the server and thus the service startup failed.  I can't believe that I have to reinstall to remove this block.  Do you have any other options, running the setup with an option to ignore the "SQL Server Database Services feature state" check on the "Add Node Rules" page?

Christo

Answer 5

Managed to fix the problem without re-installing.  Just execute the "Repair" action on the initial node, this can be found under the "Maintenance" page in SQL Server Installation Center (setup).  This action will clear the failure state and allow the node addition action.

Regards

Christo

Answer 6

Fulltilt, this did not solve my issue at least. :(

Answer 7

Did you execute the fix on the installed node (not the node that you want to add)?  What was your original installation error?

 

Answer 8

I think the problem can be avoided by changing this reg key, but here's everything I had to do to get mine working...  I recommend trying to registry change and then trying the other steps if that doesn't work.

Change registry key on active node:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.BENEDICT\ConfigurationState
Change all 4 values from 2 to 1

Download and extract the service pack by running the following command: 

SQLServer2008SP2-KB979450-x64-ENU.exe /x:C:\SP2

Run: C:\SP2\x64\setup\1033\sqlsupport.msi

Run from source media:
Setup.exe /PCUSource=C:\SP2 /SkipRules=Cluster_IsDomainController Cluster_VerifyForErrors /Action=AddNode

Answer 9

Hi guys, 

 

Just to let you all know what Jarrid said in the last post, definitely does work. 

 

Changing my regkeys gets it out of the non-install state. 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.BENEDICT\ConfigurationState
Change all 4 values from 2 to 1

Answer 10

Worked for me too. You also need to do this after you install the missing SQL Agent resource.

---

What is not explicitly allowed should be implicitly denied

Answer 11

Works for me too!

Answer 12

I was upgrading from SQL2008 to R2 and the solution from Jarrid worked for me as well :-)

Answer 13

I just ran into this issue on Denali trying to add a 3rd node and the registry change did the trick for me as well.  As the others stated before - repair failed and removed failed so short of flattening the servers I was pretty stuck.  Thanks to you I will have a cool SQL Server Denali multisite cluster to demo at Tech-Ed on Monday :)

---

David A. Bermingham, MVP Senior Technical Evangelist, SIOS Technology Corp

Answer 14

For me these two links worked:

First open regedit...

http://answers.yahoo.com/question/index?qid=20071204030329AAqTCT4

then change all 4 items to 1 even if they are 3 or 2

http://dbainhouse.blogspot.com/2011/04/rule-sql-server-database-services.htm

 

hope it can help others...:D

Answer 15

Great!

 

works for me too!

i  didn´t need run setup again, only executed "re-run" and setup continues...

Answer 16

THis may happen if your installation failed to add the "SQL server service" and "SQL server agent" service to the cluster administrator and you manullay add them to the cluster. Since you manually update the cluster the SQL server install logs will not refect that and may throw these errors when you try to add the instance from passive node.

THerefore you may need to repair for the instance from the primay node and then try the option to adding them to them to the cluster.

Answer 17

I think the problem can be avoided by changing this reg key, but here's everything I had to do to get mine working...  I recommend trying to registry change and then trying the other steps if that doesn't work.

Change registry key on active node:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.BENEDICT\ConfigurationState
Change all 4 values from 2 to 1

 

On SQL 2008 R2, this worked great. Then just click Re-run on the failing step in Setup on the Add Node instance.

Answer 18

I just want to add I also managed to get past the setup failed error using Jawidd's suggestion :)

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.BENEDICT\ConfigurationState
Change all 4 values from 2 to 1

In my case only one of the 4 states was set to 2 instead of 1.

Changed and re-run setup I am now upgraded from SQL 2008 to SQL 2008 R2

thank you for this tip!

Paul

Answer 19

Jawwid's comment worked for me too when upgrading from SQL Server 2008 R2 SP1 to SQL Server 2012 Std. Worrying that a previously failed installed feature on 2008 R2 instance could cause this. Suggests that the attempted repair actually didn't.

Answer 20

I received the error when adding a node to a multi-node (8 node) cluster using SQL 2008 R2 SP1.  My problem happened because I was also concurrently adding another node to the cluster, and it was in process while I was running this one.  In other words, the sql setup on the node where I received the error picked up the error because the node it was checking was going through some changes (add node).  I presume it read the registry key, which was probably being written to at the time.  I've installed many multi-node clusters before and have not run into this issue, but I think it was because I was doing them one at a time.  I was trying to multi-task and do more than one at a time this time.  I guess it makes sense that we don't want to be making changes to the other nodes in the cluster when the sql setup checks cluster status(es).  In my case, I just reran the sql setup w/o doing any of the other fixes on this thread, after the other sql setup was done of course.  Lesson learned.

Answer 21

Christo Pretorius,

This has worked for me, thanks!

---

LW