| Previous | Next |
| STATUS_EFS_NOT_ALLOWED_IN_TRANSACTION | STATUS_TRANSACTED_MAPPING_UNSUPPORTED_REMOTE |
STATUS_TRANSACTIONAL_OPEN_NOT_ALLOWED
STATUS_TRANSACTIONAL_OPEN_NOT_ALLOWED means that the object being opened does not support the requested transactional access. It is not a statement that the current transaction is invalid; the operation itself is excluded from the transactional model.
Compare it with STATUS_TRANSACTIONS_UNSUPPORTED_REMOTE. A remote target can cause the latter even for an otherwise valid transacted file API. This status can occur for an unsupported object class or access scenario regardless of whether the target is local.
The object or operation has no transactional-open support
- Identify the exact API, object type, access flags, and whether the target is a file, directory, device, named object, or another special endpoint.
- Check the API-specific transaction support rather than assuming every handle-creating API accepts a KTM transaction handle.
- Move only the supported portion of the workflow into a transaction; do not silently perform the excluded operation outside it without defining consistency consequences.
References
- Microsoft: CreateFileTransacted
- Microsoft: Kernel Transaction Manager overview
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.