What does HRESULT 0x8067000A (STATEREPOSITORY_E_LOCKED_SHAREDCACHE_RETRY) mean?

STATEREPOSITORY_E_LOCKED_SHAREDCACHE_RETRY

Within Windows StateRepository, STATEREPOSITORY_E_LOCKED_SHAREDCACHE_RETRY reports that a shared-cache lock held by another connection blocked this request. Diagnosis of this result should follow the original owner and generation rather than treating the visible symptom as the cause.

Facts that change the diagnosis

• Shared-cache group and connections.
• Table and schema locks.
• Active prepared statements.
• Thread and transaction ownership.

Subsystem meaning

Connections participating in a shared cache coordinate schema and table locks inside one process or cache group. The key evidence is cache-group membership and connection state, not only the database filename.

Isolation workflow

1. First: Avoid sharing one cache group without a clear concurrency design.
2. Next: Finish statements before cross-connection writes.
3. Then: Test with private caches as a control.
4. Finally: Keep retries outside the lock-owning callback.

Avoid the tempting broad fix

LOCKED_RETRY may be table locking generally; LOCKED_SHAREDCACHE_RETRY identifies shared-cache coordination.

Do not assume process-local locks will appear as external file handles.

Expected branches

Regression proof

Verify it with the original scenario, one boundary case, and one deliberate failure; success means the cache configuration supports the tested concurrency or is replaced with isolated connections that pass the same workload.

Technical references

• Microsoft Win32 metadata: winerror.h
• SQLite: Result and extended result codes
• SQLite: Shared-cache locking model
• Microsoft: Windows service guidance for StateRepository