| Previous | Next |
| ERROR_DATA_LOST_REPAIR | ERROR_TM_IDENTITY_MISMATCH |
ERROR_SPARSE_NOT_ALLOWED_IN_TRANSACTION
TxF blocks the sparse-file metadata transition inside an active transaction
ERROR_SPARSE_NOT_ALLOWED_IN_TRANSACTION is a Transactional NTFS (TxF) file-system status. Sparse-file controls change how ranges of a file consume physical allocation. The TxF status range explicitly defines sparse operations as unavailable while a transaction is active on the file. This is not an indication that the volume lacks NTFS sparse-file support; the unsupported part is combining the allocation-state transition with active TxF processing.
Trace the sparse control or filesystem library call and identify the transaction that has the file open. Finish the transaction and close transacted handles before changing sparse state or manipulating sparse allocation ranges. If sparse layout is a creation requirement, prepare the file outside TxF and then transact only supported content and namespace changes. Reissuing the same FSCTL through the transacted handle will preserve the restriction.
What to inspect
- Identify the sparse-file FSCTL or allocation operation that overlaps TxF.
- Resolve the transaction and close its handles before changing sparse state.
- Prepare sparse layout outside the transaction when the application requires both features.
References
- MS-ERREF: TxF and KTM status definitions
- Microsoft: TxF programming considerations and error range
- Microsoft: CreateFileTransacted and miniversion views
- Microsoft: TxF limitations and recommended alternatives
Looking for a different code? Search another status or error code.