|
1 |
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. |
- Check the Status of Mailbox Servers by running Get-DatabaseAvaliabilityGroup | FL
- Inspect servers in stopped and started state
- If a mailbox is in a stopped state, you can attempt to stop the individual server by running: Stop-DatabaseAvaliabilityGroup -identity <cluster> -mailboxserver <mailbox server>
- Check the status of the Fail-over Cluster Service Manager
- Launch Fail-over Cluster Service Manager > Manage a Cluster > Enter <cluster>
- Expand the <cluster>, review Nodes
- If a node is stopped, attempt to ‘Start Cluster Service’
- If Cluster Service fails to start, run : Stop-DatabaseAvaliabilityGroup -identity <cluster> -mailboxserver <mailbox server> and perform a Set-DatabaseAvalibilityGroup -identity <cluster>
- If the mailbox server fails to be evicted, reboot the server; ensure mailbox databases are dismounted first or maintenance mode is effective.
- After the restarting, Perform a force cleanup of the cluster from the failed server.
- Log into the failed server, Run Cluster Node “ServerName” /forcecleanup from an elevated command prompt.
- Once the cleanup is successful, Attempt to re-add or remove the failed server back into the cluster. You can also try running Start-DatabaseAvailabilityGroup “DAG Name” –MailboxServer “FailedServer” or Stop-DatabaseAvailabilityGroup “DAG Name” –MailboxServer “FailedServer”
Author Details
testest test