What does HRESULT 0x8001012F (CO_E_NOMATCHINGSIDFOUND) mean?

 
Previous Next
CO_E_CONVERSIONFAILED CO_E_LOOKUPACCSIDFAILED

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 it because the recovery decision depends on the exact lifecycle, security, marshaling, or state condition.

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 translation from an accepted trustee name to a security identifier across local, domain, or trusted-domain account databases. Keep this result 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 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.

Difference from nearby HRESULTs

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

A support tool discussing it 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.

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

References

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