What does HRESULT 0x800401FD (CO_E_OBJNOTCONNECTED) mean?

Previous	Next
CO_E_OBJISREG	CO_E_APPDIDNTREG

CO_E_OBJNOTCONNECTED

Object is not connected to server

Meaning and numerical form

CO_E_OBJNOTCONNECTED is HRESULT 2147746301 (0x800401FD; signed -2147220995). For CO_E_OBJNOTCONNECTED, AllStat records its meaning as “Object is not connected to server”. In practical terms, it is returned when a COM interface proxy or object reference no longer has a usable connection to its server object.

The severity bit in 0x800401FD is set, so CO_E_OBJNOTCONNECTED is a failure result rather than a success or informational status. Its facility is 4 (FACILITY_ITF) and its low 16-bit code is 509 (0x01FD). For CO_E_OBJNOTCONNECTED, those fields classify the value but do not identify the component instance, call, object or input that produced it.

Where the failure belongs

CO_E_OBJNOTCONNECTED belongs to COM activation and object lifetime. For CO_E_OBJNOTCONNECTED, COM activation is a sequence rather than one registry lookup: identifier resolution, class registration, module or process start, class-factory publication, marshaling, and object lifetime can fail independently. For CO_E_OBJNOTCONNECTED, the decisive condition is this: a COM interface proxy or object reference no longer has a usable connection to its server object. For CO_E_OBJNOTCONNECTED, record the first native producer instead of relying only on a framework exception translated several layers later.

Do not infer from CO_E_OBJNOTCONNECTED alone that reinstalling, rebooting or repeating the whole workflow is appropriate. Because CO_E_OBJNOTCONNECTED can cross process and language boundaries, its correction depends on the object identity, lifecycle generation, input and state at the first failing call.

Evidence to collect

A useful CO_E_OBJNOTCONNECTED record includes the native API or interface method, component or CLSID, process and thread IDs, architecture, apartment where relevant, operation correlation ID, elapsed time, input identity, and the first state-changing event before failure. When diagnosing CO_E_OBJNOTCONNECTED, preserve IErrorInfo, an inner HRESULT, Win32 status, device event or provider message when available.

• Capture 1 for CO_E_OBJNOTCONNECTED: server process exit code and disconnect time.
• Capture 2 for CO_E_OBJNOTCONNECTED: object identity, marshaling path, apartment and last successful call.
• Capture 3 for CO_E_OBJNOTCONNECTED: RPC and application logs around release, shutdown or network interruption.

Telemetry for CO_E_OBJNOTCONNECTED should retain types, lengths, hashes, stable opaque identifiers and lifecycle generations while redacting content and credentials. For CO_E_OBJNOTCONNECTED, this makes repeated incidents comparable without exposing paths, object identities, user data or credentials.

Likely causes

• Possible cause 1 for CO_E_OBJNOTCONNECTED: the out-of-process server exited or disconnected the object.
• Possible cause 2 for CO_E_OBJNOTCONNECTED: the client retained an interface beyond the server-defined lifetime.
• Possible cause 3 for CO_E_OBJNOTCONNECTED: RPC connectivity or apartment teardown invalidated the proxy.

Diagnostic sequence

1. Capture CO_E_OBJNOTCONNECTED at the first native return and identify the exact object and method.
2. Confirm that the observed path matches this CO_E_OBJNOTCONNECTED condition: a COM interface proxy or object reference no longer has a usable connection to its server object.
3. For CO_E_OBJNOTCONNECTED, compare the live state with the method contract before changing configuration.
4. For CO_E_OBJNOTCONNECTED, collect the code-specific evidence listed above and preserve any more specific preceding error.
5. For CO_E_OBJNOTCONNECTED, change one evidence-backed cause at a time, then repeat the smallest operation that can prove the correction.
6. Add a regression check that distinguishes CO_E_OBJNOTCONNECTED from the related outcomes described below.

Practical scenario

A background COM server restarts during an upgrade while a client keeps a cached proxy; reacquiring the component after restart avoids CO_E_OBJNOTCONNECTED. The CO_E_OBJNOTCONNECTED scenario narrows the result to a reproducible contract boundary and supplies a concrete before-and-after test.

Correction and retry boundary

• Corrective action 1 for CO_E_OBJNOTCONNECTED: reacquire a fresh object through the supported activation or discovery path.
• Corrective action 2 for CO_E_OBJNOTCONNECTED: correct lifetime ownership so clients release stale interfaces promptly.
• Corrective action 3 for CO_E_OBJNOTCONNECTED: make server restarts visible and invalidate cached proxies deterministically.

Retry guidance for CO_E_OBJNOTCONNECTED. Retry by creating a new object only when the operation is safe to repeat; calling the same disconnected interface again is not recovery. A CO_E_OBJNOTCONNECTED retry must avoid this hazard: launch duplicate servers, reuse stale proxies or repeat an activation whose side effects are unknown. It must also preserve the evidence needed to locate the original producer of CO_E_OBJNOTCONNECTED.

Difference from nearby HRESULTs

CO_E_RELEASED usually indicates use after object release, while CO_E_OBJNOTCONNECTED emphasizes that the object reference is no longer connected to its server. For CO_E_OBJNOTCONNECTED, keep these outcomes separate in logs, exception mappings, user messages, dashboards and automated retry policy.

Developer and operational guidance

Code handling CO_E_OBJNOTCONNECTED should log the failed stage before cleanup, keep ownership and lifecycle transitions explicit, and avoid converting every failure into a generic message. Tests for CO_E_OBJNOTCONNECTED should cover the primary cause, one adjacent HRESULT and the retry boundary so a future change cannot turn a deterministic contract failure into an uncontrolled loop.

Operational repair for CO_E_OBJNOTCONNECTED should use supported product installation, COM registration, activation and class-factory lifetime paths. For CO_E_OBJNOTCONNECTED, avoid unsupported configuration edits or component replacement unless evidence identifies that layer. For CO_E_OBJNOTCONNECTED, retain the original trace and a post-fix trace so the result can be attributed and the change reversed.

Official Microsoft references

• Microsoft: generic COM error codes — official documentation relevant to CO_E_OBJNOTCONNECTED.
• Microsoft: CoCreateInstance — official documentation relevant to CO_E_OBJNOTCONNECTED.
• Microsoft: COM activation and object location — official documentation relevant to CO_E_OBJNOTCONNECTED.

---

Looking for a different code? Search another status or error code.