| Previous | Next |
| ERROR_TXF_DIR_NOT_EMPTY | ERROR_TM_VOLATILE |
ERROR_INDOUBT_TRANSACTIONS_EXIST
Unresolved transaction outcomes are pinning resource-manager state
ERROR_INDOUBT_TRANSACTIONS_EXIST belongs to the Windows Kernel Transaction Manager transaction-processing model. An in-doubt transaction has reached a point where the resource manager cannot determine the final coordinated outcome yet. KTM recovery processing explicitly redelivers `TRANSACTION_NOTIFY_INDOUBT` and instructs the RM to wait for an outcome notification. Operations that would reset, reconfigure, or otherwise invalidate the RM state can therefore be blocked while these transaction branches remain unresolved.
Enumerate or log the in-doubt transaction and enlistment identifiers and trace their superior or coordinator connections. Verify recovery completed and that the RM notification loop is receiving outcome messages. A disconnected distributed coordinator may require transaction-coordinator recovery rather than local RM recreation. Never clear the RM log solely to remove the block: doing so can erase the information needed to apply the eventual commit or rollback consistently.
What to inspect
- Collect transaction and enlistment IDs for every in-doubt entry.
- Check coordinator connectivity and RM outcome-notification processing.
- Preserve recovery logs until each in-doubt transaction is reconciled.
References
- Microsoft: KTM recovery processing and presumed abort
- Microsoft: KTM transaction notifications
- MS-DTCO: superior and subordinate transaction-manager roles
Looking for a different code? Search another status or error code.