| Previous | Next |
| STATUS_TRANSACTIONAL_OPEN_NOT_ALLOWED | STATUS_TRANSACTION_REQUIRED_PROMOTION |
STATUS_TRANSACTED_MAPPING_UNSUPPORTED_REMOTE
A transacted memory mapping was requested for a remote file
STATUS_TRANSACTED_MAPPING_UNSUPPORTED_REMOTE reports a TxF limitation: creating a mapped section for a remote file while using a transaction is not supported. The file may be reachable and the transaction may be valid, but this combination is not allowed.
Memory mapping has additional coherency and flush semantics. TxF guidance also warns that mapped sections must be flushed and closed before commit; adding remote file-system behavior makes that model unsupported for this operation.
What to check
- Whether the path is a UNC path, redirected drive, WebDAV path, SMB share, or another remote file system.
- Whether the code creates a section object or memory map after opening a transacted file handle.
- Whether ordinary buffered I/O can replace the mapping for this transaction.
- Whether the operation should be performed locally and then copied after commit.
Useful distinction
This is narrower than STATUS_TRANSACTIONS_UNSUPPORTED_REMOTE. It specifically concerns memory-mapped I/O under a transaction for a remote file.
References
- Microsoft: Transactional NTFS overview
- Microsoft: How to use Transactional NTFS
- Microsoft: Kernel Transaction Manager
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.