| Previous | Next |
| E_FDPAIRING_NOPROFILES | MSG_CI_MASTER_MERGE_CANT_START |
hrNyi
Operational meaning
For hrNyi, this result identifies a specific state transition rather than a generic “database failure.” The decisive boundary is 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 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 a capability boundary, not a transient service outage or malformed parameter. Start by record the exact exported function, operating-system version, requested backup type, flags, and component being protected. That separates a reproducible incident from a later generic cleanup or service error.
Before altering files or retrying
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 exact exported function, operating-system version, requested backup type, flags, and component being protected.
- 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 it 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.
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 |
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.
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 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 decisive condition by record the exact exported function, operating-system version, requested backup type, flags, and component being protected.
- Apply only the narrow correction: use a supported VSS-based path or another documented operation instead of retrying the same call.
- 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
A useful regression test for it 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. 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.
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.
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.