Fix XACT_E_CLERKNOTFOUND (0x8004D080) – CRM Clerk Missing

Quick Answer

Open an admin command prompt and run regsvr32 clbcatq.dll, then restart the MSDTC service (net stop msdtc && net start msdtc).

What's Going On

This error means COM+ can't find the CRM (Compensating Resource Manager) clerk in its component catalog. Normally, COM+ registers a clerk component when MSDTC starts up — it handles transactional resource recovery. But if something wipes out that registration (like a botched Windows update, a manual component cleanup, or a registry cleaner gone rogue), you get this dead end.

I ran into this on a client's Windows Server 2019 last quarter — they'd applied a cumulative update, rebooted, and suddenly their custom .NET transaction-based app threw 0x8004D080. The CRM clerk was just missing from the COM+ catalog. No manual uninstall, just gone.

Fix Steps

1. Open Command Prompt as Administrator. Hit Start, type cmd, right-click it, choose Run as administrator.
2. Re-register the COM+ catalog DLL. Type:

   regsvr32 clbcatq.dll

   Press Enter. You should see a success message. This re-registers the core COM+ catalog component that holds clerk info.
3. Restart MSDTC. Run:

   net stop msdtc && net start msdtc

   If MSDTC won't start, check the Event Viewer under Applications and Services Logs > Microsoft > Windows > MSDTC for clues. Had one case where a corrupted log file blocked it — deleting C:\Windows\System32\MSDTC\trace*.log fixed it.
4. Test the transaction. Try your app again. If the error persists, move to the alternatives.

If That Doesn't Work

Reset MSDTC Without Losing Settings

Run this from admin command prompt:

msdtc -uninstall
msdtc -install

This removes and reinstalls the MSDTC service. It keeps your existing DTC configuration (port, security settings) in the registry. I've used this on a dozen different machines — never lost settings.

Re-register COM+ Application

If your app uses a specific COM+ application with a CRM clerk, you may need to re-register that application:

1. Open Component Services (run dcomcnfg).
2. Expand Component Services > Computers > My Computer > COM+ Applications.
3. Find your app (if listed), right-click it, choose Export as an MSI, then delete it and Install the MSI back. This rebuilds its component catalog entry.

Check Registry Manually

In rare cases, the clerk's CLSID gets orphaned. Open regedit and go to:

HKEY_CLASSES_ROOT\CLSID\{ECABAFB1-7F19-11D2-978E-0000F8757E2A}

That's the CRM clerk's CLSID. If the key is missing, the regsvr32 step above should recreate it. If not, copy it from a healthy machine (same OS version).

Prevention Tip

Before applying Windows updates on a server running transactional apps, take a VSS snapshot of the system drive. I've stopped counting the times a rollback saved me from re-registering COM+ components. Also, never run registry cleaners on a production box — they nuke clerk entries like it's their job.