| Previous | Next |
| hrNoBackupDirectory | hrBackupInProgress |
hrBackupDirectoryNotEmpty
Interpretation in the backup state machine
For hrBackupDirectoryNotEmpty, treat the value as part of a state machine: it says what remained valid and what did not. The decisive boundary is the selected backup destination contains artifacts that would make the new set ambiguous.
The stored Value is 0xC80001F8 (negative JET error -504; -504). The HRESULT carries failure severity, so output state must be treated according to the individual API contract. Current ESE documentation uses JET_errBackupDirectoryNotEmpty for the corresponding published JET condition.
The first useful distinction is that the guard protects set isolation; deleting files blindly can destroy the only usable backup. Start by inventory filenames, generations, database signatures, ownership, and whether a prior aborted backup left temporary files. 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: inventory filenames, generations, database signatures, ownership, and whether a prior aborted backup left temporary files.
- 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 this result and the timestamp of the first occurrence.
- Database/log enumeration transition: record it together with this result and the timestamp of the first occurrence.
- Ordered API trace: 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 | 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 selected backup destination contains artifacts that would make the new set ambiguous |
| Narrow corrective direction | move existing artifacts to quarantine or choose a clean destination, then start a new backup 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.
Recovery or retry plan
- Record it,
0xC80001F8, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by inventory filenames, generations, database signatures, ownership, and whether a prior aborted backup left temporary files.
- Apply only the narrow correction: move existing artifacts to quarantine or choose a clean destination, then start a new backup 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.
Not the same as
It specifically means that the guard protects set isolation; deleting files blindly can destroy the only usable backup. 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 |
|---|---|
hrInvalidBackupSequence | backup APIs were called in an order that violates the ESE external-backup state machine |
hrNoBackup | a backup-only API was called when no external backup session is active |
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 omit the final end/abort path.
- do not continue using a context after a sequence failure.
- 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 selected backup destination contains artifacts that would make the new set ambiguous”, 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.