| Previous | Next |
| STATUS_CANNOT_ACCEPT_TRANSACTED_WORK | STATUS_TRANSACTION_NOT_FOUND |
STATUS_CANNOT_ABORT_TRANSACTIONS
The resource manager could not abort enough outstanding transactions
STATUS_CANNOT_ABORT_TRANSACTIONS is a serious TxF resource-manager condition. It indicates that too many outstanding transactions could not be aborted and the resource manager has been shut down.
Look for a pattern of long-running, stuck, or in-doubt transactions rather than a single failing file operation. Once the resource manager shuts down, subsequent transacted operations on the same volume may fail until recovery or restart completes.
What to check
- Counts of active, pending, or in-doubt transactions before shutdown.
- Applications that start transactions and fail to commit, roll back, or close handles.
- CLFS and TxF recovery events for the affected volume.
- Whether resource pressure or a crash interrupted normal abort processing.
Useful distinction
This is different from one rollback failing. It names a resource-manager-wide inability to abort outstanding transactions, with shutdown as the consequence.
References
- Microsoft: Kernel Transaction Manager
- Microsoft: KTM resource managers
- Microsoft: KTM objects
- Microsoft: Transactional NTFS overview
Looking for a different code? Search another status or error code.