| Previous | Next |
| ERROR_LOG_START_OF_LOG | ERROR_LOG_POLICY_NOT_INSTALLED |
ERROR_LOG_POLICY_ALREADY_INSTALLED
The log already has this type of CLFS management policy
CLFS management defines policy types for auto-grow, auto-shrink, growth rate, log-tail handling, maximum and minimum size, and new-container naming and size. Policy installation is keyed by policy type: installing another policy of a type already present is not a way to update the current value. The duplicate is rejected so the active policy set remains explicit.
Query the installed policy set and compare the PolicyType before attempting installation. If the goal is to change a value, use the documented policy-management sequence for the API layer in use rather than blindly replaying initialization code. This often appears when startup code is not idempotent or when two modules both assume ownership of log sizing. Establish a single owner for each management policy type and log the effective settings after configuration.
What to inspect
- Enumerate installed policies and match the exact CLFS_MGMT_POLICY_TYPE.
- Separate policy creation from policy update in initialization and retry logic.
- Identify competing components that both configure growth or container policies on the same log.
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.