| Previous | Next |
| hrRecordDeleted | hrOutOfFileHandles |
hrReadVerifyFailure
Why this is more specific than the message text
hrReadVerifyFailure means a database page failed physical verification while being read.
This is the legacy Directory Service backup/restore HRESULT form of JET_errReadVerifyFailure (0xC80003FA).
The key comparison is: hrDiskIO is an operating-system I/O failure; this code means bytes were read but failed integrity checks. The first useful observation is to preserve the file path, page/offset, expected and actual checksum data, storage events, and a copy of surrounding logs.
Related ESE conditions
hrPermissionDenied | the caller lacks permission for the requested ESE operation or protected resource |
|---|---|
hrTempFileOpenError | ESE could not create or open a temporary file needed for sorting, maintenance, or recovery work |
hrLogCorrupted | transaction log files required by the database fail structural or integrity validation |
The ESE objects in play
| Diagnostic layer | database, log, checkpoint, or temporary files and the Windows storage/security boundary |
|---|---|
| Typical API surface | database open/attach, log recovery, temporary sort/maintenance, and file rename paths |
| Code-specific condition | a database page failed physical verification while being read |
| First corrective direction | stop writes, secure backups and diagnostics, investigate storage, and use product-supported recovery rather than editing the file |
Database and log files should not be manually fabricated, renamed, or deleted as a first response. Integrity failures require evidence preservation before repair or replay changes the on-disk state.
Data for a reproducible case
- Code-specific observation: preserve the file path, page/offset, expected and actual checksum data, storage events, and a copy of surrounding logs.
- storage, filter-driver, antivirus, and system events from the same time window; associate it with this result rather than with a later generic exception.
- the exact file, offset, length, access mode, and underlying Win32 status.
- database, log, checkpoint, and temporary-file generations present at the first event.
Corrective workflow
- Freeze the failing request context and record
0xC80003FA, the Jet API name, and the current instance/session ownership. - Verify the code-specific precondition: preserve the file path, page/offset, expected and actual checksum data, storage events, and a copy of surrounding logs.
- Apply the targeted fix: stop writes, secure backups and diagnostics, investigate storage, and use product-supported recovery rather than editing the file.
- Before retrying the operation, reconcile file identity, integrity evidence, and the supported recovery state.
Actions that can hide or worsen the problem
- Do not delete, rename, replace, or fabricate ESE files before preserving the complete set.
- Do not run destructive repair while a storage or access fault is still active.
Technical references
Looking for a different code? Search another status or error code.