| Previous | Next |
| ERROR_LOG_READ_MODE_INVALID | ERROR_LOG_METADATA_CORRUPT |
ERROR_LOG_NO_RESTART
No restart area has been written to this CLFS stream
ReadLogRestartArea returns the most recently written successful restart area. Restart areas are client checkpoint records; CLFS does not invent the client recovery payload. Transactional resource managers are expected to write restart areas periodically so recovery can begin from known checkpoint state. A stream with ordinary data records but no restart area is therefore possible, but an application that requires checkpoint-based recovery must handle that initial state explicitly.
Determine whether the stream is new, was reset, or belongs to a client that has not yet completed its first checkpoint. Review the caller logic for an assumption that every opened stream already contains restart data. On first use, the application may need to initialize its own recovery state and write a restart area after establishing a consistent checkpoint. Do not treat an absent restart area as the same condition as ERROR_LOG_RESTART_INVALID; the latter indicates unusable restart information was encountered.
What to inspect
- Confirm whether the stream is newly created or was recently reset or recreated.
- Trace successful WriteLogRestartArea calls and their flush/completion status.
- Make the client recovery path distinguish an empty initial stream from a damaged restart area.
References
- Microsoft: ReadLogRestartArea and restart read contexts
- Microsoft: CLFS log streams and restart areas used for transactional recovery
- Microsoft: Common Log File System functions and operation groups
Looking for a different code? Search another status or error code.