| Previous | Next |
| STATUS_TM_IDENTITY_MISMATCH | STATUS_CANNOT_ACCEPT_TRANSACTED_WORK |
STATUS_FLOATED_SECTION
The section object was separated from valid transactional data
STATUS_FLOATED_SECTION is associated with memory-mapped I/O and TxF transaction completion. A section object can become floated when the transaction ends, leaving no valid data path for the I/O attempted through that section.
This is why TxF guidance emphasizes flushing and closing mapped sections before committing a transaction. If the mapping survives the transaction transition, subsequent I/O may no longer have a valid transaction-backed file view.
What to check
- Memory mappings created from transacted file handles.
- Whether mapped views were flushed, unmapped, and closed before commit or rollback.
- Threads that continue reading or writing through a view after transaction completion.
- Whether the code should reopen and remap the committed file after the transaction ends.
Useful distinction
This differs from a normal mapping failure at creation time. The section existed, but its relationship to valid file data was broken by transaction completion.
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.