| Previous | Next |
| ERROR_LOG_POLICY_ALREADY_INSTALLED | ERROR_LOG_POLICY_INVALID |
ERROR_LOG_POLICY_NOT_INSTALLED
The requested management policy is absent from the log
CLFS management policies are optional per-log controls. Auto-grow, maximum size, log-tail behavior, and container naming are separate policy types; the presence of one does not imply another is installed. An operation that queries, removes, or relies on a specific policy can therefore fail when that type was never installed or was removed earlier.
Query the policy type explicitly and inspect the configuration order of the managing client. A startup race can occur when a log-full path runs before policy installation completes, while cleanup code can attempt to remove a policy twice. Do not infer policy presence from the current log size or container names, because existing state can outlive the policy that created it. Make configuration idempotent by treating absent policy state deliberately and installing only the policy types the application actually manages.
What to inspect
- Log the requested PolicyType and enumerate the policy set before modification.
- Check initialization ordering between managed-client registration and policy installation.
- Handle repeated cleanup or configuration calls without assuming the policy still exists.
References
- Microsoft: CLFS management policy types
- Microsoft: policy interactions and CLFS management considerations
- Microsoft: ClfsMgmtRegisterManagedClient and managed-client cookies
Looking for a different code? Search another status or error code.