| Previous | Next |
| STATUS_HEURISTIC_DAMAGE_POSSIBLE | STATUS_RM_ALREADY_STARTED |
STATUS_RECOVERY_NOT_NEEDED
Recovery was requested for a resource manager that is already consistent
KTM recovery replays durable transaction information after interruption and reconnects resource-manager enlistments with the transaction manager. This status is a benign lifecycle result: the resource manager has no unresolved recovery work at the point where recovery was requested.
It often indicates duplicate initialization, a repeated recovery call after a successful pass, or two components racing to bring the same resource manager online. Do not treat it as evidence of log corruption or lost transactions unless separate diagnostics show unresolved enlistments.
What to inspect
- Record which component initiated recovery and whether another startup path already completed it.
- Confirm the resource manager is accepting notifications and new enlistments after the result.
- Check for duplicated service initialization or retry logic that calls recovery unconditionally.
- Investigate transaction outcomes only when the resource manager reports unresolved work independently.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: writing a resource manager
- Microsoft: using log streams with KTM
- Microsoft: Kernel Transaction Manager functions
Looking for a different code? Search another status or error code.