| Previous | Next |
| CO_E_ACTIVATIONFAILED | CO_E_ACTIVATIONFAILED_CATALOGERROR |
CO_E_ACTIVATIONFAILED_EVENTLOGGED
CO_E_ACTIVATIONFAILED_EVENTLOGGED is the failure HRESULT 0x8004E022 (signed decimal -2147164126, unsigned decimal 2147803170). Its severity bit is 1, facility is 4 (FACILITY_ITF), and the facility-specific code field is 0xE022.
The client-facing HRESULT is a pointer to a more specific activation event
This result means COM+ activation failed and that additional information was written to the event log. The actionable diagnostic record is therefore the correlated COM+ or application event, not a speculative interpretation of the HRESULT text.
AllStat describes the result as “COM+ Activation failed. Check the event log for more information.” for it, this wording identifies the immediate COM+ condition, while surrounding context and earlier events determine why it was reached.
Contract boundary
The HRESULT is an outward summary. Event retention, clock alignment, application identity, and activation identifiers determine whether the underlying event can be matched reliably.
Causes that fit this specific result
- Server-process creation fails and COM+ records the operating-system or identity error.
- A component DLL or dependency cannot load and the server event contains the loader detail.
- Initialization code raises an exception whose information is preserved only in the local application log.
- A catalog, security, or configuration check emits a detailed COM+ event before activation is returned to the client.
Evidence to preserve before changing the system
- Collect the System and Application logs from the COM+ server, not only the client machine.
- Match UTC timestamp, CLSID, application ID, process ID, and caller request correlation.
- Export the full event XML so numeric HRESULTs and insertion strings are retained.
- Preserve preceding warnings because the final activation event may summarize an earlier failure.
Diagnostic sequence
- Find the earliest correlated COM+ event and decode any nested HRESULT it reports.
- Confirm the event belongs to the same activation attempt rather than a noisy background component.
- Apply the event-specific correction to identity, binary, catalog, security, or initialization.
- Repeat one controlled activation and verify that no new correlated event is produced.
Retry and recovery
Recovery follows the event’s actual cause. Retrying before reading the event can overwrite timing evidence and create many identical server activations.
What the result does not establish
The HRESULT itself does not say which event source, ID, or underlying subsystem failed. Absence of an event on the client is expected when activation occurs remotely.
Difference from nearby HRESULT values
CO_E_ACTIVATIONFAILED is the generic category without an explicit promise of logged detail. CO_E_INITIALIZATIONFAILED narrows the stage to an initialization function.
Practical scenario
A remote client receives this HRESULT while activating a COM+ server. The server Application log identifies a missing side-by-side dependency in the configured DLL; deployment installs the correct runtime and the next activation succeeds.
Developer and telemetry guidance
Automated incident collection should retrieve server-side event XML whenever this code appears. Store the event record ID beside the client error so future analysis does not depend on broad timestamp searches.
Official Microsoft references
- Microsoft: COM transaction and context error codes
- Microsoft: COM+ troubleshooting
- Microsoft: configuring COM+ applications
- Microsoft: COM+ Component Services
- Microsoft: HRESULT values in MS-ERREF
Looking for a different code? Search another status or error code.