What does HRESULT 0x8001012C (CO_E_WRONGTRUSTEENAMESYNTAX) mean?

 
Previous Next
CO_E_NETACCESSAPIFAILED CO_E_INVALIDSID

CO_E_WRONGTRUSTEENAMESYNTAX

Trustee name has invalid domain and account syntax

CO_E_WRONGTRUSTEENAMESYNTAX is HRESULT 2147549484 (0x8001012C) from winerror.h. AllStat describes it as “One of the trustee strings provided by the user did not conform to the <Domain>\<Name> syntax and it was not the "*" string.” 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.

Decisive interpretation boundary

Before choosing recovery, verify that the input encoding, separator, domain, account, escaping, and intended trustee type are validated before lookup. If this condition cannot be proven for it, stop before consuming outputs or repeating side effects.

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.

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 a trustee string that is neither the accepted wildcard nor a supported <code>Domain\Name</code> principal form. Keep it attached to that operation; the same numeric severity outside the owning API does not supply enough context.

Correct handling and recovery

Normalize through an identity-aware parser, reject ambiguous display names, and prefer SID-based persistence after a trusted lookup.

An unchanged retry loop for it can duplicate effects, deepen reentrancy, or hide an invalid lifetime transition.

Difference from nearby HRESULTs

It is parser-level; CO_E_NOMATCHINGSIDFOUND is a well-formed name that cannot be resolved.

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

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.

Practical scenario

A policy import uses an email-style user principal name where the legacy interface requires <code>DOMAIN\user</code>. Import translates through a verified directory lookup.

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.