Installation of SQLserver2008 cluster fails on windows2008.(The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F)

Installation of SQLserver2008 cluster might fail on windows2008 with error mentioned below

The cluster resource 'SQL Server' could not be brought online. 
Error: The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F)


Root Cause

This problem occurs because of a new security feature named Loopback check functionality. By default, loopback check functionality is turned ON in Windows and the value of the DisableLoopbackCheck registry entry is set to 0 (zero).

With this feature being turned ON: windows do not allow NTLM authentication if we try to access server from Local server using a name which is not its Net-Bios name (or) IPAddress.

When SQLServer Agent is started, SQLAgent resource access the SQLServer using SQLVirtualServer name and hence we do not allow NTLM. So the SQLServer Agent would fail and the SQLServer Agent Resource creation would also fail.

SQLServer resource will fail to come Online because, IsAlive check will be done using NTLM Autentication i.e: Cluster service startup account resolves as NT AUTHORITY\ANONYMOUS LOGON when connecting to SQLServer for IsAlive check and the connection fails.

We will not get in to this issue if startup account of SQLServer has permissions to read and write SPN's.

After the installation fails you will see the SQLServer resource is created but not the SQLAgent resource.


There are three ways to resolve this issue.

Option 1

1. After the failure, create the SPN’s manually using SetSPN tool (or) Configure SQL Server service to create SPNs dynamically for the SQL Server instances (Refer KB: 811889)

Example for creating SPN’s manually:

2. Bring the SQL Server Resource online.

3. Create the SQL Server Agent resource type.

To add the sql server agent resource type execute the below command:

cluster restype "SQL Server Agent" /create /DLL:sqagtres.dll .Once done we got the
update that the Resource type 'SQL Server Agent' created.

4. Create SQL Server agent resource manually.

We need to make sure that the newly created SQL server Agent resource have the virtualservername and Instancename .

To add this property  go to  "failover cluster management" ==>SQLServer Agent Resource==>Properties==>properties
check for the two parameters
(virtualservername and Instancename) and fill in the


5. Change configuration reg_dword values of all components to 1 in below registry path


Option 2

1. Do a Complete uninstall of failed installation (or) Configure SQL Server service to create SPNs dynamically for the SQL Server instances (Refer KB: 811889) and move to Step 3.

2. Create the SPN's before we do the installation. --



Note:Beginning with SQL Server 2008, the SPN format is changed  and new SPN format does not require a port number Refer:

3. Then install the SQL Server on cluster

Option 3 (Recommended)

1. Disable the authentication loopback check by setting the DisableLoopbackCheck value in 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa registry subkey to 1.

To set the DisableLoopbackCheck registry entry to 1, follow below steps on all nodes of cluster.

      a. Click Start, click Run, type regedit, and then click OK. 
      b. Locate the following registry path:
      c. Right-click Lsa, select New, and then click DWORD Value. 
      d. Type DisableLoopbackCheck, and then press ENTER. 
      e. Right-click DisableLoopbackCheck, and then click Modify.
       f. In the Value data box, type 1, and then click OK.

2. Restart the system.

3. Do complete uninstall and re-run the setup(or) Follow the steps from step2 in option 1.




1. We will encounter above error if we are installing the named instance of SQL Server and SQL Server browser is in stopped state. 

2.  If you have installed SQLServer 2012 (Denali) and uninstalled it on same cluster. You might encounter above issue. Refer below link for   details.


If you liked this post, do like us on Facebook at and join our Facebook group!/groups/454762937884205/

Thank you,

Karthick P.K |My Facebook Page |My Site| Blog space| Twitter

Comments (12)

  1. Wayne says:

    You aren’t installing as a domain admin and your account you are using to run SQL services has no rights except on the SQL server are you? At least this was my situation.

    I found that delegating the ability to modify serviceprincipalnames on Computer objects in the Computers OU + granting Read/Write all attributes to the the service account by the service account resolves these problems with establishing the correct SPNs for cluster failover. This allows the SQL service account to dynamicly register and deregister SPNs as instances are taken off line and brought on line.

  2. Jason says:

    you are the best option 3 worked for me

  3. DL says:

    You are amazing. I have fought this issue for a named instance install on my cluster for a week now. I knew what the issue was but had no idea how to fix it. Thanks for option #3.

  4. Athena says:

    thks a lot

  5. SQL SERVER DBA says:

    Thank You, Option 3 has to be installed on both the nodes and failover worked!!!

  6. Dianne says:

    For my install, tried option 3 first, but still got the error.  Had to do option 1 as well as option 3.  Thanks for the info!

  7. Lars says:

    Instructions were very helpful. Also be aware that software firewall settings can keep the setup from running with sucess. Make sure there are allows for the Instance IP addresses. I also found that I needed to turn off the firewall during initial setup and again when first moving the created resource to another node.

  8. tom says:

    registry entry changes, server restarted, uninstall, new install but same error 🙁 like before

  9. Hello Tom,

    ISAlive failure on SQL Cluster because of other reason could cause this. Did you ever install and uninstall denali instance on this server? refer…/sql-server-resource-fails-to-come-online-is-alive-check-fails



  10. prashanth says:

    I have followed the same-successful on node1, but it threw a different error for me when i tried to add node. During add node setup rule is failing with MSCS Cluster verification error[Cluster report is successful with some warnings]. tried "Setup /SkipRules=Cluster_VerifyForErrors /Action=AddNode", But it did throw into some other error, where the password is not valid though after providing a valid one. can you please comment on this.

  11. Hello Prashanth,

    check if you are hitting…/828861

    To get faster response join our Facebook group    and post your questions.



Skip to main content