| Previous | Next |
| ERROR_LOG_RECORD_NONEXISTENT | ERROR_LOG_SPACE_RESERVED_INVALID |
ERROR_LOG_RECORDS_RESERVED_INVALID
The reserved-record count does not match CLFS reservation state
CLFS reservation APIs allow a client to reserve capacity for future records and to adjust that reservation as records are appended. This error is specifically about record-count reservation bookkeeping, not the total number of records currently stored in the log. A count or delta outside the state tracked for the reservation cannot be applied safely.
Trace the record-reservation values passed on every reserve, append, and release operation. Pay particular attention to partial completion and retries: code that replays a decrement after the first call succeeded can drive the logical count below the outstanding reservation. Also verify signed/unsigned conversion and array lengths in interop wrappers. The diagnostic data should include reservation identity, requested record adjustment, byte-space adjustment, and operation result so ERROR_LOG_RECORDS_RESERVED_INVALID can be distinguished from the separate reserved-space error.
What to inspect
- Log record-count and byte-space reservation deltas separately.
- Make retry logic aware of whether the first reservation adjustment already completed.
- Check integer conversion and reservation-collection ownership across native interop boundaries.
References
- Microsoft: ReserveAndAppendLog reservation and append semantics
- .NET LogRecordSequence over CLFS: reservations, base sequence, restart areas, and policies
- Microsoft: CreateLogMarshallingArea, block buffers, and marshalling contexts
Looking for a different code? Search another status or error code.