| Previous | Next |
| ERROR_LOG_MULTIPLEXED | ERROR_LOG_ARCHIVE_NOT_IN_PROGRESS |
ERROR_LOG_DEDICATED
The target is a dedicated CLFS log
A dedicated CLFS log is created when the log name identifies only the physical log and no separate stream name is supplied. The dedicated stream owns its physical log, unlike a multiplexed log where several named streams share containers. An API or code path written for multiplexed stream management can therefore be invalid when applied to a dedicated handle.
Record the exact log name and handle-creation path. If the application expected a multiplexed log, check whether the stream suffix was omitted or lost during configuration or string construction. If a dedicated log is intentional, use operations appropriate for its single stream and physical log. Converting an existing deployment by renaming files is not sufficient; dedicated versus multiplexed mode is part of how CLFS creates and addresses the log. Plan migration through supported log creation and client recovery semantics.
What to inspect
- Inspect the CreateLogFile name and whether a stream component is present.
- Verify the caller selected APIs and management logic for the actual log type.
- Recreate or migrate intentionally; do not infer multiplexing from filename layout alone.
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.