| Previous | Next |
| ERROR_BAD_CLUSTERS | ERROR_VOLUME_DIRTY |
ERROR_COMPRESSION_NOT_ALLOWED_IN_TRANSACTION
TxF does not allow the file compression state to be changed inside the active transaction
ERROR_COMPRESSION_NOT_ALLOWED_IN_TRANSACTION is a Transactional NTFS (TxF) file-system status. CreateFileTransacted documentation states that transactional opens cannot be used to control compression on a file or directory. The corresponding status therefore identifies an unsupported interaction between TxF and an NTFS compression-state operation, not an unsupported compression format or lack of disk space.
Find the compression API or filesystem control that runs while the file remains in a transaction. Resolve the transaction, close its transacted handles, and then change the compression attribute through the normal filesystem path. If a deployment process needs both atomic publication and compressed files, create or compress the prepared artifact before entering the TxF publication transaction. Reordering writes inside the same active transaction does not remove the restriction.
What to inspect
- Trace compression-state changes and the transaction lifetime for the file.
- Commit or roll back and close transacted handles before changing compression.
- Prepare compressed content before the transactional publication step when possible.
References
- Microsoft: CreateFileTransacted and miniversion views
- MS-ERREF: TxF and KTM status definitions
- Microsoft: TxF programming considerations and error range
- Microsoft: TxF limitations and recommended alternatives
Looking for a different code? Search another status or error code.