ERROR_NO_SAVEPOINT_WITH_OPEN_FILES - 6842 (0x1ABA)
The savepoint operation failed because files are open on the transaction. This is not permitted.
Updated: Feb 21, 2026
Technical Meaning
The ERROR_NO_SAVEPOINT_WITH_OPEN_FILES error indicates that a savepoint operation could not be performed because files are currently open on the transaction. Savepoints are used to create a point of recovery within a transaction, allowing for partial rollbacks or commits without affecting the entire transaction.
Error Details
This error is specific to operations involving transactions and file systems in Windows environments. It occurs when an attempt is made to establish a savepoint while files associated with the current transaction are still open. This situation violates the rules governing transactional integrity, as it could lead to inconsistent states or data corruption.
Usage Context
This error typically arises in scenarios where transactions are being managed at the file system level, such as during database operations or when using transactional NTFS (TxF) features. It is important for developers and administrators to understand that this error does not allow for savepoints to be created under these conditions.
Developer Interpretation
Developers should interpret this error as a signal that the current operation cannot proceed due to an open file on the transaction. This may require closing any open files or transactions before attempting the savepoint operation again. Failure to do so could result in incomplete or inconsistent data states, leading to potential data integrity issues.
Related Errors
ERROR_TRANSACTION_INTEGRITY_VIOLATIONERROR_TRANSACTION_NOT_ACTIVEERROR_FILE_NOT_OPEN
FAQ
Q: What does the ERROR_NO_SAVEPOINT_WITH_OPEN_FILES error mean?
A: It indicates that a savepoint operation cannot be performed because files are open on the transaction.
Q: How can I resolve this issue?
A: Close any open files or transactions before attempting to create a savepoint again.
Summary
The ERROR_NO_SAVEPOINT_WITH_OPEN_FILES error is specific to operations involving file systems and transactions in Windows environments. It signals that the current operation cannot proceed due to an open file on the transaction, which could lead to data integrity issues if not addressed properly.