| Previous | Next |
| CO_E_SERVER_NOT_PAUSED | CO_E_CLRNOTAVAILABLE |
CO_E_CLASS_DISABLED
COM class or containing application is disabled
CO_E_CLASS_DISABLED is HRESULT 2147500071 (0x80004027) from winerror.h. AllStat describes it as “The component or application containing the component has been disabled.” The value must be interpreted at COM or COM+ activation of a class explicitly disabled by configuration or policy, because the same high-level symptom can come from a different contract boundary and require different cleanup.
The decisive Interpretation is that the class registration exists, but activation is administratively disabled at the class or application level. 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 or COM+ activation of a class explicitly disabled by configuration or policy.
- 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: an administrator disabled the application; a failed deployment quarantined the component; policy blocks a vulnerable class. 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 class registration exists, but activation is administratively disabled at the class or application level. 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 respect the disable decision, repair or re-enable through the owning deployment system only after validation, and avoid alternate activation that bypasses policy. 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 vulnerable COM+ component is disabled during incident response; clients display an unavailable feature instead of retrying activation.
Test it by reproducing the smallest failing contract, recording postconditions, and then changing a single input or state transition.
Difference from related HRESULTs
REGDB_E_CLASSNOTREG means no usable registration was found; it means registration exists but policy forbids activation.
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.