{"id":131997,"date":"2023-04-21T07:06:18","date_gmt":"2023-04-21T07:06:18","guid":{"rendered":"https:\/\/www.stellarinfo.com\/blog\/?p=131997"},"modified":"2024-06-12T10:15:21","modified_gmt":"2024-06-12T10:15:21","slug":"failover-cluster-manager-disconnecting-and-reconnecting","status":"publish","type":"post","link":"https:\/\/www.stellarinfo.com\/blog\/failover-cluster-manager-disconnecting-and-reconnecting\/","title":{"rendered":"How to Fix – Failover Cluster Manager Disconnecting and Reconnecting – Event IDs 1146 and 1265?"},"content":{"rendered":"

Exchange Server has an excellent high availability system, with the Database Availability Group<\/a> (DAG). In this article, we will be talking about two events in the Event Viewer – Event ID 1146<\/strong> and Event ID 1265. <\/strong>Both events are related to the Cluster Service of Windows that controls the Exchange Server availability group.<\/p>

Let’s take a detailed look at the mentioned events.<\/p>

Event ID 1146 – Microsoft Windows Failover Clustering<\/h2>

The Event ID 1146<\/strong> is prompted with the following information:<\/p>

“The Cluster Resource Host Subsystem<\/strong> (RHS) stopped unexpectedly. An attempt will be made to restart it. This is usually due to a problem in a resource DLL. Please determine which resource DLL is causing the issue and report the problem to the resource vendor.”<\/code><\/em><\/p>

The message indicates that something related to the Cluster Resource Host Subsystem (RHS)<\/strong> has stopped working. To troubleshoot the issue, you need to first check which DLL file is causing the issue, apart from reporting this to your Exchange Server expert or supplier. You need to investigate more to understand the root cause of the problem.<\/p>

From the error, it seems that the subsystem has crashed and an attempt to restart the subsystem will be initiated. This is usually with the recovery process or the resource is in deadlock.<\/p>

In the cluster service, if the deadlock timeout (which by default is 20 minutes) passes, the Cluster<\/strong> Resource Host Subsystem<\/strong> (RHS) will deem the server as failed and force a failover process. If one of the nodes is down (with only one node in the cluster), the cluster will shut down for safeguard.<\/p>

Event ID 1265 – Microsoft Windows Failover Clustering<\/h2>

This event ID appears when there is a deadlock of the Cluster<\/strong> Resource Host Subsystem (RHS)<\/strong> or the DLL has crashed. The process at this stage will terminate. It’s a notification that the process has crashed and the Event ID 1146<\/strong> will shut down the cluster.<\/p>

Troubleshooting the Issue<\/h2>

Let’s discuss the process to troubleshoot the issue.<\/p>