| Previous | Next |
| hrSeekNotEqual | hrNoWriteLock |
hrNoIdleActivity
How to read this HRESULT
hrNoIdleActivity means an idle-maintenance request found no eligible work to perform at that moment.
The stored value is 0x88000422 (positive JET status 1058; 1058). The HRESULT carries a warning, so the call may have useful output or a valid cursor state that must be inspected. Current ESE documentation uses JET_wrnNoIdleActivity for the corresponding published JET condition.
The first useful distinction is that this is a no-work result, not proof that maintenance is disabled or that a previous cleanup request failed. Start by recording the idle API, flags, elapsed time, version-store state, and whether maintenance was expected for a specific backlog.
Objects and state involved
| Diagnostic layer | version-store and idle-maintenance scheduling |
|---|---|
| Relevant API surface | JetIdle-style maintenance, transaction cleanup, version reclamation, and background tasks |
| Code-specific condition | an idle-maintenance request found no eligible work to perform at that moment |
| Narrow corrective direction | treat it as a scheduling signal and avoid immediate repeated calls that only consume CPU |
Long-running transactions can retain old record versions and delay reclamation. Idle work is opportunistic, so no-work and work-remaining results must both be handled without busy looping.
What to collect first
- Code-specific observation: record the idle API, flags, elapsed time, version-store state, and whether maintenance was expected for a specific backlog.
Controlled remediation
- Record it,
0x88000422, the API name, the current phase, and all live context or file owners. - Verify the condition by recording the idle API, flags, elapsed time, version-store state, and whether maintenance was expected for a specific backlog.
- Apply only the targeted fix: treat it as a scheduling signal and avoid immediate repeated calls that only consume CPU.
Acceptance criteria for a fix
A useful regression test should force the condition “an idle-maintenance request found no eligible work to perform at that moment”, call one documented API transition, and assert the exact HRESULT.
Related codes
It specifically means that this is a no-work result, not proof that maintenance is disabled or that a previous cleanup request failed. Related values below can appear in the same workflow but require a different response:
hrRemainingVersions | version-store cleanup still has work queued after an idle-maintenance pass |
|---|---|
hrGivenLogFileIsNotContiguous | the logs supplied from backup media contain a mandatory generation gap |
hrUnknownExpiryTokenFormat | bytes were supplied as an expiry token but the Directory Service cannot parse their format |
Actions that can make diagnosis worse
- Do not call idle maintenance in a tight loop without progress or backoff.
- Do not treat the warning as database corruption.
Technical references
- JET_ERR warning semantics — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to this HRESULT.
- ESE transaction model
- Open-source ESE implementation
Looking for a different code? Search another status or error code.