| Previous | Next |
| CO_E_LOOKUPACCNAMEFAILED | CO_E_FAILEDTOGETWINDIR |
CO_E_SETSERLHNDLFAILED
COM could not set or reset its ACL serialization handle
CO_E_SETSERLHNDLFAILED is HRESULT 2147549491 (0x80010133) from winerror.h. AllStat describes it as “Unable to set or reset a serialization handle.” 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.
Telemetry should preserve this result as a separate outcome rather than merging it with unrelated COM or WinRT failures.
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 IAccessControl persistence or stream serialization that uses an internal handle to coordinate ACL encoding and file operations. Keep it 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 handle state, operation phase, stream or file owner, and previous cleanup are reconstructed. 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.
Correct handling and recovery
Abort the serialization transaction, close valid resources once, recreate the handle, and prevent concurrent use of the same serializer.
Reconcile partial output and server-side effects before attempting the operation again.
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.
Practical scenario
Two threads serialize access data through one COM access-control instance. A per-instance lock and scoped handle make serialization single-owner.
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.
Difference from nearby HRESULTs
It is serializer state management; create/close file HRESULTs identify underlying resource operations.
Tests for it should force both results and verify that object lifetime, output use, and user messaging differ.
Developer and administrator guidance
Dashboards should classify it by its actual cause category—lifetime, timing, apartment, marshaling, identity, authorization, format, buffer, or storage—rather than grouping every COM failure under one counter.
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.
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.