| Previous | Next |
| UTC_E_FILTER_ILLEGAL_EVAL | hrBFPageNotFound |
hrBFNotSynchronous
Why this result matters
hrBFNotSynchronous means a buffer-manager observation became stale because the page was evicted before the synchronous check could complete.
The stored value is 0x880000C8 (positive JET status 200; 200). 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 this warning concerns residency and timing; it is not evidence that the database page is absent from disk or corrupt. Start by capturing the page identity, latch or ownership state, and the operation that expected the page to remain resident.
Do not confuse it with
This result specifically means that this warning concerns residency and timing; it is not evidence that the database page is absent from disk or corrupt. Related values below can appear in the same workflow but require a different response:
hrBFPageNotFound | the requested page was not present in the buffer-manager context used by the operation |
|---|---|
hrNoBackup | a backup-only API was called when no external backup session is active |
hrTooManyIO | the engine reached its outstanding-I/O throttle and refused to queue more storage work |
Forensic checklist
- Code-specific observation: capture the page identity, latch or ownership state, and the operation that expected the page to remain resident.
- 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.
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 | a buffer-manager observation became stale because the page was evicted before the synchronous check could complete |
| Narrow corrective direction | reacquire the page through the supported engine path and make the caller tolerate eviction between observations |
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.
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.
Validation after correction
- Record it,
0x880000C8, the API name, the current phase, and all live context or file owners. - Verify the condition by capturing the page identity, latch or ownership state, and the operation that expected the page to remain resident.
- Apply only the targeted fix: reacquire the page through the supported engine path and make the caller tolerate eviction between observations.
Acceptance criteria for a fix
A useful regression test should force the condition “a buffer-manager observation became stale because the page was evicted before the synchronous check could complete”, 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.