What does HRESULT 0x80010132 (CO_E_LOOKUPACCNAMEFAILED) mean?

CO_E_LOOKUPACCNAMEFAILED

LookupAccountName failed during COM access processing

CO_E_LOOKUPACCNAMEFAILED is HRESULT 2147549490 (0x80010132) from winerror.h. AllStat describes it as “The system function, LookupAccountName, 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.

The hexadecimal value and symbolic name CO_E_LOOKUPACCNAMEFAILED should remain attached to the originating API and operation generation.

Decisive interpretation boundary

Before choosing recovery, verify that the normalized name, target system, two-call buffer sequence, domain result, SID type, and native error are known. That boundary prevents CO_E_LOOKUPACCNAMEFAILED from being misclassified as corruption, network failure, or a reason for an unsafe automatic retry.

For CO_E_LOOKUPACCNAMEFAILED, 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.

Where it is encountered

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

The immediate focus for CO_E_LOOKUPACCNAMEFAILED is translation from account name to SID where the Win32 lookup call cannot complete because of buffers, connectivity, trust, ambiguity, or native errors. Keep CO_E_LOOKUPACCNAMEFAILED attached to that operation; the same numeric severity outside the owning API does not supply enough context.

Diagnostic sequence

• Capture the raw unsigned value 0x80010132 and symbolic name CO_E_LOOKUPACCNAMEFAILED 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_LOOKUPACCNAMEFAILED.
• Reconstruct the operation timeline for CO_E_LOOKUPACCNAMEFAILED, including object creation, thread or apartment initialization, security setup, callbacks, mutations, shutdown, and cleanup.
• Prove the decisive condition: the normalized name, target system, two-call buffer sequence, domain result, SID type, and native error are known.
• Inspect every output parameter, handle, interface pointer, token, SID, ACL, stream, buffer, server-side object, or asynchronous result produced before CO_E_LOOKUPACCNAMEFAILED.
• Reproduce CO_E_LOOKUPACCNAMEFAILED with the smallest safe input, change only the suspected precondition, and verify that both the HRESULT and postcondition change as predicted.

Evidence and telemetry

• Preserve input account and target system for CO_E_LOOKUPACCNAMEFAILED.
• Preserve SID and domain buffer requirements for CO_E_LOOKUPACCNAMEFAILED.
• Preserve native LookupAccountName error for CO_E_LOOKUPACCNAMEFAILED.
• Preserve SID_NAME_USE value for CO_E_LOOKUPACCNAMEFAILED.
• Preserve qualified retry result for CO_E_LOOKUPACCNAMEFAILED.

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

Correct handling and recovery

Correct buffer handling and account qualification, restore directory access where needed, and reject ambiguous or unresolved trustees.

Backoff alone is not a repair for CO_E_LOOKUPACCNAMEFAILED; a measurable state or configuration transition must justify another attempt.

Difference from nearby HRESULTs

CO_E_LOOKUPACCNAMEFAILED wraps the lookup API; CO_E_NOMATCHINGSIDFOUND is the semantic no-match outcome exposed by COM access control.

The distinction around CO_E_LOOKUPACCNAMEFAILED should be represented explicitly in control flow and operational dashboards.

Lifetime, retry, and cleanup rules

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

Developer and administrator guidance

When CO_E_LOOKUPACCNAMEFAILED crosses native, managed, scripting, RPC, or WinRT projection boundaries, preserve the unsigned 32-bit HRESULT. Unit tests for CO_E_LOOKUPACCNAMEFAILED should assert the code-specific postcondition and resource ownership, not merely that an exception was thrown.

After CO_E_LOOKUPACCNAMEFAILED, 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_LOOKUPACCNAMEFAILED.

Practical scenario

A service resolves an unqualified account on a member server and selects the wrong search scope. Configuration requires explicit domain qualification.

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

References

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

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