| Previous | Next |
| CO_E_NOMATCHINGSIDFOUND | CO_E_NOMATCHINGNAMEFOUND |
CO_E_LOOKUPACCSIDFAILED
LookupAccountSid failed during COM access processing
CO_E_LOOKUPACCSIDFAILED is HRESULT 2147549488 (0x80010130) from winerror.h. AllStat describes it as “The system function, LookupAccountSID, failed.” 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 a SID to account and domain names where the Win32 lookup call fails. 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 SID is valid and the target lookup system, buffer-sizing sequence, domain trust, and native error are recorded. 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 wraps API failure; CO_E_NOMATCHINGNAMEFOUND emphasizes that no account name could be found for the SID.
A support tool discussing it should name the neighboring result only after the originating API and decisive state are known.
Correct handling and recovery
Use the required-size pattern, allow unresolved SIDs to remain as canonical SID strings, and retry directory lookup only after connectivity or trust changes.
Reconcile partial output and server-side effects before attempting the operation again.
Practical scenario
An offline laptop cannot contact a trusted domain for an old SID. The ACL editor displays the SID string and resolves the name after connectivity returns.
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
- Microsoft: IAccessControl
- Microsoft: IAccessControl::IsAccessAllowed
- Microsoft: AccessCheck
- Microsoft: LookupAccountSidW
- Microsoft: LookupAccountNameW
- Microsoft: access control lists
- Microsoft: canonical ACE order
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.