| Previous | Next |
| hrCircularLogging | hrCommunicationError |
hrNoFullRestore
Operational meaning
For hrNoFullRestore, the hexadecimal HRESULT is most useful when kept beside the API call and the affected artifact. The decisive boundary is an incremental restore was requested before a full backup had established the destination database baseline.
The stored Value is 0xC7FF000C (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 hrMissingFullBackup concerns backup-chain history; this code describes the restore sequence at the destination. Start by record the restore catalog order, target database state, full-backup identity, and which set the application marked as current. 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 restore catalog order, target database state, full-backup identity, and which set the application marked as current.
- Final status passed to completion: record it together with this result and the timestamp of the first occurrence.
- Restore type and HBC: record it together with this result and the timestamp of the first occurrence.
- Old/new path map: record it together with this result and the timestamp of the first occurrence.
- Directory lock owner: 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 hrMissingFullBackup concerns backup-chain history; this code describes the restore sequence at the destination. Related values below can appear in the same workflow but require a different response:
hrRestoreMapExists | a restore map is already registered for the component while the caller attempts to add another mapping |
|---|---|
hrExistingLogFileIsNotContiguous | the log sequence already present in the target path contains a generation gap required by recovery |
hrFileOpenReadOnly | the database file was opened in read-only mode and the resulting handle cannot support logged updates |
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 | offline AD restore preparation, path mapping, directory locking, and HBC lifetime |
|---|---|
| Relevant API surface | DsRestorePrepare, DsRestoreGetDatabaseLocations, DsRestoreRegister, DsRestoreRegisterComplete, and DsRestoreEnd |
| Code-specific boundary | an incremental restore was requested before a full backup had established the destination database baseline |
| Narrow corrective direction | restore and validate the matching full set first, then apply only its contiguous incremental descendants |
Legacy AD restore is performed offline and the restore directories are registered and locked before files are replaced., restore completion status affects whether Active Directory is allowed to start.
Recommended handling
- Record it,
0xC7FF000C, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by record the restore catalog order, target database state, full-backup identity, and which set the application marked as current.
- Apply only the narrow correction: restore and validate the matching full set first, then apply only its contiguous incremental descendants.
- 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 this HRESULT should force the condition “an incremental restore was requested before a full backup had established the destination database baseline”, 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 report success to completion when file restoration failed.
- do not copy files before the restore directories are prepared and locked.
- 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 restore walkthrough — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- DsRestorePrepare contract
- Restore completion contract
- Microsoft list of AD DS backup errors
Looking for a different code? Search another status or error code.