The Microsoft Message Queuing (MSMQ) Resource will not come Online after Failing over to Passive Node using Microsoft Cluster Service (MSCS)
book
Article ID: 100020332
calendar_today
Updated On:
Resolution
Overview:
Microsoft Message Queuing (MSMQ) Resource will not come Online after Failing over to Passive Node using Microsoft Cluster Service (MSCS)
Details:
When the Enterprise Vault (EV) Cluster Resources are Offline, Event ID 2076 may be seen in the Event Logs with the following Description:
"The logger files cannot be initialized (Error: 0x80070020).
The file QMLog in the Msmq\Storage folder is corrupted or absent. To start the Message Queuing service without losing consistency, you must correct or recover this file (e.g. from a backup). To start the service for emergency use (with a potential loss of data consistency), delete the files QMLog, MQTrans.lg1, MQTrans.lg2, MQInSeqs.lg1, and MQInSeqs.lg2 from the Msmq\Storage folder and add the DWORD registry key
HKLM\Software\Microsoft\MSMQ\Parameters\LogDataCreated with a value of 0."
Additional Event Id 2076 entries may also be seen with the same description but different error codes, ie: "(Error: 0xc000101d)"
Event ID 2024 with the following Description may also be seen:
"The expression 'checkpoint' cannot be recovered for the checkpoint."
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is also recommended that a complete backup of the registry and workstation / server be made prior to making any registry changes.
Note: Please contact Microsoft Technical Support for further assistance as this pertains to corruption in the Clustered MSMQ Resource.
Workaround:
Warning: This workaround will bring the MSMQ to a state with empty queues. It is highly recommended that the MSMQ location be backed up prior to continuing. If there are any messages in the Queues, they may not be processed.
1. Copy the Shared MSMQ folder to an alternate location.
2. Delete the QMLog, MQTrans.lg1, MQTrans.lg2, MQInSeqs1.lg1 and MQInSeqs.lg2 files.
3. Remove the MSMQ Resource dependency from the Enterprise Vault Admin Service Resource.
4. Delete the MSMQ Cluster Resource.
5. Re-add the MSMQ Cluster Resource.
6. Bring the MSMQ Cluster Resource Online.
7. Add the MSMQ Resource as a dependency to the Enterprise Vault Admin Service Resource.
8. Bring all Enterprise Vault Cluster Resources Offline and Online.
Note: In order to attempt to re-process any existing messages in the old Message Queues, copy the messages from the MSMQ folders copied in Step 1 above to the same location in the newly created MSMQ folders.
Issue/Introduction
The Microsoft Message Queuing (MSMQ) Resource will not come Online after Failing over to Passive Node using Microsoft Cluster Service (MSCS)
Was this article helpful?
thumb_up
Yes
thumb_down
No