| Previous | Next |
| STATUS_CANT_BREAK_TRANSACTIONAL_DEPENDENCY | STATUS_TXF_DIR_NOT_EMPTY |
STATUS_CANT_CROSS_RM_BOUNDARY
The operation crosses resource-manager ownership
STATUS_CANT_CROSS_RM_BOUNDARY is about the boundary between transactional resource managers. TxF uses a resource manager for transactional file-system work on a volume. Some operations cannot make one file participate through two different resource managers at once.
This typically matters with moves, links, streams, or namespace operations across volumes, mount points, or directories controlled by different TxF resource-manager instances. The path syntax may be legal, but the transactional ownership model is not.
What to check
- Whether source and target are on the same NTFS volume and same TxF resource manager.
- Mount points, reparse points, junctions, or remote paths that hide a resource-manager boundary.
- Operations that combine handles opened in different transaction managers or resource managers.
- Whether the work must be split into separate transactions or handled without TxF.
Useful distinction
This is not a path-not-found or access-denied condition. It names a transaction resource-manager boundary that the requested file-system operation is not allowed to cross.
References
- Microsoft: Kernel Transaction Manager
- Microsoft: KTM resource managers
- Microsoft: KTM objects
- Microsoft: Transactional NTFS overview
Looking for a different code? Search another status or error code.