Microsoft MSMQ messages stuck in the outgoing queue after cloning servers


Always remember to sysprep when cloning a node! MSMQ (Microsoft Message Queuing) uses a registry valued called QMId located at:

HKLM\Software\Microsoft\MSMQ\Parameters\Machine Cache

which has to be unique on all your servers or it will cause all sorts of issues. Sysprepping a server generates a new SID which also generates a new QMId in the process. If you don’t do this and have multiple servers out there with the same QMId, you will see strange things like messages remaining in the outgoing queue in limbo and sometimes just disappear completely with no trace in journaling anywhere. Bottom line, don’t confuse MSMQ! It’s fragile!

Thankfully John Breakwell (MSMQ guru at Microsoft) blogged about this exact issue which made me realize what was going on in the environment I was troubleshooting. Well done John!

I simply ran sysprep and resealed the clone to fix it. It automatically generated a new QMId in the process so I didn’t have to follow the exact steps John had blogged about. It was a simple mistake which can be avoided in the future by using the Guest Customization Wizard in VC to automatically sysprep when creating the clone.

BTW, you can check if your SIDs are identical on a server by using getsid.exe. Download the Windows XP Service Pack 2 Support Tools:

and use the getsid.exe tool to compare SIDs on your Windows servers. Usage syntax is here:

Since I’m blogging about MSMQ, let me take a moment to plug QueueExplorer ( This is hands down the best MSMQ management software I have ever used and the developer is very open to feature requests. Give them some business and tell them Jason sent ya! 🙂 Check out a screenshot of it below:

About Jason Samuel

Jason Samuel lives in Houston, TX with a primary focus on strategic advisory and architecture of end-user computing, security, enterprise mobility, virtualization, and cloud technologies from Citrix, Microsoft, & VMware. He also has an extensive background in web architecture and networking over his 20+ year career in IT. He is an Author, Speaker, and Local User Group Community Leader. He is certified in several technologies and is 1 of 63 people globally that is a recipient of the prestigious Citrix Technology Professional (CTP) award. He is 1 of 42 people in the world that has been awarded as a VMware EUC Champion and VMware vExpert. He is a featured author on DABCC which provides the latest IT Community News on Cloud, Data Center, Desktop, Mobility, Security, Storage, & Virtualization. In his spare time Jason enjoys writing how-to articles and evangelizing the technologies he works with. Disclaimer: The content and opinions expressed in articles and posts are his own and are by no means associated with his employer.

Recommended for you


  1. John Breakwell

    June 30, 2010 at 3:14 PM

    That’s “ex MSMQ guru at Microsoft” 🙂

  2. Pingback: Tweets that mention MSMQ messages stuck in the outgoing queue after cloning servers | --

  3. Jason

    June 30, 2010 at 6:38 PM

    Guru none the less. 🙂

  4. Li

    May 9, 2017 at 6:47 AM


    I have this issue that my MSMQ messages stuck in the outgoing queue after cloning servers, I copy the Storage folder on the client computer and I don’t know how to send them to the server..
    when I copy them back to the client , after uninstall and install MSMQ the service fails to load ..
    do you have a solution for this issue?

Leave a Reply

Your email address will not be published. Required fields are marked *