| Previous | Next |
| hrBadLogVersion | hrLoggingDisabled |
hrInvalidLogSequence
Where the workflow stopped
For hrInvalidLogSequence, the useful interpretation begins with the object and phase that returned the value. The decisive boundary is the next log does not continue the expected sequence identity or timestamp chain.
The stored Value is 0xC8000203 (negative JET error -515; -515). The HRESULT carries failure severity, so output state must be treated according to the individual API contract. Current ESE documentation uses JET_errInvalidLogSequence for the corresponding published JET condition.
The first useful distinction is that contiguous filenames alone are insufficient when the internal sequence identity changes. Start by capture adjacent generation numbers, timestamps, signatures, base names, and the directories from which each file came. That separates a reproducible incident from a later generic cleanup or service error.
Similar-looking outcomes
This result specifically means that contiguous filenames alone are insufficient when the internal sequence identity changes. Related values below can appear in the same workflow but require a different response:
hrMissingLogFile | the active or current transaction log expected by the instance is absent |
|---|---|
hrLogSequenceEnd | the legacy log generation namespace reached its maximum value |
hrMissingPreviousLogFile | the checkpoint requires an earlier log generation that is absent from the available sequence |
Keep the original constant and hexadecimal value in telemetry. Replacing this result with “backup failed” or “database warning” removes the state information needed to select the next legal API call.
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 next log does not continue the expected sequence identity or timestamp chain |
| Narrow corrective direction | remove the foreign branch and supply a continuous sequence from the same database/log lineage |
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.
Minimum useful trace
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: capture adjacent generation numbers, timestamps, signatures, base names, and the directories from which each file came.
- 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.
- Database required range: 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.
Steps to resolve it
- Record it,
0xC8000203, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by capture adjacent generation numbers, timestamps, signatures, base names, and the directories from which each file came.
- Apply only the narrow correction: remove the foreign branch and supply a continuous sequence from the same database/log 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.
Actions that can make diagnosis worse
- do not create an empty replacement log.
- do not join gaps with logs from a different server or backup lineage.
- do not discard the first lower-level Win32, RPC, or JET result merely because a later cleanup call returned a more familiar error.
Acceptance criteria for a fix
A useful regression test for this HRESULT should force the condition “the next log does not continue the expected sequence identity or timestamp chain”, 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.