| Previous | Next |
| STATUS_LOG_CORRUPTION_DETECTED | STATUS_ENLISTMENT_NOT_SUPERIOR |
STATUS_RM_DISCONNECTED
The transaction may be committed, rolled back, or still unresolved elsewhere
KTM uses enlistments and notifications to coordinate each resource manager. If an RM disconnects during the outcome sequence, the caller can lose immediate access to the result even though the transaction manager may continue durable processing.
Do not map this status directly to rollback. A disconnected participant must recover and reconcile its enlistments with the transaction manager log before the final state is known.
What to inspect
- Record the transaction ID, enlistment ID, resource-manager GUID, and last notification completed.
- Correlate service crash, process termination, network loss, and transaction-manager events.
- On restart, run the documented RM recovery path and retrieve stored recovery information.
- Delay compensating actions until the durable outcome has been confirmed.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: enlistment objects
- Microsoft: writing a resource manager
- Microsoft: Kernel Transaction Manager functions
Looking for a different code? Search another status or error code.