| Previous | Next |
| ERROR_LOG_DEDICATED | ERROR_LOG_ARCHIVE_IN_PROGRESS |
ERROR_LOG_ARCHIVE_NOT_IN_PROGRESS
The archive operation has no active CLFS archive context
PrepareLogArchive snapshots the current active physical log and returns an archive context. That context maintains cursor state while the client enumerates archive extents and reads the metadata snapshot. Archive functions that depend on this state cannot be called before preparation or after TerminateLogArchive has released the context.
Trace the archive lifecycle as one state machine: PrepareLogArchive, metadata and extent reads, durable copy, tail update where appropriate, and TerminateLogArchive. Look for error cleanup that terminates the context and then falls through into another read, or for worker code that receives an archive task without the associated context. Do not persist the opaque context across process restarts. Start a new archive snapshot and use its reported base, last LSN, and current archive tail.
What to inspect
- Log archive-context creation and termination with the physical log identity.
- Stop extent or metadata iteration immediately after archive cleanup or failed preparation.
- Create a new archive context after process restart instead of reusing serialized state.
References
- Microsoft: PrepareLogArchive and active-log extent snapshots
- Microsoft: CLFS archive mode, archive tail, and physical-log archive contexts
- Microsoft: clfsw32 API reference
Looking for a different code? Search another status or error code.