BUG: The MSMQ Service Fails to Start With an Error 0xc00000e4 or 0xc00e0001

This article was previously published under Q236775
This article has been archived. It is offered "as is" and will no longer be updated.
The Microsoft Message Queue (MSMQ) Service fails to start and posts two errors to the application event log.
  1. An event 2083 from the MSMQ Kernel indicating that a particular pair of files in the MSMQ storage directory failed with error code:
    - or -
  2. An event 2023 from the MSMQ Kernel with the text:
    "The recovery initialization did not succeed"
Both of these events occur in pairs.
This error is caused by Windows NT not shutting down properly. An example of this would be a situation where the active node in a cluster fails over. This error would prevent MSMQ on the second node from coming online.

It is important to note that this hotfix is a preventative fix. Once this error has occurred the only way to get MSMQ running properly again, is to either rename or remove the files mentioned in the event logs from the MSMQ\Storage directory. Then you can restart the MSMQ service.
To resolve this problem you will need to either move or rename the files mentioned in the event log that are corrupted. Then the MSMQ service should start unless it finds other corrupted files.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This bug was corrected in Windows NT4 Service Pack 6.
This hotfix is scheduled to be included in Service Pack 6 for Windows NT 4.0. Please see this article for more information once Service Pack 6 is released.

Article ID: 236775 - Last Review: 02/28/2014 00:27:47 - Revision: 1.0

  • Microsoft Message Queue Server 1.0
  • kbnosurvey kbarchive kbbug KB236775