| Previous | Next |
| CO_E_CLASS_CREATE_FAILED | CO_E_SCM_RPC_FAILURE |
CO_E_SCM_ERROR
Treat this HRESULT as a marker, not as a request for a generic restart or reinstall. It is returned when activation failed while COM was binding the request to the SCM/DCOM activation infrastructure rather than inside the target object’s business logic.
Meaning in the subsystem
COM activation is a sequence rather than a single operation: registration lookup, SCM or surrogate selection, process startup, class-factory publication, marshaling, and finally the requested interface call. The useful evidence is the evidence from the first stage that fails; a later RPC or cleanup message can otherwise hide the original activation problem.
Do not collapse this result into a nearby status. CO_E_SCM_RPC_FAILURE is specifically an RPC communication failure after the SCM path is selected; CO_E_SCM_ERROR is the broader bind/activation-control failure. Compare lifecycle, identity, caller, and first API.
Minimum useful evidence
| Capture | Why it matters |
|---|---|
| Local versus remote activation, CLSCTX flags, machine name, and RPC endpoint context | Pins evidence to one attempt. |
| RPCSS/DCOM service state and System/DistributedCOM events at the activation time | Separates contract failure from environment. |
| CLSID/AppID registration, service or executable activation route, and identity configuration | Creates a stable before/after control. |
| Firewall/RPC evidence if the request crosses a machine boundary | Tests whether the first boundary moves. |
Identifiers, timestamps, versions, counts, state flags, hashes, and redacted paths normally provide enough correlation. Keep credentials, private keys, message bodies, recovery material, and personal data out of routine incident logs.
Isolate the responsible condition
- Activate a known-good local server through the same SCM path; keep every other input fixed and record the first event that differs from the failing run.
- Compare in-process activation with local-server activation for the same client; use a disposable or backed-up environment when the comparison changes boot, security, device, queue, or encryption state.
- Restart only the affected registered server, not the whole machine, and observe whether SCM binding changes; retain one negative control so that a broad workaround is not mistaken for a root-cause correction.
Do not use repeated retries as the primary test. In this case, a successful later attempt may reflect a new object, refreshed policy, restarted service, different token, or completed background transition, so record exactly what changed between attempts.
Avoid the common misdiagnosis
Read the comparison results in this order for communication with the COM Service Control Manager:
| Observed result | Interpretation |
|---|---|
| The minimal or known-good comparison succeeds | The control works; inspect production-specific state. |
| The control fails at the same first operation | The control also fails; inspect host/provider evidence. |
| A new HRESULT marks another boundary | The failure moved to another boundary; diagnose the new status separately rather than treating it as confirmation that the entire operation is fixed. |
Regression proof
Repair the failed contract rather than the surrounding system: Repair the activation registration or SCM/DCOM service path and preserve the original server-side failure instead of repeatedly re-registering unrelated components. Preserve the pre-change configuration or trace.
Close the incident only when the intended CLSID activates through the same local/remote route and DCOM event logs remain clean under repeated cold starts. Repeat under the original identity and state. A different environment is comparison, not proof.
Technical references
Use these sources for the formal contract, then combine them with evidence from the returning application or service for communication with the COM Service Control Manager:
- Microsoft Open Specifications: HRESULT values.
- Microsoft: COM clients and servers.
- Microsoft: CoGetClassObject.
- Microsoft: COM elevation moniker.
Looking for a different code? Search another status or error code.