| Previous | Next |
| hrLogBufferTooSmall | hrNoBackup |
hrLogSequenceEnd
How to read this HRESULT
hrLogSequenceEnd means the legacy log generation namespace reached its maximum value.
The stored value is 0xC8000207 (negative JET error -519; -519). Current ESE documentation uses JET_errLogSequenceEnd for the corresponding published JET condition.
The first useful distinction is that disk space can remain available even though no further generation can be named. Start by recording current generation, base name, checkpoint, database clean state, and whether a verified full backup exists.
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 condition | the legacy log generation namespace reached its maximum value |
| Narrow corrective direction | follow the product-supported sequence reset procedure only after clean shutdown and verified backup |
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.
What to collect first
- Code-specific observation: record current generation, base name, checkpoint, database clean state, and whether a verified full backup exists.
Controlled remediation
- Record it,
0xC8000207, the API name, the current phase, and all live context or file owners. - Verify the condition by recording current generation, base name, checkpoint, database clean state, and whether a verified full backup exists.
- Apply only the targeted fix: follow the product-supported sequence reset procedure only after clean shutdown and verified backup.
Related codes
It specifically means that disk space can remain available even though no further generation can be named. 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 |
|---|---|
hrInvalidLogSequence | the next log does not continue the expected sequence identity or timestamp chain |
hrMissingPreviousLogFile | the checkpoint requires an earlier log generation that is absent from the available sequence |
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.
Technical references
- ESE checkpoint and log files — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to this HRESULT.
- Transaction-log parameters
- JetExternalRestore phases
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.