| Previous | Next |
| CO_E_IIDREG_INCONSISTENT | CO_E_RELOAD_DLL |
CO_E_NOT_SUPPORTED
COM operation is not supported in this context
CO_E_NOT_SUPPORTED is HRESULT 2147500065 (0x80004021) from winerror.h. AllStat describes it as “The operation attempted is not supported.” The value must be interpreted at COM activation or runtime infrastructure rejecting an operation outside its supported configuration, because the same high-level symptom can come from a different contract boundary and require different cleanup.
The decisive Interpretation is that the runtime recognizes the request but the selected object, host, platform, or activation mode does not implement it. A diagnostic event for it should retain both representations of the HRESULT and the exact API boundary that produced it.
Where the result appears
- This result may surface in COM activation or runtime infrastructure rejecting an operation outside its supported configuration.
- The first boundary to preserve for it is the exact activation, initialization, call-control, or lifetime step that returned it.
- record whether the failure occurred before an object identity existed, while a method was running, or during shutdown; those phases imply different ownership and retry rules.
Before assigning cause to this result, identify the responsible thread, apartment, process, library generation, and server instance rather than relying on the final dialog text.
Typical causes and interpretation boundary
Common cause categories for it are: the feature is unavailable in-proc or out-of-proc; the platform edition omits it; the component version predates the operation. The candidate causes for it are alternatives, so test one precondition at a time instead of applying several broad repairs together.
The check that separates this result from nearby HRESULTs is: the runtime recognizes the request but the selected object, host, platform, or activation mode does not implement it. When the boundary condition behind it has not been proven, avoid retries or repairs that assume a different neighboring HRESULT.
Correct handling and recovery
The appropriate recovery is to detect the capability, select a documented alternative, or deploy the required component; do not convert the result into a transient retry. Before retrying this result, specify which precondition changed and how duplicate effects or stale outputs will be detected.
Inspect every output before cleanup because interfaces, buffers, server effects, or metadata handles may be partially initialized.
Practical scenario
A client requests a server-only activation option from an in-process component and switches to the ordinary activation path.
Test it by reproducing the smallest failing contract, recording postconditions, and then changing a single input or state transition.
Difference from related HRESULTs
E_NOTIMPL is usually returned by a method implementation; it is a COM infrastructure or activation-level rejection.
Keeping it separate from its neighbor improves retry, cleanup, and user messaging because the two results imply different postconditions.
Developer and administrator guidance
Code handling it should classify it by lifecycle and ownership rather than by the high bit alone. For <code>it</code>, initialization failures normally require rebuilding the process or thread environment, capability results require a fallback, and uncertain remote outcomes require reconciliation before retry.
Operational dashboards should keep it distinct from generic COM failures and attach deployment, service, package, runtime, policy, and architecture dimensions. Administrators should avoid broad registry edits, blanket firewall changes, or permission expansion unless the captured evidence for it identifies that subsystem.
References
- Microsoft: COM error codes
- Microsoft: COM processes, threads, and apartments
- Microsoft: COM security defaults
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.