What does HRESULT 0x80010132 (CO_E_LOOKUPACCNAMEFAILED) mean?

 
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. 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 this result 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 this result from being misclassified as corruption, network failure, or a reason for an unsafe automatic retry.

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

  • This result can be returned during IAccessControl initialization, access checks, owner/trustee processing, and serialized ACL persistence. Record the interface, method, component version, thread, apartment, process, and correlation ID.
  • 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 for it is translation from account name to SID where the Win32 lookup call cannot complete because of buffers, connectivity, trust, ambiguity, or native errors. Keep it attached to that operation; the same numeric severity outside the owning API does not supply enough context.

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 it; a measurable state or configuration transition must justify another attempt.

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.

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.

Developer and administrator guidance

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

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.

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 it, assert the raw HRESULT and all relevant outputs, then correct only the decisive condition and verify the intended success or neighboring failure result.

References

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