| Previous | Next |
| hrBadCheckpointSignature | hrDatabaseInconsistent |
hrCheckpointCorrupt
State represented by this code
hrCheckpointCorrupt means the checkpoint is missing, unreadable, or structurally invalid for recovery.
The stored value is 0xC8000215 (negative JET error -533; -533). Current ESE documentation uses JET_errCheckpointCorrupt for the corresponding published JET condition.
The first useful distinction is that the checkpoint is an optimization pointer; deleting it changes recovery scope and must not be the first unrecorded action. Start by preserving the checkpoint file, header, size, hash, system path, expected generation, and surrounding storage events.
Data for a reproducible incident
- Code-specific observation: preserve the checkpoint file, header, size, hash, system path, expected generation, and surrounding storage events.
Objects and state involved
| Diagnostic layer | the checkpoint file that bounds the log range needed for recovery |
|---|---|
| Relevant API surface | JetInit, system-path configuration, soft recovery, and hard recovery |
| Code-specific condition | the checkpoint is missing, unreadable, or structurally invalid for recovery |
| Narrow corrective direction | secure the evidence and follow product-supported recovery using the complete required logs |
The checkpoint tracks the oldest log position not fully represented in database pages. Recovery can require more log replay when checkpoint information is unavailable.
Actions that can make diagnosis worse
- Do not infer that missing checkpoint means the database is clean.
- Do not delete the checkpoint before recording it and the log set.
Nearby ESE or AD backup states
It specifically means that the checkpoint is an optimization pointer; deleting it changes recovery scope and must not be the first unrecorded action. Related values below can appear in the same workflow but require a different response:
hrError | the Directory Service backup layer returned an internal failure without a more specific facility code |
|---|---|
hrInvalidRecips | the recipient information supplied to the legacy backup operation failed validation |
hrBFPageNotFound | the requested page was not present in the buffer-manager context used by the operation |
Next actions
- Record it,
0xC8000215, the API name, the current phase, and all live context or file owners. - Verify the condition by preserving the checkpoint file, header, size, hash, system path, expected generation, and surrounding storage events.
- Apply only the targeted fix: secure the evidence and follow product-supported recovery using the complete required logs.
Acceptance criteria for a fix
A useful regression test should force the condition “the checkpoint is missing, unreadable, or structurally invalid for recovery”, call one documented API transition, and assert the exact HRESULT.
Technical references
- ESE checkpoint files — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to this HRESULT.
- Transaction-log parameters
- JetInit recovery
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.