| Previous | Next |
| CO_E_NOMATCHINGNAMEFOUND | CO_E_SETSERLHNDLFAILED |
CO_E_LOOKUPACCNAMEFAILED
LookupAccountName failed during COM access processing
CO_E_LOOKUPACCNAMEFAILED is HRESULT 2147549490 (0x80010132) from winerror.h. The documented description is “The system function, LookupAccountName, failed.” The relevant context is the COM IAccessControl, DCOM client identity, trustee translation, token inspection, security descriptor, ACL, or serialization workflow.
The hexadecimal value and symbolic name of this result should remain attached to the originating API and operation instance.
What to verify
Verify that the normalized name, target system, two-call buffer sequence, domain result, SID type, and native error are known. That boundary prevents this result from being misclassified as corruption, network failure, or a reason for an unsafe automatic retry.
Where it is encountered
- This result can be returned during IAccessControl initialization, access checks, owner/trustee processing, and serialized ACL persistence.
- This result can be returned during server-side DCOM impersonation, client blanket inspection, token and SID lookup.
- It can be returned during security descriptor construction, DACL canonicalization, file-backed policy storage, or legacy NetAccess migration.
The immediate focus is translation from account name to SID where the Win32 lookup call cannot complete because of buffers, connectivity, trust, ambiguity, or native errors.
Correct handling and recovery
Correct buffer handling and account qualification, restore directory access where needed, and reject ambiguous or unresolved trustees.
Difference from nearby HRESULTs
It wraps the lookup API; CO_E_NOMATCHINGSIDFOUND is the semantic no-match outcome exposed by COM access control.
The distinction around it should be represented explicitly in control flow and operational dashboards.
Developer and administrator guidance
After it, avoid broad permission grants or system-wide resets unless code-specific evidence proves a global configuration problem.
Practical scenario
A service resolves an unqualified account on a member server and selects the wrong search scope. Configuration requires explicit domain qualification.
References
Looking for a different code? Search another status or error code.