| Previous | Next |
| ERROR_CANNOT_GRANT_REQUESTED_OPLOCK | ERROR_OPLOCK_HANDLE_CLOSED |
ERROR_CANNOT_BREAK_OPLOCK
Atomic create-with-oplock could not proceed without breaking another oplock
FILE_FLAG_OPEN_REQUIRING_OPLOCK asks Windows to open the file and establish the opportunity to request an oplock as one atomic sequence. Before completing the create, the file system checks existing oplocks. If the new open would break one, it returns this error instead of opening the file and exposing a race between the open and the later oplock request.
This result is expected contention behavior for atomic create-with-oplock, not evidence that the file system cannot process oplocks. Retry only according to the application concurrency design: wait for the existing owner, open without the atomic flag, or choose compatible access and sharing. If the atomic open succeeds, request the oplock immediately; performing unrelated file operations before the request can deadlock other opens.
What to inspect
- Confirm FILE_FLAG_OPEN_REQUIRING_OPLOCK was intentionally requested.
- Inspect existing oplock owners and incompatible access modes.
- Do not spin on the open while the same owner remains active.
References
- Microsoft: opportunistic lock operations
- Microsoft: oplock types and break behavior
- Microsoft: FSCTL_REQUEST_OPLOCK
- Microsoft: atomic open requiring an oplock
Looking for a different code? Search another status or error code.