| Previous | Next |
| hrRestoreLogTooLow | hrGivenLogFileHasBadSignature |
hrRestoreLogTooHigh
State represented by this code
For hrRestoreLogTooHigh, the useful interpretation begins with the object and phase that returned the value. The decisive boundary is 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). The HRESULT carries failure severity, so output state must be treated according to the individual API contract. 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 record genLow, genHigh, earliest supplied generation, database backup metadata, and hard-recovery parameters. That separates a reproducible incident from a later generic cleanup or service error.
Data for a reproducible incident
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: record genLow, genHigh, earliest supplied generation, database backup metadata, and hard-recovery parameters.
- Signatures and contiguous ordering: record it together with this result and the timestamp of the first occurrence.
- GenLow and genHigh: record it together with this result and the timestamp of the first occurrence.
- Earliest and latest supplied generations: record it together with this result and the timestamp of the first occurrence.
- Database-required positions: 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.
Objects and state involved
| Diagnostic layer | the explicit low/high transaction-log generation range used for hard recovery |
|---|---|
| Relevant API surface | JetExternalRestore and JET_LOGINFO range parameters |
| Code-specific boundary | the configured starting restore generation is above an available log that belongs to the required set |
| Narrow corrective direction | select 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.
- do not discard the first lower-level Win32, RPC, or JET result merely because a later cleanup call returned a more familiar error.
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:
hrRestoreLogTooLow | the configured upper or ending restore generation is below a log that the restore set requires |
|---|---|
hrInvalidParam | a legacy Directory Service backup/restore call rejected one or more arguments before advancing its context |
hrPatchFileMismatch | the database patch file was not generated from the backup database being restored |
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.
Next actions
- Record it,
0xC800022A, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by record genLow, genHigh, earliest supplied generation, database backup metadata, and hard-recovery parameters.
- Apply only the narrow correction: select the correct starting generation and preserve the continuous sequence.
- 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.
Acceptance criteria for a fix
Technical references
- JetExternalRestore ranges and phases — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- JET_LOGINFO structure
- ESE restore errors
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.