none
Access Denied Errors: [API] s_ApiOpenClusterEx: failed with error = 5

    Question

  • We have a four node Hyper-V Failover Cluster running Windows Server 2012 R2 connected to StoreVirtual SAN storage. After importing the Cluster into SCVMM all four nodes are filling the event logs with the following two errors. This is causing higher than normal compute but everything else appears to be working as it should. Any advice or pointers as to what could be causing these errors would be much appreciated.

    Event Log: Microsoft-Windows-FailoverClustering/Diagnostic

    Event 2050, FailoverClustering

    [API] s_ApiOpenClusterEx: failed with error = 5

    and

    Event Log: Microsoft-Windows-FailoverClustering/Diagnostic

    Event 2051, FailoverClustering

    [API] AccessCheck[AndAuditAlarm] failed.  status = 0x00000005

    Friday, March 10, 2017 4:08 PM

All replies

  • Hello,

    You can steps outlined in the article below for troubleshooting the issue for Failover Cluster.

    https://blogs.msdn.microsoft.com/clustering/2012/05/07/how-to-troubleshoot-create-cluster-failures-in-windows-server-2012/

    Best regards,
    Andy Liu

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, March 13, 2017 2:35 AM
  • There are no errors or warnings in cluster validation report.

    Monday, March 13, 2017 5:06 PM
  • Hello,

    What's the version for the SCVMM? Have you get the most recent update installed for SCVMM?

    On the other hand, you may consult the documentation from StoreVirtual SAN storage, and make sure the edition for SCVMM is supported for StoreVirtual.

    Best regards,

    Andy Liu


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, April 04, 2017 7:54 AM
  • UPDATE: the permission for the network service account on the cluster object was not set correct during the creation of the clusters

    ----------------------------------------------------------------------

    Hi

    did you figure out the cause for these errors?

    Erlend


    • Edited by Erlend Øyen Friday, October 20, 2017 11:03 AM
    • Proposed as answer by heyko Tuesday, January 16, 2018 4:42 PM
    Friday, October 20, 2017 10:22 AM
  • Hi,

    We're also seeing hundreds of thousands of these errors. I gave the SCVMM network service account full control of the cluster computer object in AD but it doesn't seem to have helped. Also tried updating to 2016 UR4. Is there any step that we're missing?

    Thanks

    Jon

    Friday, January 19, 2018 2:15 PM
  • Hi It’s on the cluster object inn failovercluster manager Erlend
    Friday, January 19, 2018 2:18 PM