Microsoft KB Archive/829259

= Message Queuing does not start and an Event ID 2083 error message is logged =

Article ID: 829259

Article Last Modified on 4/20/2005

-

APPLIES TO


 * Microsoft Message Queuing 2.0

-



SYMPTOMS
The Message Queuing service may not start, and the following error is logged in the application log in Event Viewer: Event Type: Error

Event Source: MSMQ

Event Category: Kernel

Event ID: 2083

Description: The persistence packet file C:\WINNT\System32\msmq\STORAGE\pXXXXXXX.mq and the log file C:\WINNT\System32\msmq\STORAGE\lXXXXXXX.mq cannot be recovered (Error: c00000e4).

The status code 0xc00000e4 corresponds to STATUS_INTERNAL_DB_CORRUPTION. This event may be followed by the following event ID message: Event Type: Error

Event Source: MSMQ

Event Category: Kernel

Event ID: 2023

Description: Unable to initialize recovery.



CAUSE
This problem occurs because the message files that are referenced in the event description are corrupted. This corruption may occur if Microsoft Message Queuing is interrupted while it is writing to the message file (p .mq) or its corresponding bitmap file (l .mq).



RESOLUTION
To resolve this problem, move or delete the two files that are referenced in the event description. You will permanently lose any messages that are contained in these files.

You can also open a support case with Microsoft Product Support Services (PSS). PSS may be able to help you fix the corrupted file or recover the data that it contains. To contact PSS, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section of this article.



MORE INFORMATION
Message files may be corrupted when antivirus software or backup software is configured to scan the Message Queuing storage directory. To avoid this problem, exclude the storage directory from antivirus scans and backup scans. Disk drive failures can also cause this problem. Review the Event Viewer logs for any signs of disk failure, and consider replacing your hard disk, if necessary.

