COM+ App Recycle Fails on NT Service: 0X80110811 Fix

When This Error Shows Up

You're in Component Services, right-click a COM+ application, hit Shut down or Recycle, and instead of it restarting clean, you get the error COMADMIN_E_CANTRECYCLESERVICEAPPS (0X80110811). This almost always happens with internal line-of-business apps — things like a custom .NET service that someone registered as a COM+ app back in 2015 and nobody's touched since. Or it's a third-party app like a Sage or QuickBooks service that was installed by an admin who checked "Run as NT Service" in the COM+ application properties.

I had a client last month whose entire print queue system died because their ERP service was registered as a COM+ app and they tried to recycle it during a patch cycle. The service just sat there, grayed out, with that error.

Root Cause — Short and Simple

COM+ lets you host applications as Windows NT services — that means the COM+ runtime hands off the process management to the Service Control Manager (SCM). Once it's running as a service, COM+ can't recycle it the same way it does for regular library or server applications. The SCM controls start, stop, pause, and restart. COM+ doesn't have the hooks to recycle a service-hosted process. So the error is COM+ saying "I can't do that — ask the service manager."

It's not a bug. It's by design. But it catches you off guard because the Recycle option is still there in the UI. Microsoft should have grayed it out for service-hosted apps, but they didn't.

The Fix — Two Options

Option 1: Recycle via the Service Itself (Quick, No Changes)

1. Open Services.msc — hit Win + R, type services.msc, hit Enter.
2. Find the service that matches your COM+ app name. Look in the Description column — it often says something like "COM+ System Application" or a custom name you set.
3. Right-click the service and select Restart.
4. Wait 10 seconds, then check Component Services — the COM+ app should show as Running again.

That's it. No registry edits, no reboots. But if you're doing this often, you'll want Option 2.

Option 2: Switch the COM+ App to Server Application (Permanent Fix)

If you have control over the app and it doesn't need to run as a service (most don't — they just default to that because someone checked the wrong box), change it:

1. Open Component Services (run comexp.msc).
2. Expand Component Services → Computers → My Computer → COM+ Applications.
3. Right-click the problematic app and choose Properties.
4. Go to the Activation tab.
5. Change the Activation type from Server application to Library application? No — that breaks things if the app has identity or security requirements. Instead, leave it as Server application but uncheck Run as NT Service (if it's checked).
6. If the checkbox is grayed out, the app was explicitly registered as a service — you can't change it here. You'll need to unregister and re-register the COM+ application without the service flag. That's a bigger lift.
7. Click OK and restart the service via Services.msc.

Heads-up: If the app was designed to run as a service (e.g., it needs to survive logoffs, or it runs under SYSTEM account), changing this might break it. Test in dev first.

What to Check If It Still Fails

• Is the service actually running? Sometimes the service stops but COM+ doesn't know. Check Services.msc. If the service is stopped, start it manually.
• Event Viewer — Look under Windows Logs → Application for COM+ errors. Anything with event ID 1000 or 4199 tells you if the app crashed silently.
• Permissions — The account running the service needs Log on as a service right. If it's a custom domain account, those rights can get stripped during patches. Check Local Security Policy → User Rights Assignment → Log on as a service.
• Corrupt COM+ catalog — Rare, but if you've been fighting this for hours, run comadmin.exe /repair from an elevated command prompt. It rebuilds the COM+ registration database. You'll have to re-register any custom apps afterward.

And if none of that works? Sometimes the cleanest fix is to rebuild the COM+ application from scratch. Export the existing app's settings (right-click → Export → Application proxy), then delete and re-import. That clears out any bad state that's preventing recycle.

I've seen this error at least a dozen times in the wild. Nine times out of ten, Option 1 (restart the service) is all you need. The other times, someone checked "Run as NT Service" without realizing it locked them out of recycling. Now you know.