WARN [RCM] ResourceTypeChaseTheOwnerLoop::DoCall: ResType MSMQ's DLL is not present on this node. Attempting to find a good node...
WARN [RCM] ResourceTypeChaseTheOwnerLoop::DoCall: ResType MSMQTriggers's DLL is not present on this node. Attempting to find a good node...

Root Cause:

These events are logged because the MSMQ and MSMQ Triggers resource types are registered with the cluster service, but the MSMQ resource DLL cannot be loaded because the MSMQ feature is not installed. The MSMQ and MSMQ Triggers resource types are registered by default when the Failover Clustering feature is installed.

Possible Solutions:

Ignore – These are benign events to a debug log and can be safely ignored. They have no impact on the functionality of the cluster, nor do they indicate a failure.

Install MSMQ – If you plan to make MSMQ highly available on this cluster, open Server Manager and install the “Message Queuing” feature on all nodes in the cluster. The above errors will no longer be logged.

Unregister MSMQ Resources – If this is a non-MSMQ cluster, you can unregister the MSMQ and MSMQ resource type with the Cluster Service and the above errors will no longer be logged. This can be accomplished with the Remove-ClusterResourceType cmdlet. Open a PowerShell window and type the following:

Tags

Join the conversation

Thanks for the explanation and workaround. I do believe, though, that errors should not be produced by 'default', because you can quickly end up with lots of errors in your logs that aren't problematical, but you need either good experience or a crib sheet to know that, and it makes it easy to miss real errors.

This blog applies to any OS version, you can simply unregister the MSMQ and MSMQ Triggers resource types and these events will no longer be logged. The only consideration is that with Win2008 you will need to use Cluster.exe to unregister the resource types (as cluster PowerShell cmdlet’s were first introduced in Win2008 R2)