PRB: Error "The registry check point for cluster resource msmq service could not be restored" (310327)
The information in this article applies to:
- Microsoft Message Queue Server (MSMQ) 1.0
This article was previously published under Q310327 SYMPTOMS
When you bring the Microsoft Message Queue Server (MSMQ) cluster resource online, event ID 1024 is logged:
The registry check point for cluster resource msmq service could
not be restored to registry key,
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\MSMQ.
The resource may not function correctly. Make sure that no other
processes have open handles to registry keys in this registry subtree.
CAUSE
MSMQ not only provides the tools and runtime to build asynchronous applications; it also supplies and registers an asynchronous Remote Procedure Call (RPC) transport. RPC applications, such as Microsoft SNA Server and Microsoft Exchange, call Microsoft Windows NT RPC to find out which RPC transports are available.
Several NT handles are handed back to these applications, including two handles for the MSMQ registry key. These handles continue to be held by the applications, causing the registry hive to be locked so that the cluster service is unsuccessful in restoring the checkpointed MSMQ registry hive.
RESOLUTION
After installing MSMQ in the cluster, remove the following registry keys which indicate that the MSMQ RPC transport is available:
Hkey_Local_Machine\Software\Microsoft\RPC\ClientProtocols\ncadg_mq
Hkey_Local_Machine\Software\Microsoft\RPC\ServerProtocols\ncadg_mq
Remove these keys on both nodes and then reboot. With SNA Server, you could just restart the SNA RPC service; however, if Exchange is also on the computer, RPCSS will also hold the MSMQ registry key handle. A reboot ensures that any process on the system which called NT RPC will be restarted and will refresh its RPC list.
STATUS
This behavior is by design.
| Modification Type: | Major | Last Reviewed: | 1/3/2002 |
|---|
| Keywords: | kbprb KB310327 |
|---|
|