| Previous | Next |
| hrDatabaseInconsistent | hrPatchFileMismatch |
hrConsistentTimeMismatch
Interpretation in the backup state machine
hrConsistentTimeMismatch means 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). 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 recording database header times and log positions, backup metadata, log signatures, and the exact set assembly history.
Start with these observations
- Code-specific observation: record database header times and log positions, backup metadata, log signatures, and the exact set assembly history.
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 condition | 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 condition by recording database header times and log positions, backup metadata, log signatures, and the exact set assembly history.
- Apply only the targeted fix: reconstruct the restore from one coherent backup and contiguous log lineage.
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 |
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.
Technical references
- JetExternalRestore behavior — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to this HRESULT.
- Database header information
- ESE error-code table
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.