What does HRESULT 0x8001012C (CO_E_WRONGTRUSTEENAMESYNTAX) mean?

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 CO_E_WRONGTRUSTEENAMESYNTAX 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 CO_E_WRONGTRUSTEENAMESYNTAX, stop before consuming outputs or repeating side effects.

For CO_E_WRONGTRUSTEENAMESYNTAX, 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

• CO_E_WRONGTRUSTEENAMESYNTAX can be returned during IAccessControl initialization, access checks, owner/trustee processing, and serialized ACL persistence. For CO_E_WRONGTRUSTEENAMESYNTAX, record the interface, method, component version, thread, apartment, process, and correlation ID.
• CO_E_WRONGTRUSTEENAMESYNTAX can be returned during server-side DCOM impersonation, client blanket inspection, token and SID lookup. For CO_E_WRONGTRUSTEENAMESYNTAX, record the interface, method, component version, thread, apartment, process, and correlation ID.
• CO_E_WRONGTRUSTEENAMESYNTAX can be returned during security descriptor construction, DACL canonicalization, file-backed policy storage, or legacy NetAccess migration. For CO_E_WRONGTRUSTEENAMESYNTAX, record the interface, method, component version, thread, apartment, process, and correlation ID.

The immediate focus for CO_E_WRONGTRUSTEENAMESYNTAX is a trustee string that is neither the accepted wildcard nor a supported <code>Domain\Name</code> principal form. Keep CO_E_WRONGTRUSTEENAMESYNTAX attached to that operation; the same numeric severity outside the owning API does not supply enough context.

Diagnostic sequence

• Capture the raw unsigned value 0x8001012C and symbolic name CO_E_WRONGTRUSTEENAMESYNTAX before a language projection, exception wrapper, or generic COM helper replaces it.
• Identify the exact interface, method, callback, activation request, metadata query, access-control operation, or marshaling boundary that returned CO_E_WRONGTRUSTEENAMESYNTAX.
• Reconstruct the operation timeline for CO_E_WRONGTRUSTEENAMESYNTAX, including object creation, thread or apartment initialization, security setup, callbacks, mutations, shutdown, and cleanup.
• Prove the decisive condition: the input encoding, separator, domain, account, escaping, and intended trustee type are validated before lookup.
• Inspect every output parameter, handle, interface pointer, token, SID, ACL, stream, buffer, server-side object, or asynchronous result produced before CO_E_WRONGTRUSTEENAMESYNTAX.
• Reproduce CO_E_WRONGTRUSTEENAMESYNTAX with the smallest safe input, change only the suspected precondition, and verify that both the HRESULT and postcondition change as predicted.

Evidence and telemetry

• Preserve raw trustee string and encoding for CO_E_WRONGTRUSTEENAMESYNTAX.
• Preserve domain/account split for CO_E_WRONGTRUSTEENAMESYNTAX.
• Preserve trustee form and wildcard handling for CO_E_WRONGTRUSTEENAMESYNTAX.
• Preserve normalization result for CO_E_WRONGTRUSTEENAMESYNTAX.
• Preserve subsequent SID lookup for CO_E_WRONGTRUSTEENAMESYNTAX.

For CO_E_WRONGTRUSTEENAMESYNTAX, also record UTC time, process and thread IDs, apartment type, component version, security or package identity where relevant, and a correlation ID. For CO_E_WRONGTRUSTEENAMESYNTAX, use hashes, lengths, GUIDs, and SID strings rather than logging confidential payloads or credentials.

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 CO_E_WRONGTRUSTEENAMESYNTAX can duplicate effects, deepen reentrancy, or hide an invalid lifetime transition.

Difference from nearby HRESULTs

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

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

Lifetime, retry, and cleanup rules

After CO_E_WRONGTRUSTEENAMESYNTAX, determine whether the current object, interface pointer, call context, token, stream, metadata reader, asynchronous operation, or access-control instance remains valid. For CO_E_WRONGTRUSTEENAMESYNTAX, 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 CO_E_WRONGTRUSTEENAMESYNTAX should state the trigger, maximum attempts, cancellation owner, and reconciliation step for effects that may have completed elsewhere.

Developer and administrator guidance

When CO_E_WRONGTRUSTEENAMESYNTAX crosses native, managed, scripting, RPC, or WinRT projection boundaries, preserve the unsigned 32-bit HRESULT. Unit tests for CO_E_WRONGTRUSTEENAMESYNTAX should assert the code-specific postcondition and resource ownership, not merely that an exception was thrown.

Administrators investigating CO_E_WRONGTRUSTEENAMESYNTAX should preserve first-occurrence evidence before restarting COM servers, repairing packages, editing DCOM policy, or replacing serialized access data. Define who owns retry, cancellation, cleanup, policy changes, package repair, and user-facing messaging for CO_E_WRONGTRUSTEENAMESYNTAX.

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 CO_E_WRONGTRUSTEENAMESYNTAX, 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 — official Microsoft documentation relevant to CO_E_WRONGTRUSTEENAMESYNTAX.
• Microsoft: IAccessControl::IsAccessAllowed — official Microsoft documentation relevant to CO_E_WRONGTRUSTEENAMESYNTAX.
• Microsoft: AccessCheck — official Microsoft documentation relevant to CO_E_WRONGTRUSTEENAMESYNTAX.
• Microsoft: LookupAccountSidW — official Microsoft documentation relevant to CO_E_WRONGTRUSTEENAMESYNTAX.
• Microsoft: LookupAccountNameW — official Microsoft documentation relevant to CO_E_WRONGTRUSTEENAMESYNTAX.
• Microsoft: access control lists — official Microsoft documentation relevant to CO_E_WRONGTRUSTEENAMESYNTAX.
• Microsoft: canonical ACE order — official Microsoft documentation relevant to CO_E_WRONGTRUSTEENAMESYNTAX.
• Microsoft: HRESULT values — official Microsoft documentation relevant to CO_E_WRONGTRUSTEENAMESYNTAX.

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