We are experiencing some problems with a DAG on exchange 2013.
There are 2 exchange servers in the organization each one located on different site, both servers have all the roles installed.
A DAG is configured and both exchange servers only have one NIC which is used for the DAG replication and mappi connections
There are several alerts about the witness server and I get following error on the exchange admin centre when accessing the DAG properties:
Database availability group 'SMDAG01' witness is in a failed state. The database availability group requires the witness server to maintain quorum. Please use the Set-DatabaseAvailabilityGr
oup cmdlet to re-create the witness server and directory.
As the above warning recommends I ran Set-DatabaseAvailabilityGr
oup cmdlet but it fails with the following error.
oup -Identity SMDAG01 -WitnessDirectory C:\SMDAG01
WARNING: An unexpected error has occurred and a Watson dump is being generated: Some or all identity references could
not be translated.
Some or all identity references could not be translated.
+ CategoryInfo : NotSpecified: (:) [Set-DatabaseAvailabilityG
+ FullyQualifiedErrorId : System.Security.Principal.
+ PSComputerName : d5ex01.mydomain.net
Also, on the failover cluster manager on both servers I noticed that one of the nodes is down ( see attached images ) and when i tried to bring the resource online I keep getting this error.
Cluster network name resource 'Cluster Name' cannot be brought online. The computer object associated with the resource could not be updated in domain 'mydomain.net' for the following reason:
Unable to obtain the Primary Cluster Name Identity token.
The text for the associated error code is: An attempt has been made to operate on an impersonation token by a thread that is not currently impersonating a client.
The cluster identity 'SMDAG01$' may lack permissions required to update the object. Please work with your domain administrator to ensure that the cluster identity can update computer objects in the domain.
Finally, some how the DAG work as I was able to active the database copies on both servers before rebooting them.
do you guys have an idea of what might be causing this issue ?