High Availability for MYQ Print Servers in VMWare - Event 1146 RHS closed unexpectedly and has been restarted

[selahattin şadoğlu]

Hi All,


We have 2 node Failover Print cluster using Windows 2016 Server. 2 nodes are on VM based on ESXi.

I have a 10 node production ESXi 6.7 cluster.

Could you please let me know from where to start? The error is saying that RHS process stoped due to a DLL that is causing the issue. How i can find that dll?

- There is no any Image Backup Job


Failover Cluster Config :

https://imgur.com/a/S6KJOs1

https://imgur.com/a/BnB7u2o

https://imgur.com/a/HNFZTlx

in the logs I see errors:

A component on the server did not respond in a timely fashion. This caused the cluster resource 'TerminalsMonitor Script' (resource type 'Generic Script', DLL 'clusres2.dll') to exceed its time-out threshold. As part of cluster health detection, recovery actions will be taken. The cluster will try to automatically recover by terminating and restarting the Resource Hosting Subsystem (RHS) process that is running this resource. Verify that the underlying infrastructure (such as storage, networking, or services) that are associated with the resource are functioning correctly.


The cluster Resource Hosting Subsystem (RHS) process was terminated and will be restarted. This is typically associated with cluster health detection and recovery of a resource. Refer to the System event log to determine which resource and resource DLL is causing the issue.


Cluster resource 'ApacheMonitor Script' of type 'Generic Script' in clustered role 'SRV' failed.

Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

Cluster resource 'IP Address xx.xx.xx.xx (2)' of type 'IP Address' in clustered role 'SRV' failed.

Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it.  Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.



Any Help would be more appreciated

Thanks