| Previous | Next |
| ERROR_LOG_POLICY_INVALID | ERROR_LOG_PINNED_ARCHIVE_TAIL |
ERROR_LOG_POLICY_CONFLICT
A CLFS policy blocks the requested physical-log change
CLFS uses installed management policies to control operations such as log growth, shrink timing, maximum size, minimum size, and new-container sizing. A policy conflict means the requested operation is meaningful in CLFS but violates the effective management constraints. This differs from ERROR_LOG_POLICY_INVALID, where the policy set itself is not valid.
Identify the exact operation and query the policy types capable of constraining it. For a growth request, inspect maximum size, auto-grow, growth rate, and container size. For shrink or container removal, inspect minimum size and shrink policy. Then decide whether the operation is wrong or the configured policy no longer matches the workload. Avoid bypassing CLFS by manipulating files; policy enforcement is protecting physical-log invariants and the administrator or application sizing contract.
What to inspect
- Record the rejected CLFS operation before changing policy settings.
- Query only the relevant policy types, then review the complete set for interactions.
- Change policy deliberately or change the caller behavior; do not remove containers outside CLFS.
References
- Microsoft: CLFS management policy types
- Microsoft: policy interactions and CLFS management considerations
- Microsoft: ClfsMgmtHandleLogFileFull growth and tail-advance workflow
Looking for a different code? Search another status or error code.