| Previous | Next |
| hrInvalidBackupSequence | hrDeleteBackupFileFail |
hrBackupNotAllowedYet
Where the workflow stopped
For hrBackupNotAllowedYet, the hexadecimal HRESULT is most useful when kept beside the API call and the affected artifact. The decisive boundary is the instance is temporarily in a state where a backup cannot begin safely.
The stored Value is 0xC800020B (negative JET error -523; -523). The HRESULT carries failure severity, so output state must be treated according to the individual API contract. Current ESE documentation uses JET_errBackupNotAllowedYet for the corresponding published JET condition.
The first useful distinction is that this is not evidence that backup is permanently unsupported; hrNyi is the capability boundary. Start by capture initialization/recovery status, attachment changes, active maintenance, restore state, and the first event indicating readiness. That separates a reproducible incident from a later generic cleanup or service error.
Similar-looking outcomes
This result specifically means that this is not evidence that backup is permanently unsupported; hrNyi is the capability boundary. Related values below can appear in the same workflow but require a different response:
hrNoBackupDirectory | the external-backup operation has no destination directory configured for its temporary or copied artifacts |
|---|---|
hrBackupDirectoryNotEmpty | the selected backup destination contains artifacts that would make the new set ambiguous |
hrInvalidBackupSequence | backup APIs were called in an order that violates the ESE external-backup state machine |
Keep the original constant and hexadecimal value in telemetry. Replacing this result with “backup failed” or “database warning” removes the state information needed to select the next legal API call.
Objects and state involved
| Diagnostic layer | the ESE external-backup state machine and its single active session |
|---|---|
| Relevant API surface | JetBeginExternalBackup, JetGetAttachInfo, JetOpenFile/ReadFile/CloseFile, JetGetLogInfo, and JetEndExternalBackup |
| Code-specific boundary | the instance is temporarily in a state where a backup cannot begin safely |
| Narrow corrective direction | wait for the owning instance to reach a documented stable state, then begin with a fresh context |
Database files are enumerated and copied before the backup advances to the log-file phase., the engine tracks outstanding backup file handles and rejects calls made in the wrong phase.
Minimum useful trace
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: capture initialization/recovery status, attachment changes, active maintenance, restore state, and the first event indicating readiness.
- Ordered API trace: record it together with this result and the timestamp of the first occurrence.
- Instance and active backup owner: record it together with this result and the timestamp of the first occurrence.
- Open backup file handles: record it together with it and the timestamp of the first occurrence.
- Database/log enumeration transition: 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.
Steps to resolve it
- Record it,
0xC800020B, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by capture initialization/recovery status, attachment changes, active maintenance, restore state, and the first event indicating readiness.
- Apply only the narrow correction: wait for the owning instance to reach a documented stable state, then begin with a fresh context.
- 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.
Actions that can make diagnosis worse
- do not continue using a context after a sequence failure.
- do not omit the final end/abort path.
- 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 “the instance is temporarily in a state where a backup cannot begin safely”, 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
- Begin external backup — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- Enumerating backup logs
- End external backup
- Microsoft JET_ERR enumeration
Looking for a different code? Search another status or error code.