Exchange Server: File Share Witness error

Mikhail Firsov 1,876 Reputation points
2021-06-25T13:06:40.697+00:00

Hello!

Almost the same question (and the original one hasn't been answered yet):

https://learn.microsoft.com/en-us/answers/questions/314610/numerous-errors-related-to-file-share-witness.html

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).

109350-118.png
109377-119.png

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

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,326 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Amit Singh 4,846 Reputation points
    2021-06-29T04:24:50.747+00:00

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

    1 person found this answer helpful.

  2. Andy David - MVP 140.8K Reputation points MVP
    2021-06-25T13:40:16.177+00:00

    Can you change the FSW to another server? One thats isnt a DC?
    Id be curious if that makes a difference.