Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, November 6, 2018 3:19 PM
We have 2 sites within our Exchange 2016 DAG. We recently failed everything over to our secondary site and when we failed back, one of the servers in our secondary site is having problems with the cluster service. The cluster service will not start and keeps throwing an error message. From another server I can get-Clusternode and see all of the servers except the one.
I am seeing some reports of people having to evict the server from the cluster, reboot it, and then add it back into the cluster. This cluster doesnt have any shared storage.
Error:
The Cluster service cannot be started. An attempt to read configuration data from the Windows registry failed with error '2'. Please use the Failover Cluster Management snap-in to ensure that this machine is a member of a cluster. If you intend to add this machine to an existing cluster use the Add Node Wizard. Alternatively, if this machine has been configured as a member of a cluster, it will be necessary to restore the missing configuration data that is necessary for the Cluster Service to identify that it is a member of a cluster. Perform a System State Restore of this machine in order to restore the configuration data.
Any help with this would be appreciated
All replies (3)
Wednesday, November 7, 2018 7:29 AM | 2 votes
Hi,
If the member in the secondary site is failed, you can try the following steps to reincorporate it into the DAG.
- Open Command Prompt as administrator and run the cmdlet to evict it from the cluster.
cluster <DAGName> node <DAGMemberName> /forcecleanup
- Once cleanup finished, you can add the member back into the cluster using the following command.
Start-DatabaseAvailabilityGroup -Identity <DAG Name> -MailboxServer <Server Name>
Regards,
Dawn Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Thursday, November 15, 2018 9:51 AM
Hi,
How is everything going? If there is anything unclear or any update, please feel free to post it here. If you have solved the issue, please mark the solution as answer, which could be beneficial for answer searching in the forum.
Thanks for your understanding.
Regards,
Dawn Zhou
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.
Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.
Monday, August 12, 2019 6:47 AM
Thank you Dawn!
I have been struggling with this issue for hours. Your solution worked as a charm. Once again, thank you!