| Previous | Next |
| ERROR_DIRECTORY_NOT_RM | ERROR_LOG_RESIZE_INVALID_SIZE |
ERROR_TRANSACTIONS_UNSUPPORTED_REMOTE
The requested transactional file operation crossed an unsupported remote boundary
ERROR_TRANSACTIONS_UNSUPPORTED_REMOTE is a Transactional NTFS (TxF) file-system status. TxF is an NTFS transactional facility and transacted file APIs do not imply that an arbitrary SMB server can participate in the same file-system transaction. This status means the remote path cannot provide the transactional semantics requested by the caller. It should be separated from a network outage or access-denied condition: the server was reached far enough to determine that transacted file operations are unsupported.
Resolve the final path and confirm whether it is local NTFS, a mapped drive, a UNC share, or a redirected namespace target. Library code often receives a path that looks local but resolves to remote storage through a mapping. Do not retry CreateFileTransacted against the same share expecting a transient recovery. Use a nontransacted file update protocol appropriate for remote storage, or move the transactional portion to a local NTFS volume and coordinate remote publication separately.
What to inspect
- Log the resolved volume or UNC target, not only the original path string.
- Distinguish unsupported remote transactions from transport and authentication failures.
- Redesign the remote update path instead of retrying the same TxF API.
References
- Microsoft: Transactional NTFS overview
- Microsoft: CreateFileTransacted and miniversion views
- Microsoft: TxF programming considerations and error range
- Microsoft: TxF limitations and recommended alternatives
Looking for a different code? Search another status or error code.