| Previous | Next |
| STATUS_LOG_BLOCKS_EXHAUSTED | STATUS_LOG_RESTART_INVALID |
STATUS_LOG_READ_CONTEXT_INVALID
STATUS_LOG_READ_CONTEXT_INVALID applies to a CLFS read sequence rather than to the payload of one record. ReadLogRecord starts a sequence and returns a read context; subsequent reads use that context, and TerminateReadLog releases the resources associated with it.
The important distinction from STATUS_LOG_READ_MODE_INVALID is that this status concerns the context supplied to the sequence, whereas the latter concerns the selected traversal mode. A read context must not be treated as a durable record identifier or reused after its lifecycle has ended.
Audit the read-context lifecycle
- Keep the log handle, marshaling area, initial LSN, and returned read context associated in the caller state.
- Do not issue another sequence operation with a context after termination or after the owning log state has been reset or closed.
- When reproducing the failure, log the API call order and requested read direction rather than logging only the final LSN.
References
- Microsoft: CLFS API reference for read contexts
- Microsoft: Common Log File System concepts
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.