| Previous | Next |
| ERROR_LOG_BLOCK_INCOMPLETE | ERROR_LOG_BLOCKS_EXHAUSTED |
ERROR_LOG_INVALID_RANGE
The requested LSN range is outside the active log
A CLFS stream has an active range bounded by its base LSN and the current end of valid log data. ReadLogRecord requires the starting LSN to identify a valid record in that active range, and AdvanceLogBase only accepts a new base between the current base and the last LSN. Once the base advances and containers are recycled, older addresses are no longer part of the live stream even if a caller retained their numeric LSN values.
Capture the requested low and high LSNs together with the current base and last LSN. Stale checkpoints, persisted cursors, or archive code using a range from an earlier log state are common places to look. Do not compare LSNs from different streams as though they shared a global sequence. For archive operations, PrepareLogArchive can report the active-log boundaries and current archive tail; use those values to construct a valid request rather than guessing a historical range.
What to inspect
- Query the current base and last LSN and log the exact requested range.
- Check whether a stored cursor predates a base-LSN advance or log reset.
- Verify that every compared LSN belongs to the same CLFS stream.
References
- Microsoft: CLFS log sequence numbers and stream ordering
- Microsoft: ReadLogRecord and CLFS read context modes
- Microsoft: AdvanceLogBase and the valid base-LSN range
- Microsoft: PrepareLogArchive and active-log extent snapshots
Looking for a different code? Search another status or error code.