none
The File Share Witness resource is in a failed state even though the File Share Witness directory is available, and server is online in a Windows Server 2012 failover cluster RRS feed

  • Question

  • following event occurs

    File share witness resource 'File Share Witness' failed a periodic health check on file share '\\528495-WEB2\quorum'. Please ensure that file share '\\528495-WEB2\quorum' exists and is accessible by the cluster.

    Cluster resource 'File Share Witness' of type 'File Share Witness' in clustered role 'Cluster Group' failed.
    Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

    File share witness resource 'File Share Witness' failed to arbitrate for the file share '\\528495-WEB2\quorum'. Please ensure that file share '\\528495-WEB2\quorum' exists and is accessible by the cluster.

    Cluster resource 'File Share Witness' of type 'File Share Witness' in clustered role 'Cluster Group' failed.
    Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.


    The Cluster service failed to bring clustered role 'Cluster Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered role.


    Clustered role 'Cluster Group' has exceeded its failover threshold.  It has exhausted the configured number of failover attempts within the failover period of time allotted to it and will be left in a failed state.  No additional attempts will be made to bring the role online or fail it over to another node in the cluster.  Please check the events associated with the failure.  After the issues causing the failure are resolved the role can be brought online manually or the cluster may attempt to bring it online again after the restart delay period.

    ABDUL HAFEEZ MCSE MCITP

    Tuesday, November 11, 2014 12:37 PM

All replies

  • Hi Abdul, this forum relates to SQL Server tooling inside Visual Studio. Your question appears to be about a Windows Server feature so I recommend you try and find a forum related to that topic and re-ask it again there. Thanks,

    Kevin

    Wednesday, November 12, 2014 10:29 PM
    Moderator