What does HRESULT 0x80010131 (CO_E_NOMATCHINGNAMEFOUND) mean?

CO_E_NOMATCHINGNAMEFOUND

No trustee name corresponds to the supplied SID

CO_E_NOMATCHINGNAMEFOUND is HRESULT 2147549489 (0x80010131) from winerror.h. AllStat describes it as “Unable to find a trustee name that corresponds to a security identifier 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.

The caller should keep CO_E_NOMATCHINGNAMEFOUND intact through logging, exception translation, and RPC or language projection boundaries.

Where it is encountered

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

The immediate focus for CO_E_NOMATCHINGNAMEFOUND is a structurally valid SID that cannot be mapped to a current account name in local or trusted account databases. Keep CO_E_NOMATCHINGNAMEFOUND attached to that operation; the same numeric severity outside the owning API does not supply enough context.

Evidence and telemetry

• Preserve SID string and binary validation for CO_E_NOMATCHINGNAMEFOUND.
• Preserve source ACL or token for CO_E_NOMATCHINGNAMEFOUND.
• Preserve local and trusted domains queried for CO_E_NOMATCHINGNAMEFOUND.
• Preserve account deletion or domain retirement evidence for CO_E_NOMATCHINGNAMEFOUND.
• Preserve administrator replacement action for CO_E_NOMATCHINGNAMEFOUND.

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

Decisive interpretation boundary

Before choosing recovery, verify that the SID origin and account deletion, domain removal, trust, and connectivity conditions are distinguished. Validate this condition for CO_E_NOMATCHINGNAMEFOUND using the owning API state, not an inferred UI symptom.

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

Preserve the SID in ACLs and logs, display a SID-form fallback, and let administrators replace orphaned principals deliberately.

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

Diagnostic sequence

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

Lifetime, retry, and cleanup rules

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

Practical scenario

An ACL contains a SID from a decommissioned domain. The management UI shows the raw SID and supports explicit replacement without deleting the ACE silently.

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

Difference from nearby HRESULTs

CO_E_NOMATCHINGNAMEFOUND describes absent SID-to-name mapping; CO_E_INVALIDSID says the SID itself is malformed.

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

Developer and administrator guidance

Dashboards should classify CO_E_NOMATCHINGNAMEFOUND by its actual cause category—lifetime, timing, apartment, marshaling, identity, authorization, format, buffer, or storage—rather than grouping every COM failure under one counter.

After CO_E_NOMATCHINGNAMEFOUND, avoid broad permission grants or system-wide resets unless code-specific evidence proves a global configuration problem. Define who owns retry, cancellation, cleanup, policy changes, package repair, and user-facing messaging for CO_E_NOMATCHINGNAMEFOUND.

References

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

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