| Previous | Next |
| hrBFPageNotFound | hrFLDKeyTooBig |
hrRemainingVersions
Interpretation in the backup state machine
For hrRemainingVersions, a correct handler first decides whether the value is success, warning, or failure, then examines the documented outputs. The decisive boundary is version-store cleanup still has work queued after an idle-maintenance pass.
The stored Value is 0x88000141 (positive JET status 321; 321). 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_wrnRemainingVersions for the corresponding published JET condition.
The first useful distinction is that the warning reports unfinished maintenance, not immediate transaction failure. Start by measure outstanding version pages, oldest transaction age, active sessions, and whether repeated idle calls make progress. That separates a reproducible incident from a later generic cleanup or service error.
Start with these observations
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: measure outstanding version pages, oldest transaction age, active sessions, and whether repeated idle calls make progress.
- 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 this result 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.
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 | version-store cleanup still has work queued after an idle-maintenance pass |
| Narrow corrective direction | end or shorten transactions retaining old versions and schedule further idle work without spinning in a tight retry loop |
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.
Recovery or retry plan
- Record it,
0x88000141, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by measure outstanding version pages, oldest transaction age, active sessions, and whether repeated idle calls make progress.
- Apply only the narrow correction: end or shorten transactions retaining old versions and schedule further idle work without spinning in a tight retry loop.
- 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.
Not the same as
It specifically means that the warning reports unfinished maintenance, not immediate transaction failure. Related values below can appear in the same workflow but require a different response:
hrNoIdleActivity | an idle-maintenance request found no eligible work to perform at that moment |
|---|---|
hrBadDbSignature | the database signature does not match the backup or log set used for recovery |
hrCouldNotConnect | the backup client could not establish the required session with the selected server or running Directory Service |
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.
Acceptance criteria for a fix
A useful regression test for this HRESULT should force the condition “version-store cleanup still has work queued after an idle-maintenance pass”, 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.
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.