| Previous | Next |
| ERROR_CANT_RECOVER_WITH_HANDLE_OPEN | ERROR_ENLISTMENT_NOT_SUPERIOR |
ERROR_RM_DISCONNECTED
The participant responsible for the resource is no longer connected to the transaction
ERROR_RM_DISCONNECTED belongs to the Windows Kernel Transaction Manager transaction-processing model. Resource managers receive KTM notifications and report prepare, commit, or rollback completion through their enlistments. If the RM responsible for a resource disconnects, the caller can lose immediate access to the transaction outcome even though the coordinator or durable RM log may later recover it. This is different from a clean abort notification.
Identify whether the RM process crashed, intentionally shut down, lost its completion-port or notification loop, or disconnected from a superior coordinator. Record the last notification and completion call for every affected enlistment. If the RM is durable, follow recovery processing after it restarts and wait for recovered commit or in-doubt state rather than guessing the outcome from the client error. Application retries should be gated by resource-level idempotency because the original transaction may still have committed.
What to inspect
- Find the RM process or service lifecycle event that caused the disconnect.
- Record the last KTM notification and completion routine observed for the transaction.
- Use RM recovery to resolve outcome before replaying non-idempotent work.
References
- Microsoft: KTM transaction notifications
- Microsoft: KTM recovery processing and presumed abort
- Microsoft: creating and recovering a KTM resource manager
Looking for a different code? Search another status or error code.