| Previous | Next |
| ERROR_ACCOUNT_LOCKED_OUT | OR_INVALID_OID |
OR_INVALID_OXID
The referenced DCOM object exporter no longer exists.
OR_INVALID_OXID is Win32 status 1910 (0x776). In DCOM, an object exporter represents a server-side apartment or process that publishes COM objects, and its OXID is carried in marshaled object references. A client or resolver uses that identifier to obtain RPC binding information. The status means the resolver has no current exporter entry for the supplied OXID.
Why an OXID becomes invalid
- the COM server process exited, crashed, or restarted after the object reference was marshaled
- a cached or persisted OBJREF outlived the exporter instance that created it
- network reconnection, failover, or container restart delivered a reference from an obsolete server lifetime
- marshaled data was truncated, corrupted, or interpreted with the wrong structure version
- custom proxy, broker, or transport code reused an OXID across unrelated object references
DCOM evidence to capture
Record the client and server hosts, CLSID and interface IID where known, server process identity and start time, activation path, OXID value in protected diagnostics, marshaling timestamp, RPC binding information, DCOM and System events, and whether the server restarted. Do not expose raw marshaled interface data in ordinary telemetry because it can reveal internal endpoints and security bindings.
Diagnostic sequence
Determine whether the COM server instance that produced the reference is still alive. Correlate process restart or service recovery with the first 1910 result. Recreate the object through normal activation and compare the new reference; if the fresh object works, the old reference is stale rather than the endpoint mapper being generally unavailable.
If fresh activation also fails, inspect DCOM activation, firewall, RPC endpoint resolution, and server registration. For custom marshaling, validate the OBJREF signature and field boundaries and ensure references are not stored beyond their documented lifetime. Avoid attempting to repair an OXID by substituting another numeric identifier.
Recovery and design guidance
Release the stale proxy and activate or obtain a new object reference from the authoritative server. Retry only at an operation boundary where duplicate work is controlled, because the former server may have completed a request before disappearing.
Applications should treat remote COM references as lifetime-bound capabilities, detect server restart, and rebuild higher-level state. Services should log stable correlation IDs around activation rather than relying on OXID values as permanent identities.
Difference from an invalid OID
OR_INVALID_OXID means the exporter container identified by the reference is unknown. OR_INVALID_OID means the exporter context can be understood but the specific exported object identity is absent.
Example
A management console keeps a marshaled proxy while the remote COM service is upgraded and restarted. Its next call returns 1910 because the old OXID belongs to the terminated process. Discarding the proxy and activating a new server instance restores communication.
References
- Microsoft: System Error Codes (1700–3999)
- Microsoft: Win32 Error Codes in MS-ERREF
- Microsoft: DCOM Object Resolver Service
- Microsoft: IObjectExporter::ResolveOxid
Looking for a different code? Search another status or error code.