| Previous | Next |
| E_FDPAIRING_NOPROFILES | MSG_CI_MASTER_MERGE_CANT_START |
hrNyi
Operational meaning
hrNyi means the selected legacy Directory Service backup or restore entry point is present but that operation is not implemented.
The stored value is 0xC0000001 (facility-specific HRESULT). The legacy symbolic name comes from the Windows Directory Service backup/restore message header.
The first useful distinction is that this is a capability boundary, not a transient service outage or malformed parameter. Start by recording the exact exported function, operating-system version, requested backup type, flags, and component being protected.
Before altering files or retrying
- Code-specific observation: record the exact exported function, operating-system version, requested backup type, flags, and component being protected.
Comparison points
It specifically means that this is a capability boundary, not a transient service outage or malformed parameter. Related values below can appear in the same workflow but require a different response:
hrRestoreInProgress | another restore context already owns the Directory Service restore workflow |
|---|---|
hrInvalidParam | a legacy Directory Service backup/restore call rejected one or more arguments before advancing its context |
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 | the selected legacy Directory Service backup or restore entry point is present but that operation is not implemented |
| Narrow corrective direction | use a supported VSS-based path or another documented operation instead of retrying the same call |
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,
0xC0000001, the API name, the current phase, and all live context or file owners. - Verify the condition by recording the exact exported function, operating-system version, requested backup type, flags, and component being protected.
- Apply only the targeted fix: use a supported VSS-based path or another documented operation instead of retrying the same call.
Acceptance criteria for a fix
A useful regression test should force the condition “the selected legacy Directory Service backup or restore entry point is present but that operation is not implemented”, call one documented API transition, and assert the exact HRESULT.
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.