| Previous | Next |
| STATEREPOSITORY_E_BLOCKED | STATEREPOSITORY_E_BUSY_RECOVERY_RETRY |
STATEREPOSITORY_E_BUSY_RETRY
The scope of STATEREPOSITORY_E_BUSY_RETRY is Windows StateRepository: the database file is busy and the request is expected to be retried. Preserve 0x80670007 beside the returning call before cleanup or retry creates a more generic secondary failure.
Wrong turns
LOCKED_RETRY is generally table or shared-cache contention; BUSY_RETRY is database-file contention.
Do not retry indefinitely or delete journal files while connections are active.
Object and state
Database-wide contention can arise when another connection holds a lock needed for the next step. This retry-class HRESULT indicates a transient policy path, distinct from the corresponding timeout-exceeded result.
Capture before retry
- Database path and connection.
- Current transaction and lock holder.
- Retry count and delay.
- Statement that requested the lock.
Controlled comparisons
| Control | Interpretation | Hold constant |
|---|---|---|
| Same database copy, isolated connections | A change points to connection/statement/transaction ownership rather than stored content. | Use a copy and preserve schema plus repository generation. |
| Same operation, controlled environment | If the result follows one machine, account, volume, network, or device, environment matters. | Keep versions and identity explicit rather than comparing only the final message. |
Step-by-step investigation
The investigation should change one variable at a time and keep the original failing sample.
- First: Keep transactions short.
- Next: Finalize or reset statements promptly.
- Then: Use bounded backoff supplied by the caller contract.
- Finally: Correlate lock ownership before changing service state.
Closure criteria
Closure requires contention clears within the bounded policy and the operation commits exactly once; then repeat the next lifecycle operation to detect stale state.
Technical references
Looking for a different code? Search another status or error code.