| Previous | Next |
| ERROR_NOT_SNAPSHOT_VOLUME | ERROR_DATA_LOST_REPAIR |
ERROR_NO_SAVEPOINT_WITH_OPEN_FILES
Open transactional file handles prevent the savepoint state from being established
ERROR_NO_SAVEPOINT_WITH_OPEN_FILES is a Transactional NTFS (TxF) file-system status. TxF exposes savepoint actions through FSCTL_TXFS_SAVEPOINT_INFORMATION. The system status explicitly rejects the savepoint operation when files are open on the transaction. Savepoints can later roll transactional state back, so active file handles would create difficult lifetime and version questions for objects changed after the savepoint.
Inventory all handles bound to the transaction before setting the savepoint. Include duplicate handles, directory handles, inherited handles, and mappings whose original file handle may have been closed. Structure the workflow so file operations reach a quiescent point, close the handles, set the savepoint, and then reopen the required paths. Retrying the savepoint without closing the handles cannot succeed merely because I/O is idle.
What to inspect
- Track every transacted file and directory handle by transaction ID.
- Close duplicate and inherited handles and unmap file sections before the savepoint.
- Create savepoints only at explicit quiescent boundaries in the file workflow.
References
- Microsoft: TXFS_SAVEPOINT_INFORMATION actions
- Microsoft: transacted file handles and transaction binding
- Microsoft: CreateFileTransacted and miniversion views
- Microsoft: TxF filesystem control codes
Looking for a different code? Search another status or error code.