| Previous | Next |
| CO_E_INCOMPATIBLESTREAMVERSION | CO_E_DECODEFAILED |
CO_E_FAILEDTOOPENPROCESSTOKEN
COM could not open the server process token
CO_E_FAILEDTOOPENPROCESSTOKEN is HRESULT 2147549500 (0x8001013C) from winerror.h. AllStat describes it as “Unable to open the access token of the server process.” In the COM IAccessControl, DCOM client identity, trustee translation, token inspection, security descriptor, ACL, or serialization workflow, the code identifies a specific failure boundary and should not be replaced by a generic COM exception.
Telemetry should preserve this result as a separate outcome rather than merging it with unrelated COM or WinRT failures.
Where it is encountered
- IAccessControl initialization, access checks, owner/trustee processing, and serialized ACL persistence. Record the interface, method, component version, thread, apartment, process, and correlation ID.
- Server-side DCOM impersonation, client blanket inspection, token and SID lookup.
- Security descriptor construction, DACL canonicalization, file-backed policy storage, or legacy NetAccess migration.
The immediate focus for it is access-control logic that needs the process identity or privileges but cannot open the process token with required rights. Keep it attached to that operation; the same numeric severity outside the owning API does not supply enough context.
Decisive interpretation boundary
Before choosing recovery, verify that process handle, desired token access, protection level, service identity, and native error are recorded. That boundary prevents it from being misclassified as corruption, network failure, or a reason for an unsafe automatic retry.
Also confirm that all observed objects, tokens, buffers, proxies, metadata files, or ACLs belong to the current operation generation and were not retained from an earlier attempt.
Correct handling and recovery
Request only necessary token rights, correct process protection or handle permissions, and keep process-token logic separate from client impersonation.
Repeat the operation after it only when the documented precondition, identity, apartment, object generation, buffer, or configuration has changed.
Lifetime, retry, and cleanup rules
After it, determine whether the current object, interface pointer, call context, token, stream, metadata reader, asynchronous operation, or access-control instance remains valid. Release only resources owned by the failing attempt, cancel callbacks through their documented mechanism, and avoid double close, double commit, repeated activation, or replay of a non-idempotent remote method.
The retry policy for it should state the trigger, maximum attempts, cancellation owner, and reconciliation step for effects that may have completed elsewhere.
Difference from nearby HRESULTs
It concerns server process identity; CO_E_FAILEDTOOPENTHREADTOKEN concerns a thread impersonation token.
Tests for it should force both results and verify that object lifetime, output use, and user messaging differ.
Practical scenario
A hardened service requests excessive token rights and is denied. The component reduces the request to <code>TOKEN_QUERY</code> and reads only required identity fields.
A regression test should reproduce it, assert the raw HRESULT and all relevant outputs, then correct only the decisive condition and verify the intended success or neighboring failure result.
References
- Microsoft: IAccessControl
- Microsoft: IAccessControl::IsAccessAllowed
- Microsoft: AccessCheck
- Microsoft: LookupAccountSidW
- Microsoft: LookupAccountNameW
- Microsoft: access control lists
- Microsoft: canonical ACE order
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.