| Previous | Next |
| CO_E_ACESINWRONGORDER | CO_E_FAILEDTOOPENPROCESSTOKEN |
CO_E_INCOMPATIBLESTREAMVERSION
Serialized IAccessControl stream version is unsupported
CO_E_INCOMPATIBLESTREAMVERSION is HRESULT 2147549499 (0x8001013B) from winerror.h. AllStat describes it as “The version of ACL format in the stream is not supported by this implementation of IAccessControl.” 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.
A generic “operation failed” message is insufficient for it because the recovery decision depends on the exact lifecycle, security, marshaling, or state condition.
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 deserialization of ACL state written in a format version the current implementation does not understand. Keep this result 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 stream header, version, producer component, architecture, length, and integrity are known before migration. If this condition cannot be proven for it, stop before consuming outputs or repeating side effects.
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.
Difference from nearby HRESULTs
It is a recognized but unsupported format version; CO_E_DECODEFAILED means content cannot be decoded even under an expected format.
Merging it with the neighboring HRESULT would choose the wrong retry, recreation, authorization, or cleanup path.
Correct handling and recovery
Use a supported reader or migration tool, preserve the original stream, and rewrite only after semantic validation. Do not reinterpret unknown fields.
Reconcile partial output and server-side effects before attempting the operation again.
Practical scenario
A downgraded service reads ACL data produced by a newer build. Deployment restores the compatible reader and exports a backward-compatible policy.
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.
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.
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.