| Previous | Next |
| ERROR_LOG_CLIENT_ALREADY_REGISTERED | ERROR_LOG_FULL_HANDLER_IN_PROGRESS |
ERROR_LOG_CLIENT_NOT_REGISTERED
The caller has no active CLFS management-client registration
CLFS management routines such as the log-full handler operate on the client cookie returned by ClfsMgmtRegisterManagedClient. Registration connects the log stream with client callbacks and management state. If the client was never registered, registration failed, or teardown already deregistered it, management operations cannot use the stale or absent client identity.
Check the result of the original registration call and do not manufacture or cache a cookie across process lifetime boundaries. Trace teardown and error-recovery paths for premature deregistration while worker threads can still request log growth. If the application does not need managed growth and tail callbacks, it should not call managed-client routines at all. Otherwise, make registration lifetime encompass every operation that can invoke ClfsMgmtHandleLogFileFull or related management functions.
What to inspect
- Verify the register call succeeded and the returned client cookie is the one passed to management APIs.
- Stop workers before deregistration so no log-full request races with teardown.
- Never persist or reconstruct an opaque CLFS management-client cookie.
References
- Microsoft: ClfsMgmtRegisterManagedClient and managed-client cookies
- Microsoft: ClfsMgmtHandleLogFileFull growth and tail-advance workflow
- Microsoft: ClfsLogGrowthCompleteCallback and asynchronous log-full completion
Looking for a different code? Search another status or error code.