| Previous | Next |
| hrGivenLogFileHasBadSignature | hrMissingRestoreLogFiles |
hrGivenLogFileIsNotContiguous
What this return value changes
For hrGivenLogFileIsNotContiguous, treat the value as part of a state machine: it says what remained valid and what did not. The decisive boundary is the logs supplied from backup media contain a mandatory generation gap.
The stored Value is 0xC800022C (negative JET error -556; -556). The HRESULT carries failure severity, so output state must be treated according to the individual API contract. Current ESE documentation uses JET_errGivenLogFileIsNotContiguous for the corresponding published JET condition.
The first useful distinction is that a gap in supplied media is distinct from a conflict in the target instance log path. Start by enumerate media contents and copied files, then compare generation numbers and signatures with the database required range. That separates a reproducible incident from a later generic cleanup or service error.
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 boundary | the logs supplied from backup media contain a mandatory generation gap |
| Narrow corrective direction | retrieve the missing media generation or choose a different complete backup chain |
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
Preserve the first result before retries, cleanup, service restart, or file replacement changes the evidence. The diagnostic record should identify the exact API phase and the owner of every handle or artifact involved.
- Code-specific observation: enumerate media contents and copied files, then compare generation numbers and signatures with the database required range.
- Media and file hashes: record it together with this result and the timestamp of the first occurrence.
- Generation inventory: record it together with this result and the timestamp of the first occurrence.
- Header signatures: record it together with this result and the timestamp of the first occurrence.
- Copy errors and source set identity: record it together with this result and the timestamp of the first occurrence.
Use hashes, lengths, IDs, generation numbers, and redacted samples instead of copying directory contents or sensitive database values into routine logs. For this it investigation, a complete provenance chain is often more useful than a second automatic retry.
How to distinguish nearby results
It specifically means that a gap in supplied media is distinct from a conflict in the target instance log path. Related values below can appear in the same workflow but require a different response:
hrMissingRestoreLogFiles | hard recovery cannot reach consistency because one or more mandatory restore logs are absent |
|---|---|
hrGivenLogFileHasBadSignature | a log supplied from backup media has a signature that does not belong to the restore sequence |
hrDeleteBackupFileFail | backup cleanup could not delete an artifact it was responsible for removing |
Keep the original constant and hexadecimal value in telemetry. Replacing it with “backup failed” or “database warning” removes the state information needed to select the next legal API call.
A safe response sequence
- Record it,
0xC800022C, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by enumerate media contents and copied files, then compare generation numbers and signatures with the database required range.
- Apply only the narrow correction: retrieve the missing media generation or choose a different complete backup chain.
- After it, recreate any context invalidated by the failure; do not carry stale HBC, cursor, file, or restore-map state into the retry.
- repeat the smallest non-destructive test that reaches the same boundary, then verify both the return value and the resulting file, cursor, backup, or database state.
Actions that can make diagnosis worse
- do not overwrite the media copy during diagnosis.
- do not substitute a same-numbered log from another set.
- do not discard the first lower-level Win32, RPC, or JET result merely because a later cleanup call returned a more familiar error.
Acceptance criteria for a fix
Technical references
- JetExternalRestore phases — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- ESE restore error codes
- ESE files
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.