What does HRESULT 0xC800022C (hrGivenLogFileIsNotContiguous) mean?

 
Previous Next
hrGivenLogFileHasBadSignature hrMissingRestoreLogFiles

hrGivenLogFileIsNotContiguous

What this return value changes

hrGivenLogFileIsNotContiguous means the logs supplied from backup media contain a mandatory generation gap.

The stored value is 0xC800022C (negative JET error -556; -556). 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 enumerating media contents and copied files, then compare generation numbers and signatures with the database required range.

Objects and state involved

Diagnostic layerthe logs copied from backup media before they enter the target recovery path
Relevant API surfacebackup-media extraction, validation, hard-recovery Phase I, and restore-log copying
Code-specific conditionthe logs supplied from backup media contain a mandatory generation gap
Narrow corrective directionretrieve 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

  • Code-specific observation: enumerate media contents and copied files, then compare generation numbers and signatures with the database required range.

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:

hrMissingRestoreLogFileshard recovery cannot reach consistency because one or more mandatory restore logs are absent
hrGivenLogFileHasBadSignaturea log supplied from backup media has a signature that does not belong to the restore sequence
hrDeleteBackupFileFailbackup cleanup could not delete an artifact it was responsible for removing

A safe response sequence

  1. Record it, 0xC800022C, the API name, the current phase, and all live context or file owners.
  2. Verify the condition by enumerating media contents and copied files, then compare generation numbers and signatures with the database required range.
  3. Apply only the targeted fix: retrieve the missing media generation or choose a different complete backup chain.

Actions that can make diagnosis worse

  • Do not overwrite the media copy during diagnosis.
  • Do not substitute a same-numbered log from another set.

Technical references


Looking for a different code? Search another status or error code.