| Previous | Next |
| hrLogWriteFail | hrInvalidLogSequence |
hrBadLogVersion
How to read this HRESULT
hrBadLogVersion means the transaction log format is incompatible with the ESE version attempting to read it.
The stored value is 0xC8000202 (negative JET error -514; -514). Current ESE documentation uses JET_errBadLogVersion for the corresponding published JET condition.
The first useful distinction is that a version mismatch is not repaired by renaming the file and differs from a broken checksum. Start by recording engine build, log header version, database provenance, backup creation system, and any mixed binaries or copied files.
Objects and state involved
| Diagnostic layer | transaction-log format, checksum, version, and sequence identity |
|---|---|
| Relevant API surface | JetInit soft recovery, hard recovery, log backup, and log replay |
| Code-specific condition | the transaction log format is incompatible with the ESE version attempting to read it |
| Narrow corrective direction | use a compatible engine and restore the complete set produced by one supported version lineage |
ESE uses write-ahead logs to reconstruct a transaction-consistent database after an unclean shutdown. A log filename is not enough; header signature, generation, version, and contents must agree.
What to collect first
- Code-specific observation: record engine build, log header version, database provenance, backup creation system, and any mixed binaries or copied files.
Controlled remediation
- Record it,
0xC8000202, the API name, the current phase, and all live context or file owners. - Verify the condition by recording engine build, log header version, database provenance, backup creation system, and any mixed binaries or copied files.
- Apply only the targeted fix: use a compatible engine and restore the complete set produced by one supported version lineage.
Related codes
It specifically means that a version mismatch is not repaired by renaming the file and differs from a broken checksum. Related values below can appear in the same workflow but require a different response:
hrLogFileCorrupt | ESE detected structural or checksum corruption while reading a transaction log |
|---|---|
hrLogBufferTooSmall | the available recovery log buffer cannot hold the log record or sector data required for replay |
hrMissingRestoreLogFiles | hard recovery cannot reach consistency because one or more mandatory restore logs are absent |
Actions that can make diagnosis worse
- Do not run destructive repair before preserving the original set.
- Do not edit or rename logs to force acceptance.
Technical references
- ESE files and recovery — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to this HRESULT.
- JetInit recovery behavior
- ESE error-code table
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.