| Previous | Next |
| hrRestoreInProgress | hrInvalidRecips |
hrAlreadyOpen
What this return value changes
For hrAlreadyOpen, the hexadecimal HRESULT is most useful when kept beside the API call and the affected artifact. The decisive boundary is the backup context already has a file open when another file-open operation is attempted.
The stored Value is 0xC7FF0005 (facility-specific HRESULT). The HRESULT carries failure severity, so output state must be treated according to the individual API contract. The legacy this result name comes from the Windows Directory Service backup/restore message header.
The first useful distinction is that the legacy context permits one current file; the result does not mean another process has the file open at the operating-system layer. Start by record the current filename, requested filename, HBC owner, and whether DsBackupClose was reached on every prior branch. That separates a reproducible incident from a later generic cleanup or service error.
Objects and state involved
| Diagnostic layer | the legacy Ntdsbcli HBC context and exact API call contract |
|---|---|
| Relevant API surface | DsBackupPrepare/OpenFile/Read/Close/End and DsRestorePrepare/Register/Complete/End |
| Code-specific boundary | the backup context already has a file open when another file-open operation is attempted |
| Narrow corrective direction | close the current backup file and serialize file iteration within the context |
Beginning with Windows Vista, Microsoft directs new implementations to VSS instead of these legacy functions., the HBC state advances across calls and must be released even when a later step fails.
Evidence worth preserving
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 current filename, requested filename, HBC owner, and whether DsBackupClose was reached on every prior branch.
- Function and parameter values: record it together with this result and the timestamp of the first occurrence.
- HBC creation and owner: record it together with this result and the timestamp of the first occurrence.
- Current open file: record it together with this result and the timestamp of the first occurrence.
- RPC/Win32 status beneath the HRESULT: 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.
How to distinguish nearby results
It specifically means that the legacy context permits one current file; the result does not mean another process has the file open at the operating-system layer. Related values below can appear in the same workflow but require a different response:
hrInvalidHandle | the HBC context or current-file state is invalid for the requested backup/restore operation |
|---|---|
hrNyi | the selected legacy Directory Service backup or restore entry point is present but that operation is not implemented |
hrError | the Directory Service backup layer returned an internal failure without a more specific facility code |
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.
A safe response sequence
- Record it,
0xC7FF0005, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by record the current filename, requested filename, HBC owner, and whether DsBackupClose was reached on every prior branch.
- Apply only the narrow correction: close the current backup file and serialize file iteration within the 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 after an invalid context or undefined output.
- do not reuse an HBC after end, abort, or a fatal sequence error.
- 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 it should force the condition “the backup context already has a file open when another file-open operation is attempted”, 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
- AD backup error values — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- AD backup walkthrough
- DsRestorePrepare contract
Looking for a different code? Search another status or error code.