Windows Server 2019 — MSMQ service stuck in starting state after journal corruption — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

The Message Queuing service on Windows Server 2019 remains in a Starting state and never reaches Running. Dependent line-of-business apps cannot enqueue or read messages, causing transactional flows to stall and downstream processors to back off entirely.

Environment & Reproduction

Common after an unclean shutdown that left the MSMQ journal or transaction logs in an inconsistent state. Inspect the storage directory and Application log.

Get-Service -Name msmq
Get-WinEvent -LogName System -MaxEvents 40
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10

Root Cause Analysis

Causes include corrupt LQS files, oversized transactional logs, ACL loss on the MSMQ storage folder, or a kernel disk write that was truncated.

Quick Triage

Capture service state, MSMQ storage size, and the most recent journal-related error event before remediation.

sc.exe query msmq
Get-Service -Name msmq | Select-Object Status,StartType
Get-EventLog -LogName System -Newest 30 | Where-Object {$_.Source -match 'msmq'}

Step-by-Step Diagnosis

List MSMQ files, check storage path ACLs, and read MSMQ error events from the Application log.

Get-WinEvent -LogName System -MaxEvents 50 | Where-Object {$_.ProviderName -match 'msmq'} | Select TimeCreated,Id,LevelDisplayName,Message
sc.exe qfailure msmq
sfc /verifyonly

Solution — Primary Fix

Stop the service, move the journal files aside to a quarantine folder, then start MSMQ to let it rebuild a clean store.

Restart-Service -Name msmq -Force
Get-Service -Name msmq | Select-Object Status,StartType
Get-WinEvent -LogName System -MaxEvents 20 | Where-Object {$_.ProviderName -match 'msmq'}

Solution — Alternative Approaches

If queues must be preserved, run mqsvc repair workflow and restore the storage folder from the most recent backup.

sc.exe config msmq start= auto
sc.exe failure msmq reset= 86400 actions= restart/60000/restart/60000/run/1000
Restart-Service -Name msmq -Force

Verification & Acceptance Criteria

MSMQ runs, queues are enumerable, and test messages flow through without sequence errors.

Get-Service -Name msmq
Get-WinEvent -LogName System -MaxEvents 25 | Where-Object {$_.ProviderName -match 'msmq' -and $_.LevelDisplayName -eq 'Error'}
Test-NetConnection -ComputerName localhost -Port 

Rollback Plan

Restore the storage directory and registry hive from the previous good backup if rebuild loses needed messages.

Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
wbadmin get versions
# Restore previous configuration export if available

Prevention & Hardening

Schedule clean shutdowns, monitor MSMQ store growth, and back up the storage path on a regular cadence.

Get-Service -Name msmq | Export-Clixml C:/Temp/msmq-baseline.xml
Get-WinEvent -LogName System -MaxEvents 50 > C:/Temp/msmq-events.txt
Get-ScheduledTask | Where-Object {$_.TaskName -match 'msmq'}

Related Errors & Cross-Refs

Related to event identifiers 2030, 2028, and SCM service timeout 7022.

Related tutorial: View the step-by-step tutorial for Windows Server 2019.

View all Windows Server 2019 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn documentation for Message Queuing storage recovery on Windows Server 2019.