| Previous | Next |
| hrMissingLogFile | hrBadLogSignature |
hrLogDiskFull
What this return value changes
For hrLogDiskFull, this code narrows the investigation to one engine boundary and should not be flattened into a generic exception. The decisive boundary is the volume hosting transaction logs cannot allocate the next required log write or generation.
The stored Value is 0xC8000211 (negative JET error -529; -529). The HRESULT carries failure severity, so output state must be treated according to the individual API contract. Current ESE documentation uses JET_errLogDiskFull for the corresponding published JET condition.
The first useful distinction is that free space on the database volume is irrelevant if logs are on a different volume. Start by capture free and reserved space, log growth rate, checkpoint lag, circular-log policy, outstanding backup, and volume quotas. That separates a reproducible incident from a later generic cleanup or service error.
Objects and state involved
| Diagnostic layer | durable write-ahead-log I/O and capacity of the log volume |
|---|---|
| Relevant API surface | transaction commit, log flush, generation creation, recovery undo, and backup truncation |
| Code-specific boundary | the volume hosting transaction logs cannot allocate the next required log write or generation |
| Narrow corrective direction | create safe capacity on the log volume and let the owning service recover; never delete required logs ad hoc |
ESE must log changes before corresponding database pages become durable., log storage is often separate from database storage and must be diagnosed independently.
Evidence worth preserving
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 free and reserved space, log growth rate, checkpoint lag, circular-log policy, outstanding backup, and volume quotas.
- Path, generation, offset, and byte count: record it together with this result and the timestamp of the first occurrence.
- Win32 status and latency: record it together with this result and the timestamp of the first occurrence.
- Free/reserved space and quota: record it together with this result and the timestamp of the first occurrence.
- Checkpoint and growth rate: 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.
How to distinguish nearby results
It specifically means that free space on the database volume is irrelevant if logs are on a different volume. Related values below can appear in the same workflow but require a different response:
hrLogWriteFail | the write-ahead log could not durably accept a required record |
|---|---|
hrNyi | the selected legacy Directory Service backup or restore entry point is present but that operation is not implemented |
hrConsistentTimeMismatch | the database last-consistent timestamp does not match the recovery or backup lineage being applied |
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.
A safe response sequence
- Record it,
0xC8000211, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by capture free and reserved space, log growth rate, checkpoint lag, circular-log policy, outstanding backup, and volume quotas.
- Apply only the narrow correction: create safe capacity on the log volume and let the owning service recover; never delete required logs ad hoc.
- 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 delete required log generations to free space.
- do not keep accepting writes after durable logging has failed.
- 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
Technical references
- ESE log files and reserves — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- Transaction-log parameters
- ESE error codes
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.