FSW - File share witness not bring to online
Question
Monday, April 2, 2018 11:48 AM
Hi.
SQL 2016 and server OS - 2012 R2.
Successfully created AG setup in SQL 2016 and all databases schronized between node 1 and node 2.
Quorum configured as File share witness. it was working since last two days. but today got issues and fsw not bring to the online. cluster core resources is online.
Please suggest and how to resolve as below errors
Error messages:
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.
Thnaks
All replies (5)
Monday, April 2, 2018 1:23 PM
Did you made any changes ? Any other relevant message related to FS witness in Cluster logs, GUI or eventviewer. Does server on which it resides is online does it has connectivity with both the nodes ?
Cheers,
Shashank
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
Monday, April 2, 2018 1:36 PM
Nothing changes on both the nodes and FSW remote file share witness servers also.
Event viewer messages:
File share witness resource 'File Share Witness' failed to arbitrate for the file share '\Servername\ESCDBWITNESS'. Please ensure that file share '\Servername\ESCDBWITNESS' exists and is accessible by the cluster.
Event id - 16069 and 1564.
But can able to access this share folder path for both the nodes. by using run command.
Monday, April 2, 2018 1:45 PM
Hi,
This may be of helpful.
/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc756221(v=ws.10)
Thanks
Syed.
Dont forget to mark as Answered if you found this post helpful.
Monday, April 2, 2018 1:50 PM
Event viewer messages 1
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.
Messages 2
Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason:
DNS bad key.
Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.
But cluster core resources online and cluster name ping with virtual IP also - it is same subnet cluster configurations.
Messages 3
Cluster network name resource 'Cluster Name' encountered an error enabling the network name on this node. The reason for the failure was:
'Unable to obtain a logon token'.
The error code was '-1073741717'.
You may take the network name resource offline and online again to retry.
Monday, April 2, 2018 2:24 PM
Check the ACLs (both file share and NTFS permissions) on the file share. Make sure that the Cluster Name Object still has Read and Write permissions to it.
I'm starting to think that somebody accidentally deleted the Cluster Name Object in Active Directory or modified a Group Policy Object that affects it. Error code -1073741717 means that the Cluster Name Object could not reset its password in Active Directory.
Edwin M Sarmiento Microsoft Data Platform MVP | Microsoft Certified Master/Solutions Master
Blog | Twitter | LinkedIn
Learn SQL Server High Availability and Disaster Recovery