What does HRESULT 0x80010127 (CO_E_TRUSTEEDOESNTMATCHCLIENT) mean?

 
Previous Next
CO_E_FAILEDTOGETTOKENINFO CO_E_FAILEDTOQUERYCLIENTBLANKET

CO_E_TRUSTEEDOESNTMATCHCLIENT

IAccessControl trustee does not match the DCOM caller

CO_E_TRUSTEEDOESNTMATCHCLIENT is HRESULT 2147549479 (0x80010127) from winerror.h. AllStat describes it as “The client who called IAccessControl::IsAccessPermitted was not the trustee provided to the method.” 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.

A generic “operation failed” message is insufficient for it because the recovery decision depends on the exact lifecycle, security, marshaling, or state condition.

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 the system DCOM access-control implementation receiving a trustee other than the actual client represented by the current distributed COM call. Keep this result 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 the trustee form, current caller identity, and <code>IAccessControl::IsAccessAllowed</code> invocation are captured inside the active call. 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

Pass the current client trustee required by the implementation, or use a different authorization design for arbitrary principals. Do not test another user through the caller-bound API.

Backoff alone is not a repair for it; a measurable state or configuration transition must justify another attempt.

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 is a semantic mismatch between trustee and caller; name- and SID-lookup HRESULTs concern principal translation.

Tests for it should force both results and verify that object lifetime, output use, and user messaging differ.

Practical scenario

A server tries to ask DCOMAccessControl whether an unrelated administrator could access the object. It changes to an explicit offline ACL check for hypothetical principals.

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

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