| Previous | Next |
| hrLoggingDisabled | hrLogSequenceEnd |
hrLogBufferTooSmall
How to read this HRESULT
For hrLogBufferTooSmall, the hexadecimal HRESULT is most useful when kept beside the API call and the affected artifact. The decisive boundary is the available recovery log buffer cannot hold the log record or sector data required for replay.
The stored Value is 0xC8000205 (negative JET error -517; -517). The HRESULT carries failure severity, so output state must be treated according to the individual API contract. Current ESE documentation uses JET_errLogBufferTooSmall for the corresponding published JET condition.
The first useful distinction is that increasing an application output buffer will not fix an engine recovery-buffer incompatibility. Start by capture engine version, log format, sector and file size, configured log buffers, and the exact recovery phase. That separates a reproducible incident from a later generic cleanup or service error.
Objects and state involved
| Diagnostic layer | transaction-log format, checksum, version, and sequence identity |
|---|---|
| Relevant API surface | JetInit soft recovery, hard recovery, log backup, and log replay |
| Code-specific boundary | the available recovery log buffer cannot hold the log record or sector data required for replay |
| Narrow corrective direction | use a compatible engine/configuration and preserve the source logs before changing recovery parameters |
ESE uses write-ahead logs to reconstruct a transaction-consistent database after an unclean shutdown., a log filename is not enough; header signature, generation, version, and contents must agree.
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: capture engine version, log format, sector and file size, configured log buffers, and the exact recovery phase.
- Hash and failing offset: record it together with this result and the timestamp of the first occurrence.
- Engine version: record it together with this result and the timestamp of the first occurrence.
- Database and checkpoint signatures: record it together with this result and the timestamp of the first occurrence.
- Log generation and header: 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,
0xC8000205, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by capture engine version, log format, sector and file size, configured log buffers, and the exact recovery phase.
- Apply only the narrow correction: use a compatible engine/configuration and preserve the source logs before changing recovery parameters.
- 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 available recovery log buffer cannot hold the log record or sector data required for replay”, 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.
Boundary with related codes
It specifically means that increasing an application output buffer will not fix an engine recovery-buffer incompatibility. Related values below can appear in the same workflow but require a different response:
hrLogFileCorrupt | ESE detected structural or checksum corruption while reading a transaction log |
|---|---|
hrBadLogVersion | the transaction log format is incompatible with the ESE version attempting to read it |
hrCircularLogging | the Directory Service component is using circular logs, so the historical range needed for an incremental backup is not guaranteed to remain |
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 run destructive repair before preserving the original set.
- do not edit or rename logs to force acceptance.
- 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 files and recovery — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- JetInit recovery behavior
- ESE error-code table
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.