This post has been republished via RSS; it originally appeared at: Failover Clustering articles.
First published on MSDN on Apr 05, 2013
After using the Get-ClusterLog cmdlet to generate the Cluster.log, you may notice the following errors and warnings in the cluster log:
ERR [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQ returned 21.'
WARN [RCM] Failed to load restype 'MSMQ': error 21.
ERR [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQTriggers returned 21.'
WARN [RCM] Failed to load restype 'MSMQTriggers': error 21.
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:
Remove-ClusterResourceType MSMQ
Remove-ClusterResourceType MSMQTriggers
In summary... just ignore them, they are just noise. If they annoy you and you don't plan to use MSMQ, then unregister the MSMQ resource types.
Thanks!
Elden Christensen
Principal PM Manager
Clustering & High-Availability
Microsoft