| Previous | Next |
| STATUS_BAD_MCFG_TABLE | STATUS_BAD_KEY |
STATUS_CANNOT_BREAK_OPLOCK
The requested action conflicts with an existing oplock and must not break it
Some file-system operations provide a “do not break oplocks” semantic so callers can test or perform work only when cached state remains undisturbed. This status means an incompatible oplock exists and honoring the caller’s restriction prevents the operation.
It is not equivalent to a generic sharing violation. The caller deliberately chose atomic failure over triggering the break. Recovery depends on whether that guarantee is essential.
What to inspect
- Identify the option or FSCTL that requested no-oplock-break behavior.
- Record the existing oplock owner and level if available through tracing.
- Retry without the restriction only when the application can tolerate notifying the oplock owner and waiting for break processing.
References
- Microsoft: FSCTL_REQUEST_OPLOCK
- Microsoft: Types of Opportunistic Locks
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.