| Previous | Next |
| CO_E_ACTIVATIONFAILED_EVENTLOGGED | CO_E_ACTIVATIONFAILED_TIMEOUT |
CO_E_ACTIVATIONFAILED_CATALOGERROR
CO_E_ACTIVATIONFAILED_CATALOGERROR is the failure HRESULT 0x8004E023 (signed decimal -2147164125, unsigned decimal 2147803171). Its severity bit is 1, facility is 4 (FACILITY_ITF), and the facility-specific code field is 0xE023.
The COM+ catalog could not supply a usable activation configuration
This HRESULT narrows COM+ activation failure to catalog or configuration data. The runtime could not build the component’s activation environment from the persisted application, class, interface, identity, or service attributes.
AllStat describes the result as “COM+ Activation failed due to a catalog or configuration error.” for it, this wording identifies the immediate COM+ condition, while surrounding context and earlier events determine why it was reached.
Contract boundary
The authoritative configuration is the COM+ catalog’s logical view, which combines its registration database with selected Windows registration data. Editing an isolated registry value may not repair the catalog transaction or the deployed package.
Causes that fit this specific result
- The component entry references a missing or mismatched DLL, type library, or application identity.
- A partial package import leaves inconsistent application and class attributes.
- Manual registry changes diverge from the COM+ catalog entry used at activation.
- Catalog data is unreadable, stale, or damaged after rollback, restore, or unsupported copying.
Evidence to preserve before changing the system
- Export the COM+ application configuration and record application ID, CLSID, DLL path, and bitness.
- Compare the catalog entry with the actual file version, registry class registration, and deployment manifest.
- Capture COM+ catalog and System Application events before attempting reinstallation.
- Check whether the same component activates in a freshly created test application.
Diagnostic sequence
- Use Component Services or COMAdmin APIs to inspect the logical catalog rather than editing RegDB files directly.
- Repair deployment by reinstalling or reimporting the component through supported administration operations.
- Validate application identity, activation type, threading model, and required service attributes.
- Retest after recycling the affected COM+ application, not every application on the server.
Retry and recovery
Restore a consistent catalog entry from a known deployment package or reinstall the component. Repeating activation against unchanged catalog data is deterministic.
What the result does not establish
The code does not prove physical catalog corruption; an internally consistent but incorrect attribute can produce the same result. It also does not identify the exact property without logs.
Difference from nearby HRESULT values
REGDB_E_CLASSNOTREG concerns COM class registration more generally. CO_E_THREADINGMODEL_CHANGED specifically identifies a threading-model mismatch after COM+ installation.
Practical scenario
An upgrade copies a new component DLL but skips the COM+ package update. The catalog still describes the prior binary and activation fails with this HRESULT; reinstalling the component through Component Services synchronizes the metadata.
Developer and telemetry guidance
Version COM+ catalog exports with application binaries. Deployment validation should compare CLSID, path, architecture, and service attributes before switching traffic.
Official Microsoft references
- Microsoft: COM transaction and context error codes
- Microsoft: the COM+ catalog
- Microsoft: configuring COM+ applications
- Microsoft: COM+ Components collection
- Microsoft: HRESULT values in MS-ERREF
Looking for a different code? Search another status or error code.