none
Cluster Installation Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation. RRS feed

  • Question

  • Hi,

    I searched a lot but did not found any solution. So, now I am here.

    I´m trying to install MS SQL 2014 Failover Cluster on a WindowsServer 2012 R2. In test environment everything went fine, now in the prod environment we are running into a failure.

    The installation is nearly complete up to the point "BringAgentResoucreOnlineAction". It fails with following error message:

    TITLE: Microsoft SQL Server 2014 Setup
    ------------------------------

    The following error has occurred:

    The cluster resource 'SQL Server Agent' could not be brought online.  Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation.
    .

    Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.

    Error Log gives following details:

    (01) 2018-03-09 16:04:07 Slp: ----------------------------------------
    (01) 2018-03-09 16:04:07 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    (01) 2018-03-09 16:04:07 Slp: Inner exceptions are being indented
    (01) 2018-03-09 16:04:07 Slp:
    (01) 2018-03-09 16:04:07 Slp: Exception type: Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException
    (01) 2018-03-09 16:04:07 Slp:     Message:
    (01) 2018-03-09 16:04:07 Slp:         The cluster resource 'SQL Server Agent' could not be brought online.  Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation.
    (01) 2018-03-09 16:04:07 Slp:         .
    (01) 2018-03-09 16:04:07 Slp:     HResult : 0x86d8003a
    (01) 2018-03-09 16:04:07 Slp:         FacilityCode : 1752 (6d8)
    (01) 2018-03-09 16:04:07 Slp:         ErrorCode : 58 (003a)
    (01) 2018-03-09 16:04:07 Slp:     Data:
    (01) 2018-03-09 16:04:07 Slp:       resourceName = SQL Server Agent
    (01) 2018-03-09 16:04:07 Slp:       errorMessage = There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation.
    .
    (01) 2018-03-09 16:04:07 Slp:       WatsonData = Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException@58
    (01) 2018-03-09 16:04:07 Slp:       DisableRetry = true
    (01) 2018-03-09 16:04:07 Slp:     Inner exception type: Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException
    (01) 2018-03-09 16:04:07 Slp:         Message:
    (01) 2018-03-09 16:04:07 Slp:                 There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The group or resource is not in the correct state to perform the requested operation.
    (01) 2018-03-09 16:04:07 Slp:                 .
    (01) 2018-03-09 16:04:07 Slp:         HResult : 0x86d70002
    (01) 2018-03-09 16:04:07 Slp:                 FacilityCode : 1751 (6d7)
    (01) 2018-03-09 16:04:07 Slp:                 ErrorCode : 2 (0002)
    (01) 2018-03-09 16:04:07 Slp:         Data:
    (01) 2018-03-09 16:04:07 Slp:           ExceptionMessage = Generic failure
    (01) 2018-03-09 16:04:07 Slp:           StatusCode = 5023
    (01) 2018-03-09 16:04:07 Slp:           Description = The group or resource is not in the correct state to perform the requested operation.

    (01) 2018-03-09 16:04:07 Slp:           WatsonData = Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException@2
    (01) 2018-03-09 16:04:07 Slp:         Stack:
    (01) 2018-03-09 16:04:07 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
    (01) 2018-03-09 16:04:07 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.ClusterResource.Online(Int32 timeout)
    (01) 2018-03-09 16:04:07 Slp:         Inner exception type: System.Management.ManagementException
    (01) 2018-03-09 16:04:07 Slp:             Message:
    (01) 2018-03-09 16:04:07 Slp:                         Generic failure
    (01) 2018-03-09 16:04:07 Slp:             HResult : 0x80131501
    (01) 2018-03-09 16:04:07 Slp:             Data:
    (01) 2018-03-09 16:04:07 Slp:               WmiErrorCode = Failed
    (01) 2018-03-09 16:04:07 Slp:               WatsonData = Failed@5023
    (01) 2018-03-09 16:04:07 Slp:               Description = The group or resource is not in the correct state to perform the requested operation.

    (01) 2018-03-09 16:04:07 Slp:               ErrorType = 1
    (01) 2018-03-09 16:04:07 Slp:               Operation = ExecMethod
    (01) 2018-03-09 16:04:07 Slp:               ParameterInfo = MSCluster_Resource.Name="SQL Server Agent"
    (01) 2018-03-09 16:04:07 Slp:               ProviderName = WinMgmt
    (01) 2018-03-09 16:04:07 Slp:               StatusCode = 5023
    (01) 2018-03-09 16:04:07 Slp:             Stack:
    (01) 2018-03-09 16:04:07 Slp:                         at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
    (01) 2018-03-09 16:04:07 Slp:                         at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)
    (01) 2018-03-09 16:04:07 Slp:                         at Microsoft.SqlServer.Configuration.WMIInterop.Resource.BringOnline(UInt32 TimeOut)
    (01) 2018-03-09 16:04:07 Slp:                         at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
    (01) 2018-03-09 16:04:07 Slp: ----------------------------------------

    SQL Server is up and running, the SQL Server Agent cannot be started due to the above mentioned error.

    We already tried to re-create DNS entry, re-create AD object, compared the permissions between prod and test system. But we don´t see any differences.

    So, now I am hoping anyone of you have an idea.

    Regards,
    Helen

    PS: I can test again on Monday CET.

    Friday, March 9, 2018 3:52 PM

Answers

  • Finally we found the problem.

    The service owner had no local admin rights on the server... giving the user the correct rights, everything worked fine.

    I had hoped, that the error message would inidcate that kind of error, something with missing rights.

    The Windows Event Log was a good hint, because there was a message, that a specfic file could not be read due to missing access rights.

    Best regards,

    Helen

    • Marked as answer by HSelling Monday, March 12, 2018 12:42 PM
    Monday, March 12, 2018 12:42 PM

All replies

  • Hi HSelling,

    Please go to Windows Event Log to get more information related to this problem.

    Based on the error message, "The group or resource is not in the correct state to perform the requested operation", this problem can be cause by that your Cluster NetBIOS resource name does not have access to create the SQL NetBIOS name and bring this online.

    Please refer to this case: https://social.technet.microsoft.com/Forums/windowsserver/en-US/dfb642da-9e78-42de-a64e-10a46069fb7e/sql-server-2012-cluster-installation-is-getting-failed?forum=winserverClustering

    Best Regards,

    Teige


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, March 12, 2018 7:48 AM
    Moderator
  • Finally we found the problem.

    The service owner had no local admin rights on the server... giving the user the correct rights, everything worked fine.

    I had hoped, that the error message would inidcate that kind of error, something with missing rights.

    The Windows Event Log was a good hint, because there was a message, that a specfic file could not be read due to missing access rights.

    Best regards,

    Helen

    • Marked as answer by HSelling Monday, March 12, 2018 12:42 PM
    Monday, March 12, 2018 12:42 PM
  • Please check the eventviewer and if you see SSPI Handshake error then try the following:-

    WORKAROUND/SOLUTION Loopback check can be removed by adding a registry entry as follows:

    Edit the registry using regedit. (Start –> Run > Regedit ) Navigate to: HKLM\System\CurrentControlSet\Control\LSA Add a DWORD value called “DisableLoopbackCheck” Set this value to 1

    Wednesday, October 16, 2019 7:27 AM