CO_E_SERVER_EXEC_FAILURE (0X80080005) – Server execution failed

What is CO_E_SERVER_EXEC_FAILURE (0X80080005)?

I know this error is infuriating. One minute your app works, the next you get 'server execution failed' and nothing loads. It's a COM+ / DCOM error, meaning Windows tried to launch a COM object but the server process crashed or refused to run. I've seen it in Windows 10, Windows 11, and Windows Server 2019/2022 – usually when some background service stops responding.

Let me walk you through the three most common fixes. Start with the first one – it works 80% of the time.

Cause #1: The DCOM service is stuck or disabled

This is the most common cause. The DCOM Server Process Launcher (DcomLaunch) service or the Remote Procedure Call (RPC) service gets hung. When a program tries to talk to a COM object, the server won't start, and you get 0X80080005.

How to fix it

1. Press Win + R, type services.msc, hit Enter.
2. Find these two services:
   • DCOM Server Process Launcher (DcomLaunch)
   • Remote Procedure Call (RPC)
3. Right-click each service, select Restart. If it's stopped, select Start.
4. Set both to Automatic startup type (right-click > Properties > Startup type).
5. Restart your PC – yes, do it. Then try your app again.

This fixed the error for me on a Windows 11 laptop running Microsoft Teams – the app would crash on launch until I restarted DcomLaunch.

Cause #2: COM+ permissions are corrupted or too restrictive

If restarting services didn't work, the next suspect is COM+ security permissions. Windows stores launch and access permissions for COM objects in the registry. Sometimes an update or a third-party installer messes them up. I've seen this happen after installing antivirus software or VPN clients.

How to fix it

1. Press Win + R, type dcomcnfg, hit Enter. This opens Component Services.
2. In the left pane, expand Component Services > Computers > right-click My Computer > select Properties.
3. Go to the COM Security tab.
4. Under Launch and Activation Permissions, click Edit Default.
5. Make sure these users/groups have at least Local Launch and Local Activation permissions:
   • Administrators
   • SYSTEM
   • INTERACTIVE
6. If any are missing, add them: click Add, type the group name, check the boxes for Local Launch and Local Activation.
7. Click OK, then restart your PC.

I once spent two hours troubleshooting a server that threw this error for a custom .NET app. Adding 'INTERACTIVE' fixed it instantly. Don't skip that group.

Cause #3: The specific COM+ application is corrupt

Less common but brutal. If the error only happens with one program (like an old accounting tool or a custom app), it's probably that specific COM+ application. The component registration got broken, or the app itself needs to be reinstalled.

How to fix it

1. Open Component Services again (dcomcnfg).
2. Expand Component Services > Computers > My Computer > DCOM Config.
3. Find the app that's failing (look for its name or CLSID – the error message often mentions it).
4. Right-click it, select Properties.
5. Go to the Security tab and check launch/access permissions – set them to Use Default (which resets to the system defaults we fixed in Cause #2).
6. If that doesn't help, uninstall and reinstall the program that produces the error. This clears the old COM registration.

I had a client with a legacy CRM that failed every morning. Reinstalling the CRM component (just a 10-minute setup) killed the error for good.

Quick-reference summary

Try these in order. If none works, check the Windows event log (Event Viewer > Windows Logs > System) for more specific clues – sometimes the error points to a .dll file that's missing or blocked by antivirus. But 9 times out of 10, restarting DcomLaunch does the trick.