| Previous | Next |
| hrGivenLogFileIsNotContiguous | hrMissingFullBackup |
hrMissingRestoreLogFiles
What this return value changes
hrMissingRestoreLogFiles means hard recovery cannot reach consistency because one or more mandatory restore logs are absent.
The stored value is 0xC800022D (negative JET error -557; -557). Current ESE documentation uses JET_errMissingRestoreLogFiles for the corresponding published JET condition.
The first useful distinction is that optional roll-forward logs may be omitted, but Phase I logs needed to make the database consistent are mandatory. Start by deriving the required range from database and backup metadata, list all supplied generations, and identify the first gap.
Objects and state involved
| Diagnostic layer | the logs copied from backup media before they enter the target recovery path |
|---|---|
| Relevant API surface | backup-media extraction, validation, hard-recovery Phase I, and restore-log copying |
| Code-specific condition | hard recovery cannot reach consistency because one or more mandatory restore logs are absent |
| Narrow corrective direction | assemble the complete mandatory sequence from one lineage and restart from a freshly restored database copy |
Supplied logs should be verified before they are mixed with any target-instance logs. Generation continuity and sequence signature are both required.
Evidence worth preserving
- Code-specific observation: derive the required range from database and backup metadata, list all supplied generations, and identify the first gap.
How to distinguish nearby results
It specifically means that optional roll-forward logs may be omitted, but Phase I logs needed to make the database consistent are mandatory. Related values below can appear in the same workflow but require a different response:
hrGivenLogFileIsNotContiguous | the logs supplied from backup media contain a mandatory generation gap |
|---|---|
hrGivenLogFileHasBadSignature | a log supplied from backup media has a signature that does not belong to the restore sequence |
hrRestoreLogTooHigh | the configured starting restore generation is above an available log that belongs to the required set |
A safe response sequence
- Record it,
0xC800022D, the API name, the current phase, and all live context or file owners. - Verify the condition by deriving the required range from database and backup metadata, list all supplied generations, and identify the first gap.
- Apply only the targeted fix: assemble the complete mandatory sequence from one lineage and restart from a freshly restored database copy.
Actions that can make diagnosis worse
- Do not overwrite the media copy during diagnosis.
- Do not substitute a same-numbered log from another set.
Acceptance criteria for a fix
A useful regression test should force the condition “hard recovery cannot reach consistency because one or more mandatory restore logs are absent”, call one documented API transition, and assert the exact HRESULT.
Technical references
- JetExternalRestore phases — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to this HRESULT.
- ESE restore error codes
- ESE files
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.