What does HRESULT 0xC800022A (hrRestoreLogTooHigh) mean?

 
Previous Next
hrRestoreLogTooLow hrGivenLogFileHasBadSignature

hrRestoreLogTooHigh

State represented by this code

hrRestoreLogTooHigh means the configured starting restore generation is above an available log that belongs to the required set.

The stored value is 0xC800022A (negative JET error -554; -554). Current ESE documentation uses JET_errStartingRestoreLogTooHigh for the corresponding published JET condition.

The first useful distinction is that this is the complementary boundary to hrRestoreLogTooLow, not a complaint that a log filename is numerically large. Start by recording genLow, genHigh, earliest supplied generation, database backup metadata, and hard-recovery parameters.

Data for a reproducible incident

  • Code-specific observation: record genLow, genHigh, earliest supplied generation, database backup metadata, and hard-recovery parameters.

Objects and state involved

Diagnostic layerthe explicit low/high transaction-log generation range used for hard recovery
Relevant API surfaceJetExternalRestore and JET_LOGINFO range parameters
Code-specific conditionthe configured starting restore generation is above an available log that belongs to the required set
Narrow corrective directionselect the correct starting generation and preserve the continuous sequence

Phase I requires every mandatory generation needed to bring the backup database to consistency. Later roll-forward logs are optional only after the mandatory range has been satisfied.

Actions that can make diagnosis worse

  • Do not skip a mandatory generation to make recovery continue.
  • Do not guess range endpoints from filenames alone.

Nearby ESE or AD backup states

It specifically means that this is the complementary boundary to hrRestoreLogTooLow, not a complaint that a log filename is numerically large. Related values below can appear in the same workflow but require a different response:

hrRestoreLogTooLowthe configured upper or ending restore generation is below a log that the restore set requires
hrInvalidParama legacy Directory Service backup/restore call rejected one or more arguments before advancing its context
hrPatchFileMismatchthe database patch file was not generated from the backup database being restored

Next actions

  1. Record it, 0xC800022A, the API name, the current phase, and all live context or file owners.
  2. Verify the condition by recording genLow, genHigh, earliest supplied generation, database backup metadata, and hard-recovery parameters.
  3. Apply only the targeted fix: select the correct starting generation and preserve the continuous sequence.

Technical references


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