| Previous | Next |
| ERROR_TM_IDENTITY_MISMATCH | ERROR_CANNOT_ACCEPT_TRANSACTED_WORK |
ERROR_FLOATED_SECTION
The section object outlived the transactional file view that supplied its data
ERROR_FLOATED_SECTION is a Transactional NTFS (TxF) file-system status. A mapped section can remain referenced independently of the original file handle. TxF may invalidate file handles when a transaction ends or rolls back, and the status definition describes a section that has been floated as a result of transaction completion. There is no valid data view for further I/O through that section.
Track section and mapped-view lifetime as part of the transaction scope. Unmap views and close section handles before commit, rollback, or rollback to a savepoint that can invalidate the associated file view. After the outcome, create a new file handle and mapping against the desired committed state. Do not interpret a successfully mapped virtual address as proof that the backing TxF view remains valid; the section object can outlive that transactional association.
What to inspect
- Log file, section, and mapped-view handles under the same transaction ID.
- Unmap views before transaction outcome or savepoint rollback.
- Create a fresh mapping from the post-transaction file view after completion.
References
- MS-ERREF: TxF and KTM status definitions
- Microsoft: CreateFileTransacted and miniversion views
- Microsoft: transacted file handles and transaction binding
- Microsoft: TxF isolation, locking, and file views
Looking for a different code? Search another status or error code.