| Previous | Next |
| hrLogBufferTooSmall | hrNoBackup |
hrLogSequenceEnd
How to read this HRESULT
For hrLogSequenceEnd, a correct handler first decides whether the value is success, warning, or failure, then examines the documented outputs. The decisive boundary is the legacy log generation namespace reached its maximum value.
The stored Value is 0xC8000207 (negative JET error -519; -519). The HRESULT carries failure severity, so output state must be treated according to the individual API contract. 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 record current generation, base name, checkpoint, database clean state, and whether a verified full backup exists. That separates a reproducible incident from a later generic cleanup or service error.
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 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
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 current generation, base name, checkpoint, database clean state, and whether a verified full backup exists.
- Complete generation inventory: record it together with this result and the timestamp of the first occurrence.
- Log signatures and timestamps: record it together with this result and the timestamp of the first occurrence.
- 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.
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.
Controlled remediation
- Record it,
0xC8000207, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by record current generation, base name, checkpoint, database clean state, and whether a verified full backup exists.
- Apply only the narrow correction: follow the product-supported sequence reset procedure only after clean shutdown and verified backup.
- 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
Boundary with 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 |
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.
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.
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.