| Previous | Next |
| ERROR_LOG_CONTAINER_LIMIT_EXCEEDED | ERROR_LOG_POLICY_ALREADY_INSTALLED |
ERROR_LOG_START_OF_LOG
A backward CLFS read reached the start of the log
CLFS supports linked traversal through previous-record and undo-next chains, and restart APIs can read earlier restart areas. The stream still has a beginning defined by its active range. Microsoft documents the corresponding start-of-log condition when ReadPreviousLogRestartArea has no earlier restart area. This is a boundary result, not evidence that the current record is corrupt.
Inspect the read mode and the caller loop termination condition. A reverse scanner should treat start-of-log as the end of available history and stop or switch to its higher-level recovery logic. If the application expected older records, check whether the base LSN advanced, old containers were recycled, or the stream was reset. Retrying the same previous-read call cannot reveal records that are no longer in the active range. Archive storage, when used, is a separate source of older physical-log history.
What to inspect
- Treat start-of-log as a traversal boundary unless the application contract requires older retained history.
- Record the current record LSN and base LSN when the boundary is reached.
- Check archive retention or prior base-LSN advances if older history was expected.
References
- Microsoft: ReadPreviousLogRestartArea and restart history
- Microsoft: ReadLogRecord and CLFS read context modes
- Microsoft: CLFS log sequence numbers and stream ordering
- Microsoft: CLFS archive mode, archive tail, and physical-log archive contexts
Looking for a different code? Search another status or error code.