| Previous | Next |
| CO_E_SETSERLHNDLFAILED | CO_E_PATHTOOLONG |
CO_E_FAILEDTOGETWINDIR
COM access-control code could not obtain the Windows directory
CO_E_FAILEDTOGETWINDIR is HRESULT 2147549492 (0x80010134) from winerror.h. AllStat describes it as “Unable to obtain the Windows directory.” 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 legacy serialization or support code that requires the Windows directory for temporary or persistent access-control data. 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 environment, API buffer size, path redirection, service account, and native error are recorded. That boundary prevents it 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.
Correct handling and recovery
Use the documented Windows-directory API with dynamic sizing, avoid hard-coded paths, and verify filesystem access under the service identity.
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
A constrained service environment returns an unexpected directory length. The component adopts dynamic path sizing and a product-owned data directory.
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 path discovery failure; CO_E_PATHTOOLONG occurs after a path is built beyond supported limits.
The distinction around it should be represented explicitly in control flow and operational dashboards.
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.
Document the owner of the boundary so future occurrences can be correlated across client, proxy, server, package, and security logs. 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.