| Previous | Next |
| STATEREPOSITORY_E_LOCKED_SHAREDCACHE_TIMEOUT_EXCEEDED | STATEREPOSTORY_E_NESTED_TRANSACTION_NOT_SUPPORTED |
STATEREPOSITORY_E_SERVICE_STOP_IN_PROGRESS
Within Windows StateRepository, STATEREPOSITORY_E_SERVICE_STOP_IN_PROGRESS reports that the request arrived while the StateRepository service was stopping. Diagnosis of this result should follow the original owner and generation rather than treating the visible symptom as the cause.
Mechanism behind the code
Service stop is a lifecycle boundary: new work should be rejected while in-flight transactions and database resources drain. A caller that immediately restarts work can create a stop/start race.
High-value telemetry
- Service state and stop trigger.
- Caller request time.
- In-flight transaction count.
- Retry or restart owner.
Decision table
- 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 service state and stop trigger and remove only unrelated work.
- Targeted corrective control: Use this as a diagnostic branch rather than a blanket workaround: stop issuing new requests after stop notification. Hold constant: keep the original failing sample available for the final regression test.
Safe reduction procedure
Use a disposable control object, repository copy, file, or device association where the subsystem permits that safely.
- First: Stop issuing new requests after stop notification.
- Next: Let in-flight work resolve according to contract.
- Then: Wait for a new service generation before retrying.
- Finally: Tag connections and requests by generation.
Do not erase the distinction
During an investigation, STATEREPOSITORY_E_BLOCKED can occur during other internal phases; SERVICE_STOP_IN_PROGRESS is specifically teardown.
Do not force-start another service instance or reuse connections from the stopping generation.
Successful outcome
Verify it with the original scenario, one boundary case, and one deliberate failure; success means all old-generation work drains or fails deterministically and new work begins only after a confirmed start.
Technical references
Looking for a different code? Search another status or error code.