| Previous | Next |
| hrConsistentTimeMismatch | hrRestoreLogTooLow |
hrPatchFileMismatch
The exact condition reported here
hrPatchFileMismatch means the database patch file was not generated from the backup database being restored.
The stored value is 0xC8000228 (negative JET error -552; -552). Current ESE documentation uses JET_errDatabasePatchFileMismatch for the corresponding published JET condition.
The first useful distinction is that a patch file is backup-specific and cannot be borrowed from another set with the same database name. Start by capturing patch and database signatures, backup-set ID, file hashes, page size, and restore-map entry.
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 patch file was not generated from the backup database being restored |
| Narrow corrective direction | use the patch file packaged with this exact backup or restart from a complete verified set |
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.
Adjacent conditions
This result specifically means that a patch file is backup-specific and cannot be borrowed from another set with the same database name. Related values below can appear in the same workflow but require a different response:
hrConsistentTimeMismatch | the database last-consistent timestamp does not match the recovery or backup lineage being applied |
|---|---|
hrDatabaseInconsistent | the database is not in a clean transaction-consistent state and requires recovery before normal use |
hrRecoveredWithErrors | repair or restore completed far enough to produce output but encountered errors that affect confidence in the result |
Diagnostic record
- Code-specific observation: capture patch and database signatures, backup-set ID, file hashes, page size, and restore-map entry.
- Backup identity and restore map: capture the value and timestamp from the first occurrence.
- Required log positions: capture the value and timestamp from the first occurrence.
- Database header and state: capture the value and timestamp from the first occurrence.
- Signatures, page size, and hashes: capture the value and timestamp from the first occurrence.
Actions that can make diagnosis worse
- Do not modify the only backup copy in place.
- Do not attach a dirty or mismatched database as if it were clean.
Corrective path
- Record it,
0xC8000228, the API name, the current phase, and all live context or file owners. - Verify the condition by capturing patch and database signatures, backup-set ID, file hashes, page size, and restore-map entry.
- Apply only the targeted fix: use the patch file packaged with this exact backup or restart from a complete verified set.
Acceptance criteria for a fix
A useful regression test should force the condition “the database patch file was not generated from the backup database being restored”, call one documented API transition, and assert the exact HRESULT.
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.