{"id":3698,"date":"2023-03-26T16:48:13","date_gmt":"2023-03-26T16:48:13","guid":{"rendered":"https:\/\/geekmungus.co.uk\/?p=3698"},"modified":"2023-04-10T07:14:10","modified_gmt":"2023-04-10T07:14:10","slug":"microsoft-exchange-2016-how-to-fix-exchange-dag-witness-failed-state","status":"publish","type":"post","link":"https:\/\/geekmungus.co.uk\/?p=3698","title":{"rendered":"Microsoft Exchange 2016 – How to Fix Exchange DAG Witness Failed State"},"content":{"rendered":"\n

In certain situations the Exchange DAG witness can become a problem, this can occur during an upgrade or can happen if there is a network interruption. Although the DAG will continue to operate the witness is considered failed, which can cause odd behaviour in a failover scenario, as there is no quorum available for the database resource (i.e. to decide which side is going to be active and which passive).<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

It is recommended to run the PowerShell console as Administrator.<\/p>\n\n\n\n

Confirming the Issue<\/h1>\n\n\n\n

To confirm the issue run the following PowerShell command from the Exchange Management Shell:<\/p>\n\n\n\n

Get-DatabaseAvailabilityGroup -Identity \"DAG01\" -Status | format-list Name, *Witness*, Servers\n<\/code><\/pre>\n\n\n\n
Now in my output, I was seeing “InvalidConfiguration” under the WitnessShareInUse field.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Notice the the WitnessShareInUse is showing “InvalidConfiguration”.<\/p>\n\n\n\n
If you just try to set it back up again with:<\/p>\n\n\n\n
Set-DatabaseAvailabilityGroup -Identity \"DAG1603\" -WitnessServer \"exchserver1.domain.com\u201d -WitnessDirectory \"C:\\DAGFileShareWitnesses\\DAG1603.domain.com\"\n<\/code><\/pre>\n\n\n\n
You get this error:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Resolution<\/h1>\n\n\n\n
To resolve it you just need to set a new WitnessServer, in our setup we have two Witness servers each taking half of the pairs of the servers in each DAG. So instead, if you run:<\/p>\n\n\n\n
Set-DatabaseAvailabilityGroup -Identity \"DAG1603\" -WitnessServer \"wtgc-exch-wit-b.internal.sanger.ac.uk\u201d -WitnessDirectory \"C:\\DAGFileShareWitnesses\\DAG1603.internal.sanger.<\/code><\/pre>\n\n\n\n
\"(tick)\" Notice, this is a different WitnessServer specified wtgc-exch-wit-b.internal.sanger.ac.uk<\/strong> instead of wtgc-exch-wit-a.internal.sanger.ac.uk<\/strong>.<\/p>\n\n\n\n
Now to confirm its okay, re-run:<\/p>\n\n\n\n
Get<\/code>-DatabaseAvailabilityGroup<\/code> -Identity<\/code> \"DAG1603\"<\/code> -Status<\/code> | <\/code>format-list<\/code> Name, *Witness*, Servers<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
That’s better, its showing primary <\/strong>now.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
If you also run this, you’ll see a quorum resource is now specified:<\/p>\n\n\n\n
Get<\/code>-ClusterQuorum<\/code> | <\/code>fl<\/code> *<\/code><\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
When it is operating correctly, the QuorumResource <\/strong>field will show a value, when it is not, this will be blank (typically).<\/p>\n\n\n\n
Alternate Witness Server<\/h2>\n\n\n\n
Now, if like me you have the alternate witness server specified you may need to change this as well, for example, in our case each DAG uses two witness servers, so we have A and B servers specified as the WitnessServer and the AlternateWitnessServer, now it doesn’t matter which is which, as long as they are both different servers for maximum availability.<\/p>\n\n\n\n
Run the commands above to set a new directory setting specifying the different server for the alternate as per the original\/primary.<\/p>\n\n\n\n
Additional Information<\/h1>\n\n\n\n