| Previous | Next |
| hrBackupInProgress | hrLogWriteFail |
hrMissingPreviousLogFile
State represented by this code
For hrMissingPreviousLogFile, a correct handler first decides whether the value is success, warning, or failure, then examines the documented outputs. The decisive boundary is the checkpoint requires an earlier log generation that is absent from the available sequence.
The stored Value is 0xC80001FD (negative JET error -509; -509). The HRESULT carries failure severity, so output state must be treated according to the individual API contract. Current ESE documentation uses JET_errMissingPreviousLogFile for the corresponding published JET condition.
The first useful distinction is that hrMissingLogFile normally identifies the current log; this result ties the gap to checkpoint-based recovery. Start by read the checkpoint generation, list every log generation and signature, and record any manual deletion or failed truncation. 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: read the checkpoint generation, list every log generation and signature, and record any manual deletion or failed truncation.
- Database required range: record it together with this result and the timestamp of the first occurrence.
- Checkpoint generation: record it together with this result and the timestamp of the first occurrence.
- Complete generation inventory: record it together with this result and the timestamp of the first occurrence.
- Log signatures and timestamps: record it together with it 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 | checkpoint position and the continuous transaction-log generation sequence |
|---|---|
| Relevant API surface | JetInit recovery, hard restore ranges, checkpoint processing, and log enumeration |
| Code-specific boundary | the checkpoint requires an earlier log generation that is absent from the available sequence |
| Narrow corrective direction | restore the exact missing generation from the same lineage or rebuild from a complete backup set |
The checkpoint identifies the oldest log work not yet fully represented in database pages., recovery requires every mandatory generation in order and from one signature lineage.
Actions that can make diagnosis worse
- do not join gaps with logs from a different server or backup lineage.
- do not create an empty replacement log.
- 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 hrMissingLogFile normally identifies the current log; it ties the gap to checkpoint-based recovery. Related values below can appear in the same workflow but require a different response:
hrLogSequenceEnd | the legacy log generation namespace reached its maximum value |
|---|---|
hrInvalidLogSequence | the next log does not continue the expected sequence identity or timestamp chain |
hrMissingLogFile | the active or current transaction log expected by the instance is absent |
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,
0xC80001FD, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by read the checkpoint generation, list every log generation and signature, and record any manual deletion or failed truncation.
- Apply only the narrow correction: restore the exact missing generation from the same lineage or rebuild from a complete backup set.
- 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 checkpoint requires an earlier log generation that is absent from the available sequence”, 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
- ESE checkpoint and log files — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- Transaction-log parameters
- JetExternalRestore phases
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.