| Previous | Next |
| ERROR_CANT_BREAK_TRANSACTIONAL_DEPENDENCY | ERROR_TXF_DIR_NOT_EMPTY |
ERROR_CANT_CROSS_RM_BOUNDARY
A single file cannot be managed simultaneously by two transactional resource managers
ERROR_CANT_CROSS_RM_BOUNDARY is a Transactional NTFS (TxF) file-system status. TxF resource managers provide the file-system side of transaction participation. A transactional file object must belong to a coherent RM context so logging, recovery, and outcome processing agree on its state. This status is returned when an operation would involve one file with two transactional resource managers.
Resolve both source and destination paths to their volumes and resource-manager contexts. Moves, links, restore workflows, or secondary-RM layouts can accidentally cross an RM boundary even when paths appear related at the application level. Keep the file operation inside one RM or split the workflow into coordinated steps with a clear commit boundary. Do not copy TxF metadata from one RM context to another to make the operation appear local.
What to inspect
- Map every participating path to its volume and TxF resource manager.
- Check rename, link, move, and restore operations for cross-RM transitions.
- Split the workflow at a transaction boundary when one file would otherwise span two RMs.
References
- Microsoft: Transactional NTFS overview
- Microsoft: querying TxF resource-manager state
- Microsoft: TxF filesystem control codes
- MS-FSCC: NTFS attribute types including transactional data
Looking for a different code? Search another status or error code.