| Previous | Next |
| hrBadDbSignature | hrCheckpointCorrupt |
hrBadCheckpointSignature
How to read this HRESULT
hrBadCheckpointSignature means the checkpoint signature is incompatible with the log sequence selected for recovery.
The stored value is 0xC8000214 (negative JET error -532; -532). Current ESE documentation uses JET_errBadCheckpointSignature for the corresponding published JET condition.
The first useful distinction is that hrCheckpointCorrupt also covers a missing or unreadable checkpoint; this code isolates signature mismatch. Start by recording checkpoint header, log signature, base name, system path, generation, and provenance of copied files.
Objects and state involved
| Diagnostic layer | cryptographic-style ESE identity signatures linking database, logs, checkpoint, and backup set |
|---|---|
| Relevant API surface | soft recovery, hard recovery, database attachment, and backup verification |
| Code-specific condition | the checkpoint signature is incompatible with the log sequence selected for recovery |
| Narrow corrective direction | use a checkpoint from the same set or allow supported recovery to rebuild state from a complete log sequence |
ESE signatures identify lineage; they are not interchangeable with filenames or timestamps. A signature mismatch commonly indicates mixed files even when each file is individually readable.
What to collect first
- Code-specific observation: record checkpoint header, log signature, base name, system path, generation, and provenance of copied files.
Controlled remediation
- Record it,
0xC8000214, the API name, the current phase, and all live context or file owners. - Verify the condition by recording checkpoint header, log signature, base name, system path, generation, and provenance of copied files.
- Apply only the targeted fix: use a checkpoint from the same set or allow supported recovery to rebuild state from a complete log sequence.
Related codes
It specifically means that hrCheckpointCorrupt also covers a missing or unreadable checkpoint; this code isolates signature mismatch. Related values below can appear in the same workflow but require a different response:
hrBadLogSignature | a transaction log header signature does not match the expected log sequence |
|---|---|
hrBadDbSignature | the database signature does not match the backup or log set used for recovery |
hrExistingLogFileHasBadSignature | a log already present in the target log path belongs to a different log sequence or has an unreadable signature |
Actions that can make diagnosis worse
- Do not choose files solely by matching names and dates.
- Do not patch signatures or headers.
Technical references
- ESE error codes — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to this HRESULT.
- ESE files and signatures
- JetExternalRestore
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.