| Previous | Next |
| hrBFNotSynchronous | hrRemainingVersions |
hrBFPageNotFound
The exact condition reported here
hrBFPageNotFound means the requested page was not present in the buffer-manager context used by the operation.
The stored value is 0x880000C9 (positive JET status 201; 201). The HRESULT carries a warning, so the call may have useful output or a valid cursor state that must be inspected. The legacy symbolic name comes from the Windows Directory Service backup/restore message header.
The first useful distinction is that a cache miss must not be promoted automatically to hrReadVerifyFailure or hrDatabaseCorrupted. Start by recording the page number, database identity, cache operation, and whether the lookup was expected to find only resident pages.
Objects and state involved
| Diagnostic layer | ESE buffer-cache residency, page ownership, and latch lifetime |
|---|---|
| Relevant API surface | internal page acquisition and buffer-manager paths beneath normal Jet table operations |
| Code-specific condition | the requested page was not present in the buffer-manager context used by the operation |
| Narrow corrective direction | let the normal page-acquisition path read or reconstruct the page instead of relying on a stale buffer reference |
Buffer-cache observations can become stale without implying on-disk corruption. A supported caller should use Jet handles and cursor operations rather than retain internal page assumptions.
Adjacent conditions
This result specifically means that a cache miss must not be promoted automatically to hrReadVerifyFailure or hrDatabaseCorrupted. Related values below can appear in the same workflow but require a different response:
hrBFNotSynchronous | a buffer-manager observation became stale because the page was evicted before the synchronous check could complete |
|---|---|
hrBadLogVersion | the transaction log format is incompatible with the ESE version attempting to read it |
hrLogDiskFull | the volume hosting transaction logs cannot allocate the next required log write or generation |
Diagnostic record
- Code-specific observation: record the page number, database identity, cache operation, and whether the lookup was expected to find only resident pages.
- Thread and cursor that made the observation: capture the value and timestamp from the first occurrence.
- Underlying disk-read result if one occurred: capture the value and timestamp from the first occurrence.
- Database and page identity: capture the value and timestamp from the first occurrence.
- Cache residency and ownership state: capture the value and timestamp from the first occurrence.
Actions that can make diagnosis worse
- Do not delete database or log files based on a buffer warning.
- Do not spin while holding stale page or latch state.
Corrective path
- Record it,
0x880000C9, the API name, the current phase, and all live context or file owners. - Verify the condition by recording the page number, database identity, cache operation, and whether the lookup was expected to find only resident pages.
- Apply only the targeted fix: let the normal page-acquisition path read or reconstruct the page instead of relying on a stale buffer reference.
Acceptance criteria for a fix
A useful regression test should force the condition “the requested page was not present in the buffer-manager context used by the operation”, call one documented API transition, and assert the exact HRESULT.
Technical references
- ESE error-code table — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to this HRESULT.
- ESE architecture and transactions
- Open-source ESE implementation
Looking for a different code? Search another status or error code.