| Previous | Next |
| hrIncrementalBackupDisabled | hrCircularLogging |
hrLogFileNotFound
State represented by this code
For hrLogFileNotFound, treat the value as part of a state machine: it says what remained valid and what did not. The decisive boundary is an incremental Directory Service backup cannot assemble the required transaction-log set.
The stored Value is 0xC7FF000A (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 hrMissingLogFile is an ESE current-log failure; this code is the higher-level incremental-backup contract. Start by enumerate the expected and present log generations, checkpoint position, prior truncation, circular-logging state, and backup catalog. 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: enumerate the expected and present log generations, checkpoint position, prior truncation, circular-logging state, and backup catalog.
- Catalog and truncation history: record it together with this result and the timestamp of the first occurrence.
- Full and incremental backup IDs: record it together with this result and the timestamp of the first occurrence.
- Database and log signatures: record it together with this result and the timestamp of the first occurrence.
- Generation range and checkpoint: 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 | full-backup baseline, incremental descendants, retained log generations, and catalog lineage |
|---|---|
| Relevant API surface | DsBackupPrepare backup type, log enumeration/truncation, and ESE external backup |
| Code-specific boundary | an incremental Directory Service backup cannot assemble the required transaction-log set |
| Narrow corrective direction | recover the missing log only from the same lineage or abandon the incremental attempt and create a full backup |
An incremental backup depends on a previous full database image and a continuous required log history., circular logging retires old generations based on checkpoint state rather than backup-chain retention needs.
Actions that can make diagnosis worse
- do not delete logs manually to make a directory look clean.
- do not combine an incremental set with an unrelated full backup.
- 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 hrMissingLogFile is an ESE current-log failure; this code is the higher-level incremental-backup contract. Related values below can appear in the same workflow but require a different response:
hrFullBackupNotTaken | the caller requested an incremental backup without a completed full backup recorded as its baseline |
|---|---|
hrMissingFullBackup | an incremental backup set does not have the earlier full backup required to establish its database baseline |
hrCircularLogging | the Directory Service component is using circular logs, so the historical range needed for an incremental backup is not guaranteed to remain |
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,
0xC7FF000A, the API name, the current phase, and all live context or file owners. - Verify the decisive condition by enumerate the expected and present log generations, checkpoint position, prior truncation, circular-logging state, and backup catalog.
- Apply only the narrow correction: recover the missing log only from the same lineage or abandon the incremental attempt and create a full backup.
- 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 walkthrough — API ordering, file semantics, warning/error interpretation, or recovery behavior relevant to it.
- ESE files and circular logging
- External backup sequence
- Microsoft JET_ERR enumeration
- Microsoft list of AD DS backup errors
Looking for a different code? Search another status or error code.