| Previous | Next |
| STATUS_TRANSACTIONMANAGER_NOT_FOUND | STATUS_TRANSACTIONMANAGER_RECOVERY_NAME_COLLISION |
STATUS_TRANSACTIONMANAGER_NOT_ONLINE
STATUS_TRANSACTIONMANAGER_NOT_ONLINE means that the transaction manager associated with the request is not online. A durable KTM transaction manager recovers its state from its log before transaction or resource-manager namespace objects can be opened; an error writing the log can also take the manager offline.
This is therefore not solved by merely reopening a transaction handle. The relevant evidence is the recovery sequence, the TM log, and the reason recovery stopped. A healthy lookup with an offline state is different from STATUS_TRANSACTIONMANAGER_NOT_FOUND.
The transaction manager exists but is not ready for work
- Check the transaction-manager recovery result and the event log for log I/O, access, or metadata errors.
- Verify that recovery completed before resource managers begin opening transactions or enlistments.
- Do not delete or replace the log before preserving it and determining whether it contains recoverable transactional state.
References
- Microsoft: KTM transaction managers and recovery
- Microsoft: creating a KTM resource manager
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.
