| Previous | Next |
| hrAlreadyOpen | hrCouldNotConnect |
hrInvalidRecips
State represented by this code
For hrInvalidRecips, the useful interpretation begins with the object and phase that returned the value. The decisive boundary is the recipient information supplied to the legacy backup operation failed validation.
The stored Value is 0xC7FF0006 (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 this is metadata validation, not a failure to connect to the backup server. Start by preserve the recipient count, structure sizes, encoding, null entries, and the API or component that assembled the recipient list. That separates a reproducible incident from a later generic cleanup or service error.
Data for a reproducible incident
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: preserve the recipient count, structure sizes, encoding, null entries, and the API or component that assembled the recipient list.
- RPC/Win32 status beneath the HRESULT: record it together with this result and the timestamp of the first occurrence.
- 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 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.
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 recipient information supplied to the legacy backup operation failed validation |
| Narrow corrective direction | rebuild the recipient set from the documented structure and reject malformed entries before calling the API |
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.
Actions that can make diagnosis worse
- do not reuse an HBC after end, abort, or a fatal sequence error.
- do not continue after an invalid context or undefined output.
- do not discard the first lower-level Win32, RPC, or JET result merely because a later cleanup call returned a more familiar error.
Nearby ESE or AD backup states
It specifically means that this is metadata validation, not a failure to connect to the backup server. Related values below can appear in the same workflow but require a different response:
hrError | the Directory Service backup layer returned an internal failure without a more specific facility code |
|---|---|
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 |
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.
Next actions
- Record it,
0xC7FF0006, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by preserve the recipient count, structure sizes, encoding, null entries, and the API or component that assembled the recipient list.
- Apply only the narrow correction: rebuild the recipient set from the documented structure and reject malformed entries before calling the API.
- 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
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.