COMQC_E_QUEUING_SERVICE_NOT_AVAILABLE (0X80110602) Fix

When This Error Shows Up

You're working with a COM+ application that uses queued components — maybe a legacy ERP system or a custom app that sends inventory updates to a central server. You fire up the component, and boom: COMQC_E_QUEUING_SERVICE_NOT_AVAILABLE (0X80110602) with the message "Message Queuing is required for the requested operation and is not installed." I've seen this on Windows Server 2019 after a clean install, and on Windows 10 Pro workstations running test environments. The component tries to hand off a message to MSMQ, finds nothing listening, and throws this exact hex code.

Root Cause

What's actually happening here is that COM+ Queued Components rely on Microsoft Message Queuing (MSMQ) as their transport layer. When you create a queued component, COM+ serializes the method call into an MSMQ message. If MSMQ isn't installed — no service, no binaries, no queues — the COM+ runtime can't create the message object. The error 0X80110602 is the COM+ layer telling you "I need a messenger boy, and he's not here."

The reason this isn't a permissions or firewall issue (though those can break it later) is that the error specifically says "not installed." MSMQ is an optional Windows component. It's disabled by default on most server and desktop editions. You have to turn it on manually.

The Fix: Install MSMQ

Skip any registry hacks or service tweaks — the real fix is adding the Windows Feature. Here's the exact sequence that works every time.

1. Open Windows Features
   Press Win + R, type optionalfeatures, hit Enter. The Windows Features dialog opens.
2. Find Message Queuing
   Scroll down to Microsoft Message Queue (MSMQ) Server. Don't confuse it with anything else — it's the only entry with "Queue" in the name.
3. Enable it
   Check the box next to "Microsoft Message Queue (MSMQ) Server." By default, this installs the core MSMQ service and the HTTP support sub-feature. That's enough for COM+ queued components. You don't need Active Directory integration or Triggers for this to work.
4. Let it install
   Click OK. Windows might ask for installation media or just grab files from Windows Update. Wait a minute or two.
5. Reboot
   Yes, you need to restart. The MSMQ service won't start until after a reboot. I've tried to start it manually — doesn't work until the OS finishes post-install setup.
6. Verify the service
   After reboot, open Services.msc and look for the "Message Queuing" service. It should be running. If it's stuck on Starting, your boot sequence might have a conflict — but that's rare.

Check This If It Still Fails

If you still get 0X80110602 after installing MSMQ, look at these:

• Service not running: Open Services.msc, find "Message Queuing." If it's stopped, right-click and Start. Set its startup type to Automatic.
• Firewall blocking: MSMQ uses ports 1801 (RPC), 135 (RPC Endpoint Mapper), and 2101-2107 (multicast). If your app is across machines, ensure these are open. For local COM+ calls, this isn't an issue.
• COM+ application not configured for queuing: Right-click the COM+ application in Component Services, go to the Queuing tab, and check "Queued" is enabled. The component itself must also support queuing — check the component's interfaces for the "Queued" flag.
• Wrong MSMQ edition: On Windows Server Core or Nano, MSMQ might not be available. You need the Desktop Experience or full GUI. Yes, it's annoying.

One last thing: if you're on Windows 10/11 Home edition, MSMQ isn't available at all. You need Pro or Enterprise. The optionalfeatures dialog will show it grayed out or missing entirely. Upgrade your OS edition or move to a proper server.