| Previous | Next |
| STATEREPOSITORY_E_BUSY_TIMEOUT_EXCEEDED | STATEREPOSITORY_E_LOCKED_TIMEOUT_EXCEEDED |
STATEREPOSITORY_E_BUSY_RECOVERY_TIMEOUT_EXCEEDED
The scope of STATEREPOSITORY_E_BUSY_RECOVERY_TIMEOUT_EXCEEDED is Windows StateRepository: database recovery remained active beyond the allowed wait threshold. Preserve 0x8067000D beside the returning call before cleanup or retry creates a more generic secondary failure.
Read the condition first
A recovery timeout indicates that crash recovery is stalled, repeatedly restarted, or blocked by storage or another participant. It is stronger evidence than a single recovery-retry response.
Keep neighboring conditions separate
BUSY_RECOVERY_RETRY is expected transient waiting; this code means the recovery wait budget expired.
Do not delete recovery artifacts without a supported recovery plan and a preserved copy.
Incident record
- Recovery start and elapsed time.
- Journal/WAL and storage state.
- Process restarts.
- I/O errors or resource pressure.
Reproduce without destroying evidence
The investigation should change one variable at a time and keep the original failing sample.
- First: Preserve files before intervention.
- Next: Determine whether one recovery process is making progress.
- Then: Check storage and free-space conditions.
- Finally: Avoid repeated service termination during recovery.
Three useful controls
- Isolated connection against a repository copy: a changed result separates retained object, connection, path, host, or device state from the original input. Hold constant: preserve schema, data generation, and transaction sequence.
- Reduced failing operation: If this result follows the reduced step, the rejecting transition is localized. Hold constant: retain recovery start and elapsed time and remove only unrelated work.
- Targeted corrective control: Use this as a diagnostic branch rather than a blanket workaround: preserve files before intervention. Hold constant: keep the original failing sample available for the final regression test.
Definition of done
Closure requires recovery completes once within the threshold and later opens require no repeated repair; then repeat the next lifecycle operation to detect stale state.
Technical references
The references below define the API family or storage/protocol behavior used to interpret this result.
Looking for a different code? Search another status or error code.