| Previous | Next |
| STATUS_LOG_POLICY_INVALID | STATUS_LOG_PINNED_ARCHIVE_TAIL |
STATUS_LOG_POLICY_CONFLICT
STATUS_LOG_POLICY_CONFLICT means a policy installed on the target CLFS log prevented the requested operation. The policy can be valid on its own; the failure is the conflict between the operation and constraints such as log-size, container, growth, shrink, or tail-management behavior.
That makes it distinct from STATUS_LOG_POLICY_INVALID, which concerns an invalid policy set, and from STATUS_LOG_POLICY_ALREADY_INSTALLED, which concerns a duplicate type. Removing a policy blindly may undermine capacity or archive assumptions shared by other log clients.
Identify the policy-operation collision
- Capture the requested operation, target log, and effective policy values before making a change.
- Check whether a shared managed client owns or depends on the policy that is blocking the operation.
- Choose a policy-compliant operation, or coordinate a documented policy change with every affected client.
References
- Microsoft: CLFS policy-based management
- Microsoft: CLFS policy considerations
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.