| Previous | Next |
| ERROR_LOG_SPACE_RESERVED_INVALID | ERROR_LOG_FULL |
ERROR_LOG_TAIL_INVALID
The requested CLFS tail or base position is outside its permitted LSN range
CLFS has several boundary LSNs with different meanings. AdvanceLogBase requires a new base between the current base and the last LSN of the stream. SetLogArchiveTail requires a valid physical LSN in the log and uses it as the last archived position. Confusing a stream LSN, a physical archive-tail LSN, or an address from another log can make an otherwise well-formed value invalid.
Record which API rejected the value and query the current base, last LSN, and archive tail before retrying. Preserve the originating log identity with any persisted boundary cursor. For archive code, use the LSNs returned by PrepareLogArchive and the archive extent sequence; for stream reclamation, advance the base only to a valid record boundary allowed by CLFS. Never clamp a rejected LSN numerically without understanding its container and stream context.
What to inspect
- Identify whether the value is a stream base, physical archive tail, or another boundary LSN.
- Compare it with current CLFS-reported boundaries immediately before the failing call.
- Reject stale or cross-stream persisted LSNs instead of coercing them into the current range.
References
- Microsoft: AdvanceLogBase and the valid base-LSN range
- Microsoft: SetLogArchiveTail and physical archive-tail LSN requirements
- Microsoft: PrepareLogArchive and active-log extent snapshots
- Microsoft: CLFS log sequence numbers and stream ordering
Looking for a different code? Search another status or error code.