What does HRESULT 0x80010129 (CO_E_FAILEDTOSETDACL) mean?

 
Previous Next
CO_E_FAILEDTOQUERYCLIENTBLANKET CO_E_ACCESSCHECKFAILED

CO_E_FAILEDTOSETDACL

COM could not place a DACL in the security descriptor

CO_E_FAILEDTOSETDACL is HRESULT 2147549481 (0x80010129) from winerror.h. AllStat describes it as “Unable to set a discretionary ACL into a security descriptor.” 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.

Handling this result correctly requires the code-specific postcondition, not merely the fact that FAILED(hr) is true.

Decisive interpretation boundary

Before choosing recovery, verify that the ACL is structurally valid, self-relative versus absolute form is correct, and owner/group fields satisfy the consuming API. 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 construction or update of a COM access-control security descriptor where the discretionary ACL cannot be attached or validated. Keep it attached to that operation; the same numeric severity outside the owning API does not supply enough context.

Correct handling and recovery

Rebuild the descriptor with documented security APIs, validate every ACE and SID, and apply the DACL only after canonical ordering.

Reconcile partial output and server-side effects before attempting the operation again.

Difference from nearby HRESULTs

It is descriptor assembly failure; CO_E_ACCESSCHECKFAILED occurs when evaluating an assembled descriptor.

Merging it with the neighboring HRESULT would choose the wrong retry, recreation, authorization, or cleanup path.

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.

Change the smallest component, identity, ACL, package, or threading boundary that the evidence identifies, then reproduce the same operation. Define who owns retry, cancellation, cleanup, policy changes, package repair, and user-facing messaging for it.

Practical scenario

A configuration tool builds a self-relative descriptor but calls a setter that expects absolute pointers. It converts format explicitly and verifies the resulting DACL.

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.