| Previous | Next |
| ERROR_LOG_FULL_HANDLER_IN_PROGRESS | ERROR_LOG_CONTAINER_WRITE_FAILED |
ERROR_LOG_CONTAINER_READ_FAILED
Log service encountered an error when attempting to read from a log container.
ERROR_LOG_CONTAINER_READ_FAILED is Win32 error 6639 (0x000019EF) in Common Log File System (CLFS).
Where the result appears
- opening existing log records after service restart.
- scanning containers during recovery or archive validation.
- reading a container stored in an NTFS stream.
- replaying transaction records from a dedicated CLFS log.
What to verify
Verify whether the selected container can be read consistently through the file system and storage stack. Check container path or stream name, read offset and requested byte count, and underlying NTSTATUS or storage error.
Likely causes
- the container file or stream is inaccessible.
- a storage or file-system read failed.
- container metadata points to an invalid extent or offset.
- security or sharing state changed after the log was opened.
- media corruption prevents a complete read.
Troubleshooting steps
- Collect container path or stream name.
- Record read offset and requested byte count.
- Correlate underlying NTSTATUS or storage error with the owning application log, CLFS-related System events, storage events, and any transaction or recovery trace.
Handling, retry, and recovery
Preserve the affected log, verify the volume and container metadata, restore a known-good copy when required, and avoid deleting containers until recovery requirements are understood.
Related errors
ERROR_LOG_CONTAINER_OPEN_FAILED occurs before a usable container handle exists; this code reports failure after the container was selected for reading.
Example
A transaction service restarts and cannot replay a specific container. The failing offset maps to a damaged disk extent, and restoring that container from the coordinated backup allows replay to continue without discarding later logs.
References
Looking for a different code? Search another status or error code.