| Previous | Next |
| STATUS_LOG_NOT_ENOUGH_CONTAINERS | STATUS_LOG_CLIENT_NOT_REGISTERED |
STATUS_LOG_CLIENT_ALREADY_REGISTERED
STATUS_LOG_CLIENT_ALREADY_REGISTERED means the caller attempted to register a managed CLFS client that the stream already recognizes. Managed registration is part of the cooperation model used for full-log handling and tail advancement, not a per-operation permission token.
A duplicate registration often signals lifecycle confusion: a retry path may have re-ran initialization after a partial success, or two components may be using the same identity without coordinating ownership. Re-registering until success can hide that design error.
What to inspect
- Track the client identity, stream, registration handle, and owner across initialization and recovery paths.
- Make registration idempotent only when the component can prove that the existing registration belongs to its current lifecycle.
- Unregister through the owner that created the managed client; do not drop a shared registration because another component observed a duplicate.
References
- Microsoft: ClfsMgmtHandleLogFileFull and full-log handling
- Microsoft: CLFS containers, tail pinning, and managed clients
- Microsoft: container, reservation, append, and flush APIs
- Wine: independent NTSTATUS constant definitions
Looking for a different code? Search another status or error code.