Event ID 2076 — Message Queuing Logging and Checkpoint Events

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

red

To provide transaction consistency, Message Queuing logs transaction status changes and incoming messages to a log file (QMLog), and then creates a checkpoint that is written to a separate file. The checkpoint file contains version information, and the QMLog is updated to refer to that version of the checkpoint file as being the current checkpoint.

During initialization of the MSMQ Service, there is a recovery phase for transactional messages where the QMLog file is read. It contains the version information for the most current checkpoint entry in the checkpoint files and then uses the current checkpoint file to perform recovery of transactional messages.

If there is a failure between the time that the checkpoint file was created and when the QMLog was updated with the new version, the QMLog file refers to the earliest checkpoint file version and recovery fails.

Message Queuing uses several checkpoint files to maintain consistency. These checkpoint files are used to perform recovery of transactional messages.

 

Event Details

Product: Windows Operating System
ID: 2076
Source: MSMQ
Version: 6.1
Symbolic Name: EVENT_ERROR_CANT_INIT_LOGGER
Message: The logger files cannot be initialized. The file QMLog in the Msmq\Storage folder is corrupted or absent. Error %1: %2

Resolve

Correct or recover corrupt log and checkpoint files

The MSMQ Service needs access permissions on the checkpoint and log files. If the service has permissions and you receive this error, then the file is probably corrupt. To start the MSMQ Service without losing consistency, you must correct or recover corrupted checkpoint and log files.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To correct or recover corrupted checkpoint and log files:

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

  1. To start the service for emergency use (with a potential loss of data consistency), navigate to the %windir%\sSystem32\msmq\storage folder, and then delete the following files: QMLog, MQTrans.lg1, MQTrans.lg2, MQInSeqs.lg1, MQInSeqs.lg2.
  2. Open Registry Editor. To open Registry Editor, click Start. In the search box, type regedit, and then press ENTER.
  3. Create the DWORD registry entry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters\LogDataCreated, and then set to a value of 0.

If you continue to get this error, note any details in the event message, and then contact Microsoft Customer Service and Support (CSS). For information about how to contact CSS, see Enterprise Support (http://go.microsoft.com/fwlink/?LinkId=52267).

Verify

Verify that the MSMQ Service is installed and running.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verfiy that the MSMQ Service is installed and running:

  1. Open the Services snap-in. To open Services, click Start. In the search box, type services.msc, and then press ENTER.
  2. Locate the Message Queuing service, and then confirm that the value in the Status column is Started.
  3. For further confirmation, run a test application that uses the Active Directory features that you require.

Related Management Information

Message Queuing Logging and Checkpoint Events

Message Queuing

Community Additions

ADD
Show: