| Previous | Next |
| hrExistingLogFileHasBadSignature | hrColumnNull |
hrExistingLogFileIsNotContiguous
State represented by this code
For hrExistingLogFileIsNotContiguous, a correct handler first decides whether the value is success, warning, or failure, then examines the documented outputs. The decisive boundary is the log sequence already present in the target path contains a generation gap required by recovery.
The stored Value is 0x8800022F (positive JET status 559; 559). The HRESULT carries a warning, so the call may have useful output or a valid cursor state that must be inspected. Current ESE documentation uses JET_wrnExistingLogFileIsNotContiguous for the corresponding published JET condition.
The first useful distinction is that this concerns the existing target sequence, whereas hrGivenLogFileIsNotContiguous concerns the logs supplied from backup media. Start by enumerate generations in the target path and compare them with the checkpoint and the requested restore range. 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: enumerate generations in the target path and compare them with the checkpoint and the requested restore range.
- Provenance and hashes: record it together with this result and the timestamp of the first occurrence.
- Target and backup log directory listings: record it together with this result and the timestamp of the first occurrence.
- Generation numbers and signatures: record it together with this result and the timestamp of the first occurrence.
- Checkpoint and database signatures: 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 relationship between pre-existing target logs and the restore log lineage |
|---|---|
| Relevant API surface | hard recovery, restore target paths, log generation validation, and checkpoint processing |
| Code-specific boundary | the log sequence already present in the target path contains a generation gap required by recovery |
| Narrow corrective direction | supply the missing generation from the same sequence or restart with a clean target directory and a complete lineage |
Every log generation carries sequence identity in addition to its filename., warnings about existing target logs identify a collision that should be resolved before normal service resumes.
Actions that can make diagnosis worse
- do not overwrite the conflicting files before preserving evidence.
- do not mix logs from different backups because names appear contiguous.
- 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 concerns the existing target sequence, whereas hrGivenLogFileIsNotContiguous concerns the logs supplied from backup media. Related values below can appear in the same workflow but require a different response:
hrExistingLogFileHasBadSignature | a log already present in the target log path belongs to a different log sequence or has an unreadable signature |
|---|---|
hrRestoreLogTooLow | the configured upper or ending restore generation is below a log that the restore set requires |
hrInvalidLogSequence | the next log does not continue the expected sequence identity or timestamp chain |
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,
0x8800022F, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by enumerate generations in the target path and compare them with the checkpoint and the requested restore range.
- Apply only the narrow correction: supply the missing generation from the same sequence or restart with a clean target directory and a complete lineage.
- 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
A useful regression test for this HRESULT should force the condition “the log sequence already present in the target path contains a generation gap required by recovery”, call one documented API transition, and assert the exact HRESULT. The corrected the case should change only the decisive precondition and should verify cleanup as well as the primary output. For the result backup or restore path, also prove that the resulting set can be enumerated and that no file handle or context remains active after finalization.
Technical references
- JetExternalRestore phases and ranges — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- ESE files and checkpoint behavior
- ESE error-code table
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.