| Previous | Next |
| hrInvalidLogSequence | hrLogBufferTooSmall |
hrLoggingDisabled
Why this result matters
For hrLoggingDisabled, treat the value as part of a state machine: it says what remained valid and what did not. The decisive boundary is the requested operation requires transaction logging but the instance currently has logging inactive.
The stored Value is 0xC8000204 (negative JET error -516; -516). The HRESULT carries failure severity, so output state must be treated according to the individual API contract. Current ESE documentation uses JET_errLoggingDisabled for the corresponding published JET condition.
The first useful distinction is that this is configuration/state, whereas hrLogWriteFail means an active log failed during I/O. Start by record recovery and circular-log parameters, initialization mode, instance state, and the API that first required a log record. That separates a reproducible incident from a later generic cleanup or service error.
Do not confuse it with
This result specifically means that this is configuration/state, whereas hrLogWriteFail means an active log failed during I/O. 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 |
|---|---|
hrColumnSetNull | a column update resulted in a NULL value as an explicit outcome |
hrTooManyIO | the engine reached its outstanding-I/O throttle and refused to queue more storage work |
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.
Forensic checklist
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 recovery and circular-log parameters, initialization mode, instance state, and the API that first required a log record.
- Instance state: record it together with this result and the timestamp of the first occurrence.
- Operation requiring logging: record it together with it and the timestamp of the first occurrence.
- Initialization parameters: record it together with it and the timestamp of the first occurrence.
- Recovery and circular-log settings: 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.
Objects and state involved
| Diagnostic layer | whether an ESE instance is initialized with an active logging and recovery configuration |
|---|---|
| Relevant API surface | JetInit, system parameters, transaction updates, and recovery modes |
| Code-specific boundary | the requested operation requires transaction logging but the instance currently has logging inactive |
| Narrow corrective direction | initialize the instance with the supported logging mode or avoid operations that require logged updates |
Disabling recovery/logging changes which files exist and which operations are safe., an application must not assume a writable database implies an active durable log.
Actions that can make diagnosis worse
- do not enable logging midway by manipulating files.
- do not perform updates whose durability contract cannot be met.
- do not discard the first lower-level Win32, RPC, or JET result merely because a later cleanup call returned a more familiar error.
Validation after correction
- Record it,
0xC8000204, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by record recovery and circular-log parameters, initialization mode, instance state, and the API that first required a log record.
- Apply only the narrow correction: initialize the instance with the supported logging mode or avoid operations that require logged updates.
- 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 requested operation requires transaction logging but the instance currently has logging inactive”, 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
- JetInit file behavior — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- ESE files
- Backup and restore parameters
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.