| Previous | Next |
| CO_E_SERVER_PAUSED | CO_E_CLASS_DISABLED |
CO_E_SERVER_NOT_PAUSED
COM server is not currently paused
CO_E_SERVER_NOT_PAUSED is HRESULT 2147500070 (0x80004026) from winerror.h. AllStat describes it as “Activations on the server are not paused.” The value must be interpreted at administrative control attempting an operation that requires a paused COM server, because the same high-level symptom can come from a different contract boundary and require different cleanup.
The decisive Interpretation is that the requested transition or maintenance action expected the server to be paused, but it is running or already resumed. Keep the symbolic name beside the raw hexadecimal value so later analysis does not collapse the result into an unrelated COM family.
Where the result appears
- This result may surface in administrative control attempting an operation that requires a paused COM server.
- 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.
Determine the object and lifecycle phase that owned this result; a UI symptom cannot establish whether the origin was the caller, proxy, runtime, server, or metadata producer.
Typical causes and interpretation boundary
Common cause categories for it are: two operators race; an idempotent resume is treated as an error; deployment state is stale; another controller already resumed service. Evaluate these branches independently and require evidence from the owning API before promoting one branch to the root cause.
The check that separates this result from nearby HRESULTs is: the requested transition or maintenance action expected the server to be paused, but it is running or already resumed. If the decisive fact for it is unknown, keep the result unresolved and collect the missing state instead of inferring it from wording.
Correct handling and recovery
The appropriate recovery is to refresh the actual server state, make orchestration idempotent, and execute only transitions valid from the observed state. The owner of retry for it must define idempotency, refreshed state, maximum attempts, backoff, and cancellation responsibility.
After this result, apply the API-specific validity rules to outputs and release only resources whose ownership transferred during this attempt.
Practical scenario
A deployment resume step runs twice; the second invocation records the already-running state and continues without resetting the application.
A regression test for it should force the decisive precondition, assert native outputs, fix only that condition, and confirm the expected neighboring result.
Difference from related HRESULTs
CO_E_SERVER_PAUSED blocks new activation because pause is active; it rejects a control operation based on a false state assumption.
Represent this distinction for it directly in control flow and dashboards instead of grouping it under a single COM-failure label.
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: common HRESULT values
- Microsoft: COM error codes
- Microsoft: CoInitializeEx
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.