question

Lt-Columbo avatar image
0 Votes"
Lt-Columbo asked DonaldJamie-3524 commented

Numerous errors related to File Share Witness

Hi All,

I have two sites (HO and BO) connected to each other over site-to-site VPN.
In the HO I have a failover cluster and in the BO I have a host with a file share configured as a file share witness for the failover cluster.
Both hosts of the failover cluster can ping the hosts where FSW resides.
Both hosts can access FSW by UNC path \\vmhost\witness.
However, in the Cluster Events I can the following warnings and errors.

1562 - File share witness resource 'File Share Witness' failed a periodic health check on file share '\\VMHOST01\WITNESS'. Please ensure that file share '\\VMHOST01\WITNESS' exists and is accessible by the cluster.
1069 - 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.

1564 - File share witness resource 'File Share Witness' failed to arbitrate for the file share '\\VMHOST01\WITNESS'. Please ensure that file share '\\VMHOST01\WITNESS' exists and is accessible by the cluster.
1205 - 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.

I can't understand why those warnings and errors are generated if the failover cluster itself functions normally.
If any has ever had the same issue please advise if it lead to failover cluster failure if a half of the nodes is down.

windows-server-clustering
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

We have noticed this post and we are doing research on it now, if there's any update, we'll feedback as soon as possible. Thanks for your understanding!

Best Regards,
Joann

0 Votes 0 ·
jiayaozhu-MSFT avatar image
0 Votes"
jiayaozhu-MSFT answered DonaldJamie-3524 commented

Hi,

Thank you for your reply!

Here are some tips that I can give you to troubleshoot your issue:

1.Does your cluster event have this problem occasionally or keep reporting this error? Is the current witness status online or offline?

2.If the current witness is offline, please try online to see if there are any errors,

3.If it is currently online and no error is reported at the current time, it may be caused by temporary network instability when the error occurs. Please check the network connection with witness when the witness is offline.

Thank you for your time and please feel free to feedback if you still have concerns about your issue.

Best regards
Joann


If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

HiJohan, have the same issue as described. We are using a file share witness. I will answer your questions.

1.Does your cluster event have this problem occasionally or keep reporting this error? Is the current witness status online or offline? The event keeps occuring and repeating its self, for the last two days now. Current witness state is offline , i will try again and online, To note the witness share can be accessed from both nodes.


2.If the current witness is offline, please try online to see if there are any errors,

**Tried again to bring online and again we receive the following errror " Eventid - 1069 , 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.**





0 Votes 0 ·
Lt-Columbo avatar image
0 Votes"
Lt-Columbo answered jiayaozhu-MSFT commented

Decided to set up cloud witness instead.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

Thank you for your reply!

If you successfully replace with cloud witness, you can share your workaround with others by posting it on this page. And Accept Answer to let other people who have the similar issues with yours to get the solution more quickly.

Best regards
Joan

0 Votes 0 ·