| Previous | Next |
| ERROR_STATE_LOAD_STORE_FAILED | ERROR_STATE_SET_VERSION_FAILED |
ERROR_STATE_GET_VERSION_FAILED
The state-store version could not be read
ERROR_STATE_GET_VERSION_FAILED means the repository was found, but its version metadata could not be obtained. Version information is needed before code can decide whether the stored layout is compatible or requires migration.
Likely causes
- Corrupted or incomplete metadata.
- An interrupted upgrade left the store between schema versions.
- The caller lacks access to the metadata record.
- The storage provider returned an I/O or consistency error.
What to inspect
Compare the application build, package version, and repository modification time. Look for an earlier migration or deployment failure. Avoid treating this as an ordinary missing setting: the unreadable version can make every value in the store unsafe to interpret.
Developer response
Fail closed with respect to schema interpretation. Log both the expected version and the underlying storage error, then use the product's supported repair or migration mechanism rather than guessing a layout.
Compatibility implications
Code should not deserialize records under an assumed schema when the version cannot be read. Even if individual fields look plausible, interpreting them with the wrong layout can produce silent corruption that is harder to repair than a clean startup failure.
Test coverage
Exercise upgrades from every supported previous version, cancellation during migration, power loss between data writes and the version update, and recovery from a read-only store. These tests verify that version metadata remains the authoritative gate for migration.
References
Looking for a different code? Search another status or error code.