| Previous | Next |
| ERROR_LOG_METADATA_FLUSH_FAILED | ERROR_LOG_APPENDED_FLUSH_FAILED |
ERROR_LOG_INCONSISTENT_SECURITY
Security on the log and its containers is inconsistent.
ERROR_LOG_INCONSISTENT_SECURITY is Win32 error 6646 (0x000019F6).
Where the result appears
- opening a log copied from another server.
- adding a container created under a different identity.
- restoring containers separately.
- changing permissions on a log directory or NTFS stream.
What to verify
Verify whether the base log and every container expose a compatible owner, DACL, integrity level, and access policy. Check security descriptor for base log and each container, owner and inheritance flags, and service token and privileges.
Likely causes
- a container inherited a different ACL.
- owner or integrity information differs from the base log.
- backup restored data without matching security metadata.
- manual permission changes touched only part of the log.
- service identities changed without an ACL migration.
Troubleshooting steps
- Collect security descriptor for base log and each container.
- Record owner and inheritance flags.
- Correlate service token and privileges with the owning application log, CLFS-related System events, storage events, and any transaction or recovery trace.
Handling, retry, and recovery
Derive the intended security descriptor from the owning application, apply it consistently to the complete log set, verify effective access as the service identity, and then reopen the log.
Related errors
ERROR_ACCESS_DENIED reports one failed access check; this code reports that the log set itself has inconsistent security configuration.
Example
A restored base log keeps its original ACL while one container inherits permissions from a new folder. Aligning owner and DACL across the set allows CLFS to open the log safely.
References
Looking for a different code? Search another status or error code.