| Previous | Next |
| hrSeekNotEqual | hrNoWriteLock |
hrNoIdleActivity
How to read this HRESULT
For hrNoIdleActivity, this result identifies a specific state transition rather than a generic “database failure.” The decisive boundary is 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 record the idle API, flags, elapsed time, version-store state, and whether maintenance was expected for a specific backlog. That separates a reproducible incident from a later generic cleanup or service error.
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 boundary | 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
Preserve the first result before retries, cleanup, service restart, or file replacement changes the evidence. The diagnostic record should identify the exact API phase and the owner of every handle or artifact involved.
- Code-specific observation: record the idle API, flags, elapsed time, version-store state, and whether maintenance was expected for a specific backlog.
- Version-store usage and trend: record it together with this result and the timestamp of the first occurrence.
- Maintenance flags and elapsed time: record it together with this result and the timestamp of the first occurrence.
- Progress between successive calls: record it together with this result and the timestamp of the first occurrence.
- Oldest transaction age: record it together with it and the timestamp of the first occurrence.
Use hashes, lengths, IDs, generation numbers, and redacted samples instead of copying directory contents or sensitive database values into routine logs. For this it investigation, a complete provenance chain is often more useful than a second automatic retry.
Controlled remediation
- Record it,
0x88000422, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by record the idle API, flags, elapsed time, version-store state, and whether maintenance was expected for a specific backlog.
- Apply only the narrow correction: treat it as a scheduling signal and avoid immediate repeated calls that only consume CPU.
- After it, recreate any context invalidated by the failure; do not carry stale HBC, cursor, file, or restore-map state into the retry.
- repeat the smallest non-destructive test that reaches the same boundary, then verify both the return value and the resulting file, cursor, backup, or database state.
Acceptance criteria for a fix
A useful regression test for this HRESULT 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. The corrected the case should change only the decisive precondition and should verify cleanup as well as the primary output. For the result backup or restore path, also prove that the resulting set can be enumerated and that no file handle or context remains active after finalization.
Boundary with 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 |
Keep the original constant and hexadecimal value in telemetry. Replacing it with “backup failed” or “database warning” removes the state information needed to select the next legal API call.
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.
- do not discard the first lower-level Win32, RPC, or JET result merely because a later cleanup call returned a more familiar error.
Technical references
- JET_ERR warning semantics — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- ESE transaction model
- Open-source ESE implementation
Looking for a different code? Search another status or error code.