| Previous | Next |
| ERROR_LOG_GROWTH_FAILED | ERROR_TXF_METADATA_ALREADY_PRESENT |
ERROR_TRANSACTED_MAPPING_UNSUPPORTED_REMOTE
TxF does not support mapping a remote transactional file into memory
ERROR_TRANSACTED_MAPPING_UNSUPPORTED_REMOTE is a Transactional NTFS (TxF) file-system status. The documented status is specifically about creating a mapped section for a remote file under a transaction. File mapping creates a section object whose cached and paged I/O lifetime differs from ordinary ReadFile or WriteFile calls. Combining that model with a remote transactional file view is not supported.
Trace CreateFileMapping or section creation back to the transacted file handle and confirm whether the resolved path is remote. Libraries can memory-map files automatically for parsers or databases, so the mapping may be several layers above the TxF open. For a remote file, choose explicit I/O without a mapped section or remove TxF from the remote path. Moving the mapping call earlier or retrying after reconnect does not change the unsupported combination.
What to inspect
- Identify the section or CreateFileMapping call using the transacted handle.
- Confirm whether the final file location is remote after path resolution.
- Use explicit file I/O or redesign the transaction boundary instead of mapping the remote file.
References
- MS-ERREF: TxF and KTM status definitions
- 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.