| Previous | Next |
| ERROR_OPERATION_NOT_SUPPORTED_IN_TRANSACTION | ERROR_TRANSACTION_NOT_ENLISTED |
ERROR_EXPIRED_HANDLE
The TxF resource-manager generation changed and the old file handle has expired
ERROR_EXPIRED_HANDLE is a Transactional NTFS (TxF) file-system status. The status definition says the handle may have been opened in a transactional resource manager that was subsequently forced to restart. A handle created under the earlier RM state cannot simply be attached to the restarted transactional context. This differs from an invalid numeric handle: the handle has lost the transaction association required for TxF I/O.
Correlate the first expired-handle error with TxF resource-manager restart, recovery, storage, and log events. Close the handle and open the file again using the current transaction and RM state, exactly as the system message directs. Also check application handle caches and long-lived worker objects: they can retain pre-restart transacted handles after the recovery path is complete. Repeated I/O through the expired handle will not rebind it automatically.
What to inspect
- Find the RM restart or recovery event that invalidated the handle generation.
- Close and reopen the file under the current transactional context.
- Purge cached transacted handles whenever the resource manager restarts.
References
- MS-ERREF: TxF and KTM status definitions
- Microsoft: querying TxF resource-manager state
- Microsoft: transacted file handles and transaction binding
Looking for a different code? Search another status or error code.