| Previous | Next |
| STATUS_LOG_CLIENT_ALREADY_REGISTERED | STATUS_LOG_FULL_HANDLER_IN_PROGRESS |
STATUS_LOG_CLIENT_NOT_REGISTERED
STATUS_LOG_CLIENT_NOT_REGISTERED identifies a missing managed-client relationship on the stream. Operations that ask CLFS management to make space or coordinate tail movement require the client registration established for that specific stream and lifecycle.
It is not a generic authentication failure. A valid log handle can still be insufficient if the caller is using a management API without the corresponding managed-client state.
What to inspect
- Verify that registration completed successfully on the same stream and has not been unregistered or invalidated during shutdown.
- Pass the managed-client object returned by the registration path, not a reconstructed or stale identity.
- Separate missing registration from
STATUS_LOG_CLIENT_ALREADY_REGISTERED; they require opposite lifecycle corrections.
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.