| Previous | Next |
| ERROR_LOG_PINNED_ARCHIVE_TAIL | ERROR_LOG_RECORDS_RESERVED_INVALID |
ERROR_LOG_RECORD_NONEXISTENT
The requested CLFS record is not present in the log
An LSN identifies an individual record within a CLFS stream, and ReadLogRecord requires the starting LSN to refer to a valid record in the active range. A numeric LSN can fail this requirement even when it lies between broad range boundaries: it may not correspond to a record start, may belong to another stream, or may reference data that has been truncated or recycled.
Log the full LSN and the stream identity that produced it. Avoid synthesizing record addresses by incrementing LSN fields; forward traversal should use a CLFS read context, which returns records in the selected mode. Check persisted cursors after AdvanceLogBase, TruncateLog, reset, or log recreation. If the application stores LSNs externally, pair them with enough log identity/version state to detect that the physical log has been replaced rather than applying an old address to a new stream.
What to inspect
- Verify the LSN came from CLFS for the same stream rather than being arithmetically constructed.
- Check whether the stream base advanced, was truncated, reset, or recreated after the cursor was saved.
- Use ReadNextLogRecord traversal instead of guessing the next physical record address.
References
- Microsoft: CLFS log sequence numbers and stream ordering
- Microsoft: ReadLogRecord and CLFS read context modes
- Microsoft: AdvanceLogBase and the valid base-LSN range
Looking for a different code? Search another status or error code.