Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Unable to start Microsoft Message Queuing service due to Event ID 2078 — Message Queuing Logging and Checkpoint Events

Unable to start Microsoft Message Queuing service due to Event ID 2078 — Message Queuing Logging and Checkpoint Events

Created by Daniel Polaske, last modified by Caroline Juszczak on Jan 10, 2018

Views: 854 Votes: 1 Revisions: 13


You may find that the Microsoft Message Queuing (MSMQ) service is unable to start.

This may occur after deleting .mq files in the MSMQ folder, or due to unrelated SolarWinds or Windows issues.


All Orion Core products


SolarWinds is dependent on this service to be able to start.

When investigating the Event Viewer log, you may find Event 2078 which displays the following: 

Information below is from the Microsoft website


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.


To resolve the issue, see





Last modified