What does HRESULT 0x8001012F (CO_E_NOMATCHINGSIDFOUND) mean?

CO_E_NOMATCHINGSIDFOUND

No SID corresponds to the supplied trustee name

CO_E_NOMATCHINGSIDFOUND is HRESULT 2147549487 (0x8001012F) from winerror.h. AllStat describes it as “Unable to find a security identifier that corresponds to a trustee string provided by the user.” 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 CO_E_NOMATCHINGSIDFOUND because the recovery decision depends on the exact lifecycle, security, marshaling, or state condition.

Diagnostic sequence

• Capture the raw unsigned value 0x8001012F and symbolic name CO_E_NOMATCHINGSIDFOUND 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_NOMATCHINGSIDFOUND.
• Reconstruct the operation timeline for CO_E_NOMATCHINGSIDFOUND, including object creation, thread or apartment initialization, security setup, callbacks, mutations, shutdown, and cleanup.
• Prove the decisive condition: the lookup target system, normalized name, domain connectivity, trust path, and account lifecycle are known.
• Inspect every output parameter, handle, interface pointer, token, SID, ACL, stream, buffer, server-side object, or asynchronous result produced before CO_E_NOMATCHINGSIDFOUND.
• Reproduce CO_E_NOMATCHINGSIDFOUND with the smallest safe input, change only the suspected precondition, and verify that both the HRESULT and postcondition change as predicted.

Where it is encountered

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

The immediate focus for CO_E_NOMATCHINGSIDFOUND is translation from an accepted trustee name to a security identifier across local, domain, or trusted-domain account databases. Keep CO_E_NOMATCHINGSIDFOUND 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 lookup target system, normalized name, domain connectivity, trust path, and account lifecycle are known. Validate this condition for CO_E_NOMATCHINGSIDFOUND using the owning API state, not an inferred UI symptom.

For CO_E_NOMATCHINGSIDFOUND, 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.

Evidence and telemetry

• Preserve normalized trustee name for CO_E_NOMATCHINGSIDFOUND.
• Preserve lookup computer and domain for CO_E_NOMATCHINGSIDFOUND.
• Preserve directory and trust availability for CO_E_NOMATCHINGSIDFOUND.
• Preserve account lifecycle state for CO_E_NOMATCHINGSIDFOUND.
• Preserve resolved replacement SID for CO_E_NOMATCHINGSIDFOUND.

For CO_E_NOMATCHINGSIDFOUND, 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_NOMATCHINGSIDFOUND, use hashes, lengths, GUIDs, and SID strings rather than logging confidential payloads or credentials.

Difference from nearby HRESULTs

CO_E_NOMATCHINGSIDFOUND is name-to-SID failure; CO_E_LOOKUPACCNAMEFAILED says the underlying lookup API itself failed.

A support tool discussing CO_E_NOMATCHINGSIDFOUND should name the neighboring result only after the originating API and decisive state are known.

Correct handling and recovery

Confirm the account and domain, retry only after directory or trust recovery, and store the resolved SID rather than repeatedly depending on display-name lookup.

For CO_E_NOMATCHINGSIDFOUND, reconcile partial output and server-side effects before attempting the operation again.

Practical scenario

A service policy references a deleted domain account. Administration selects the replacement account and persists its new SID after verification.

A regression test should reproduce CO_E_NOMATCHINGSIDFOUND, assert the raw HRESULT and all relevant outputs, then correct only the decisive condition and verify the intended success or neighboring failure result.

Lifetime, retry, and cleanup rules

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

Developer and administrator guidance

A support bundle for CO_E_NOMATCHINGSIDFOUND should include first-occurrence logs, interface and component identity, object generation, relevant policy, and safe hashes. For CO_E_NOMATCHINGSIDFOUND, redact credentials, tokens, private metadata, ACL identities, and serialized payload contents.

Administrators investigating CO_E_NOMATCHINGSIDFOUND 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_NOMATCHINGSIDFOUND.

References

• Microsoft: IAccessControl — official Microsoft documentation relevant to CO_E_NOMATCHINGSIDFOUND.
• Microsoft: IAccessControl::IsAccessAllowed — official Microsoft documentation relevant to CO_E_NOMATCHINGSIDFOUND.
• Microsoft: AccessCheck — official Microsoft documentation relevant to CO_E_NOMATCHINGSIDFOUND.
• Microsoft: LookupAccountSidW — official Microsoft documentation relevant to CO_E_NOMATCHINGSIDFOUND.
• Microsoft: LookupAccountNameW — official Microsoft documentation relevant to CO_E_NOMATCHINGSIDFOUND.
• Microsoft: access control lists — official Microsoft documentation relevant to CO_E_NOMATCHINGSIDFOUND.
• Microsoft: canonical ACE order — official Microsoft documentation relevant to CO_E_NOMATCHINGSIDFOUND.
• Microsoft: HRESULT values — official Microsoft documentation relevant to CO_E_NOMATCHINGSIDFOUND.

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