To fix this, add full permission to \dc1\Cluster_Vote for user Cluster$ (in my case, it’s VirtualDB$).. Hope this will help..
Exchange Server: File Share Witness error

Hello!
Almost the same question (and the original one hasn't been answered yet):
There's the test Exchange setup that had been running flawlessly ~ for 10 months: DAG1 = Exch1 + Exch2 + File Share Witness on DC.
Exch2 fails and the cluster fails as well because the first healthy node - Exch1 - thinks the FSW is not accessible (thus there's no quorum and the cluster can not start).
The event 5398 says ~"start the cluster using Start-ClusterNode -FQ' " but I doubt it will make Exch1 "see" the witness share.
Does anybode know why is this happening? (and it's obviously not related to any network related problems - the share is constantly available).
Thank you in advance,
Michael
Let me know its solve or not
Hi @Mikhail Firsov
I am writing here to confirm with you how thing going now?
Please let us know if you need further help on this issue.