Fix COMQC_E_NO_QUEUEABLE_INTERFACES (0X80110601) Error

Quick answer

Open Component Services, find your COM+ application, right-click it, select Properties, go to the Queuing tab, and check "Queued" and "Listen". Then restart the application.

Why this happens

This error tripped me up the first time too. It shows up when you try to use COM+ queued components, but the component doesn't have queueable interfaces. Usually happens in Windows Server 2012 R2 or 2016 after installing MSMQ (Message Queuing) or when a third-party app tries to use queued calls. The component just isn't marked as queueable.

Fix steps

1. Open Component Services: Press Win + R, type dcomcnfg, hit Enter.
2. Go to Component Services > Computers > My Computer > COM+ Applications.
3. Find your application (the one giving the error). Right-click it, choose Properties.
4. Click the Queuing tab. Check both Queued and Listen boxes.
5. Click Apply, then OK.
6. Right-click the application again, choose Shut down, then right-click and Start it.
7. Try your operation again. Should work now.

Alternative fix (registry method)

If Component Services doesn't let you change the queuing settings, or if it's greyed out, you can force it via registry. Be careful here — one wrong move and you'll break things.

1. Press Win + R, type regedit, hit Enter.
2. Back up the registry first: File > Export, save somewhere safe.
3. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\COM3\Applications.
4. Find your application's GUID (looks like {GUID}) under this key.
5. Inside that GUID key, look for a DWORD named QueuingEnabled. If it doesn't exist, create it: right-click > New > DWORD (32-bit).
6. Set its value to 1.
7. Close regedit, restart the COM+ application from Component Services.

Prevention tip

When you create new COM+ components, always mark them as queueable from the start. In Visual Studio, set the QueuingExceptionClass attribute on your interface, or use the InterfaceQueuingAttribute. Saves you from this headache later.

Also, make sure MSMQ is installed with the COM+ Queuing feature. Go to Server Manager > Add Roles and Features, check Message Queuing > MSMQ HTTP Support (if needed) and COM+ Queuing. Without it, no queuing works at all.

"This error is frustrating because it's not obvious. But once you know the fix, it takes five minutes."

Still stuck? Check the Windows Event Viewer logs under Applications and Services Logs > Microsoft > Windows > COM+. They sometimes give more details about which component is failing. Good luck!