| Previous | Next |
| WDSCP_E_CONFIG_STRING_REQUIRED | hrError |
hrInvalidParam
Operational meaning
hrInvalidParam means a legacy Directory Service backup/restore call rejected one or more arguments before advancing its context.
The stored value is 0xC7FF0001 (facility-specific HRESULT). The legacy symbolic name comes from the Windows Directory Service backup/restore message header.
The first useful distinction is that this facility-specific result belongs to the DsBackup/DsRestore contract and should not be confused with the ESE hrInvalidParameter code. Start by capturing the function name, server string, backup type, pointers, sizes, flags, and whether optional pairs were supplied consistently.
Before altering files or retrying
- Code-specific observation: capture the function name, server string, backup type, pointers, sizes, flags, and whether optional pairs were supplied consistently.
Comparison points
It specifically means that this facility-specific result belongs to the DsBackup/DsRestore contract and should not be confused with the ESE hrInvalidParameter code. Related values below can appear in the same workflow but require a different response:
hrAlreadyOpen | the backup context already has a file open when another file-open operation is attempted |
|---|---|
hrNyi | the selected legacy Directory Service backup or restore entry point is present but that operation is not implemented |
hrInvalidHandle | the HBC context or current-file state is invalid for the requested backup/restore operation |
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 condition | a legacy Directory Service backup/restore call rejected one or more arguments before advancing its context |
| Narrow corrective direction | validate the exact Ntdsbcli function signature and keep output parameters untouched on failure |
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.
Recommended handling
- Record it,
0xC7FF0001, the API name, the current phase, and all live context or file owners. - Verify the condition by capturing the function name, server string, backup type, pointers, sizes, flags, and whether optional pairs were supplied consistently.
- Apply only the targeted fix: validate the exact Ntdsbcli function signature and keep output parameters untouched on failure.
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.
Technical references
- AD backup error values — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to this HRESULT.
- AD backup walkthrough
- DsRestorePrepare contract
Looking for a different code? Search another status or error code.