FIX: MSMQ Service will not Start with Corrupt Message

• Microsoft Message Queue Server version 1.0

SYMPTOMS

The MSMQ service fails to start with an Windows NT Event 2083 indicating there are corrupt messages. Details on the specific file containing the bad message is contained in the event description. This event may be followed by Windows NT Event 2023.

CAUSE

If Microsoft Message Queue Server (MSMQ) is not shut down properly due to a computer crash or power outage, then the last batch of messages may not be flushed to disk. The message log file has already been updated indicating that the block of storage in the message file does contain valid messages even though the actual contents have not yet been written. This causes the MSMQ service to view this block as one or more corrupted messages when it restarts.

RESOLUTION

MSMQ service was changed to make sure that all messages are flushed to disk.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

This bug was corrected in Windows NT4 Service Pack 6.

MORE INFORMATION

The ID of the message file containing the corrupt message is contained in the message text accompanying the event ID 2083. This message file and the file with the same number but prefixed with an "l" may be removed from the MSMQ storage directory.

CAUTION: Removing this message file results in the loss of all other messages contained in this file.

Additional query words:

Keywords : kbMSMQ kbMSMQ100 kbDSupport
Version : winnt:1.0
Platform : winnt
Issue type : kbbug