| Previous | Next |
| hrKeyChanged | WEP_E_NOT_PROVISIONED_ON_ALL_VOLUMES |
hrFileOpenReadOnly
Operational meaning
For hrFileOpenReadOnly, a correct handler first decides whether the value is success, warning, or failure, then examines the documented outputs. The decisive boundary is the database file was opened in read-only mode and the resulting handle cannot support logged updates.
The stored Value is 0x88000715 (positive JET status 1813; 1813). The HRESULT carries a warning, so the call may have useful output or a valid cursor state that must be inspected. Current ESE documentation uses JET_wrnFileOpenReadOnly for the corresponding published JET condition.
The first useful distinction is that read-only access is an established mode, distinct from access denied while opening or a later disk-write failure. Start by capture attach/open flags, file attributes, volume permissions, instance recovery mode, and the first operation requiring a write. That separates a reproducible incident from a later generic cleanup or service error.
Before altering files or retrying
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 attach/open flags, file attributes, volume permissions, instance recovery mode, and the first operation requiring a write.
- File attributes and recovery state: record it together with this result and the timestamp of the first occurrence.
- Instance and session IDs: record it together with this result and the timestamp of the first occurrence.
- Canonical database path: record it together with this result and the timestamp of the first occurrence.
- Attach/open flags: 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.
Comparison points
It specifically means that read-only access is an established mode, distinct from access denied while opening or a later disk-write failure. Related values below can appear in the same workflow but require a different response:
hrDatabaseAttached | the database was already attached to the instance when another attach operation was requested |
|---|---|
hrInvalidParam | a legacy Directory Service backup/restore call rejected one or more arguments before advancing its context |
hrIncrementalBackupDisabled | the database lineage no longer permits the requested incremental backup and requires a new full baseline |
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.
Objects and state involved
| Diagnostic layer | database attachment/open mode and ownership by an ESE instance |
|---|---|
| Relevant API surface | attach, open, initialization, recovery, and instance lifecycle operations |
| Code-specific boundary | the database file was opened in read-only mode and the resulting handle cannot support logged updates |
| Narrow corrective direction | keep the workflow read-only or reopen through the owning application with a writable, recoverable log configuration |
Attachment belongs to an instance, while an open database ID belongs to a session., read-only and already-attached warnings can be valid operating modes but constrain later calls.
Recommended handling
- Record it,
0x88000715, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by capture attach/open flags, file attributes, volume permissions, instance recovery mode, and the first operation requiring a write.
- Apply only the narrow correction: keep the workflow read-only or reopen through the owning application with a writable, recoverable log configuration.
- 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 database file was opened in read-only mode and the resulting handle cannot support logged updates”, 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.
Actions that can make diagnosis worse
- do not attempt logged writes through a read-only path.
- do not detach a database merely to silence a warning without checking owners.
- 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 lifecycle — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- JetInit and recovery
- ESE warning table
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.