Site icon EfmSoft

What does HRESULT 0x80010131 (CO_E_NOMATCHINGNAMEFOUND) mean?

 
Previous Next
CO_E_LOOKUPACCSIDFAILED CO_E_LOOKUPACCNAMEFAILED

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 this result intact through logging, exception translation, and RPC or language projection boundaries.

Where it is encountered

The immediate focus for it is a structurally valid SID that cannot be mapped to a current account name in local or trusted account databases. Keep it 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 SID origin and account deletion, domain removal, trust, and connectivity conditions are distinguished. Validate this condition for it using the owning API state, not an inferred UI symptom.

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.

Reconcile partial output and server-side effects before attempting the operation again.

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

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 it, 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

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

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

Developer and administrator guidance

Dashboards should classify it 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 it, 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 it.

References


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

Exit mobile version