| Previous | Next |
| ERROR_LOG_METADATA_CORRUPT | ERROR_LOG_METADATA_INCONSISTENT |
ERROR_LOG_METADATA_INVALID
The file presented as CLFS metadata is not a valid CLFS base log
The base log file is the CLFS metadata anchor for a physical log. This status differs from metadata corruption: the file does not look like metadata that the log file system could have created. A wrong file at the expected .blf path, a renamed arbitrary file, or a mismatched restore can therefore produce a different diagnostic path from damage to a previously valid CLFS metadata structure.
Verify the exact log name passed to CreateLogFile and resolve it to the physical base-log path. Check deployment, restore, and cleanup scripts for filename collisions or accidental replacement. For multiplexed logs, also distinguish the physical log name from the stream name after the double-colon separator. Do not simply add a .blf extension to an application path and assume the resulting file is a valid CLFS log. If the path is correct but the file identity is wrong, preserve it and let the owning component recreate the log only after its recovery requirements are understood.
What to inspect
- Record the exact CLFS log-name string used by the caller and the resulting base-log path.
- Inspect file creation and restore history for replacement or filename collisions.
- For multiplexed logs, verify physical log and stream names are not being confused.
References
- Microsoft: CLFS base log files, containers, dedicated and multiplexed logs
- Microsoft: dedicated CLFS logs and physical log storage
- Microsoft: clfsw32 API reference
Looking for a different code? Search another status or error code.