| Previous | Next |
| hrDatabaseInconsistent | hrPatchFileMismatch |
hrConsistentTimeMismatch
Interpretation in the backup state machine
For hrConsistentTimeMismatch, the useful interpretation begins with the object and phase that returned the value. The decisive boundary is the database last-consistent timestamp does not match the recovery or backup lineage being applied.
The stored Value is 0xC8000227 (negative JET error -551; -551). The HRESULT carries failure severity, so output state must be treated according to the individual API contract. Current ESE documentation uses JET_errConsistentTimeMismatch for the corresponding published JET condition.
The first useful distinction is that matching filenames and generation numbers do not override a consistency-time mismatch. Start by record database header times and log positions, backup metadata, log signatures, and the exact set assembly history. That separates a reproducible incident from a later generic cleanup or service error.
Start with these observations
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 database header times and log positions, backup metadata, log signatures, and the exact set assembly history.
- Signatures, page size, and hashes: record it together with this result and the timestamp of the first occurrence.
- Backup identity and restore map: record it together with this result and the timestamp of the first occurrence.
- Required log positions: record it together with this result and the timestamp of the first occurrence.
- Database header and state: record it together with this result and the timestamp of the first occurrence.
Objects and state involved
| Diagnostic layer | database, patch, log, and backup metadata that establish one recoverable lineage |
|---|---|
| Relevant API surface | hard recovery, database-header inspection, patch application, and post-restore validation |
| Code-specific boundary | the database last-consistent timestamp does not match the recovery or backup lineage being applied |
| Narrow corrective direction | reconstruct the restore from one coherent backup and contiguous log lineage |
A hard-recovery failure leaves the restored database invalid; retry begins from a fresh restored copy., database state, signature, page size, consistent time, and required logs must agree.
Recovery or retry plan
- Record it,
0xC8000227, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by record database header times and log positions, backup metadata, log signatures, and the exact set assembly history.
- Apply only the narrow correction: reconstruct the restore from one coherent backup and contiguous log lineage.
- 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.
Not the same as
It specifically means that matching filenames and generation numbers do not override a consistency-time mismatch. Related values below can appear in the same workflow but require a different response:
hrPatchFileMismatch | the database patch file was not generated from the backup database being restored |
|---|---|
hrRecoveredWithErrors | repair or restore completed far enough to produce output but encountered errors that affect confidence in the result |
hrDatabaseInconsistent | the database is not in a clean transaction-consistent state and requires recovery before normal use |
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 attach a dirty or mismatched database as if it were clean.
- do not modify the only backup copy in place.
- 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
- JetExternalRestore behavior — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- Database header information
- ESE error-code table
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.