| Previous | Next |
| hrInvalidLogSequence | hrLogBufferTooSmall |
hrLoggingDisabled
Why this result matters
hrLoggingDisabled means the requested operation requires transaction logging but the instance currently has logging inactive.
The stored value is 0xC8000204 (negative JET error -516; -516). 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 recording recovery and circular-log parameters, initialization mode, instance state, and the API that first required a log record.
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 |
Forensic checklist
- Code-specific observation: record recovery and circular-log parameters, initialization mode, instance state, and the API that first required a log record.
- Instance state: capture the value and timestamp from the first occurrence.
- Operation requiring logging: capture the value and timestamp from the first occurrence.
- Initialization parameters: capture the value and timestamp from the first occurrence.
- Recovery and circular-log settings: capture the value and timestamp from the first occurrence.
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 condition | 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.
Validation after correction
- Record it,
0xC8000204, the API name, the current phase, and all live context or file owners. - Verify the condition by recording recovery and circular-log parameters, initialization mode, instance state, and the API that first required a log record.
- Apply only the targeted fix: initialize the instance with the supported logging mode or avoid operations that require logged updates.
Acceptance criteria for a fix
A useful regression test 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.
Technical references
- JetInit file behavior — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to this HRESULT.
- ESE files
- Backup and restore parameters
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.