| Previous | Next |
| ERROR_FILE_IDENTITY_NOT_PERSISTENT | ERROR_CANT_CROSS_RM_BOUNDARY |
ERROR_CANT_BREAK_TRANSACTIONAL_DEPENDENCY
A transactional dependency protects the property that this operation would change
ERROR_CANT_BREAK_TRANSACTIONAL_DEPENDENCY is a Transactional NTFS (TxF) file-system status. TxF concurrency is not limited to byte-range writes. File identity, namespace, and other transactional properties can become dependencies for another transaction view. This error means changing the property would invalidate an assumption on which another active transaction depends, so TxF refuses the operation rather than break isolation.
Determine which property-changing operation failed and identify transactions that have the file open or locked. Use the locked-files and metadata controls to correlate the file with active transactions, then trace the earlier read or namespace operation that established the dependency. The safe resolution is to let the dependent transaction finish or reorder the application workflow. Retrying the same mutation in a tight loop only preserves the conflict.
What to inspect
- Log the exact file property or namespace operation that was rejected.
- Identify transactions holding the file and the order in which they accessed it.
- Resolve the dependency through transaction ordering or completion, not forced metadata changes.
References
- Microsoft: TxF isolation, locking, and file views
- Microsoft: listing files locked by a transaction
- Microsoft: retrieving TxF metadata and locking transaction
Looking for a different code? Search another status or error code.