| Previous | Next |
| CONTEXT_E_TMNOTAVAILABLE | CO_E_ACTIVATIONFAILED_EVENTLOGGED |
CO_E_ACTIVATIONFAILED
CO_E_ACTIVATIONFAILED is the failure HRESULT 0x8004E021 (signed decimal -2147164127, unsigned decimal 2147803169). Its severity bit is 1, facility is 4 (FACILITY_ITF), and the facility-specific code field is 0xE021.
COM+ could not create the configured component, but this code is only the outer category
This is the generic COM+ activation failure. It states that activation did not complete, but it deliberately carries less cause information than the event-logged, catalog, timeout, or initialization variants.
AllStat describes the result as “An unexpected error occurred during COM+ Activation.” for it, this wording identifies the immediate COM+ condition, while surrounding context and earlier events determine why it was reached.
Contract boundary
Activation spans catalog lookup, security checks, server-process launch, context construction, and component initialization. The first failing stage must be recovered from event records, activation tracing, and the component deployment rather than inferred from this symbol alone.
Causes that fit this specific result
- A COM+ security or software-restriction check rejects activation without a more specific outward code.
- The configured server process, component DLL, or dependent runtime fails during startup.
- Catalog data and binary registration disagree in a way not mapped to the catalog-specific result.
- Custom initialization raises an unexpected failure that loses its inner detail across the activation boundary.
Evidence to preserve before changing the system
- Capture the CLSID, application ID, caller identity, server process, and activation flags.
- Preserve the first COM+ and application event-log entry from the same timestamp.
- Record catalog version, component DLL path, bitness, and deployed file hash.
- Collect the inner HRESULT or exception from server startup and component activation if available.
Diagnostic sequence
- Check for a more specific companion event before changing configuration.
- Validate that the registered component and COM+ catalog entry identify the same build and architecture.
- Reproduce activation with a minimal client under the same identity.
- Repair the first classified failure rather than repeatedly restarting Component Services.
Retry and recovery
Correct the underlying launch, security, catalog, or initialization problem and reactivate the application. Blind retries are appropriate only when evidence shows a transient process-start condition.
What the result does not establish
The generic code does not establish catalog corruption, a timeout, or component initialization failure. Those interpretations require additional evidence or a narrower HRESULT.
Difference from nearby HRESULT values
CO_E_ACTIVATIONFAILED_EVENTLOGGED directs diagnosis to a recorded event. CO_E_ACTIVATIONFAILED_CATALOGERROR, CO_E_ACTIVATIONFAILED_TIMEOUT, and CO_E_INITIALIZATIONFAILED classify particular activation stages.
Practical scenario
A serviced component fails only on one server and the client receives this generic HRESULT. The paired COM+ event reveals an application identity logon failure; fixing that identity resolves activation without modifying the component code.
Developer and telemetry guidance
Always log activation identifiers and the inner server-side result. Dashboards should group the outer HRESULT by first event-log cause so a generic code does not hide several unrelated incidents.
Official Microsoft references
- Microsoft: COM transaction and context error codes
- Microsoft: COM+ Component Services
- Microsoft: configuring COM+ applications
- Microsoft: COM+ troubleshooting
- Microsoft: HRESULT values in MS-ERREF
Looking for a different code? Search another status or error code.