| Previous | Next |
| ERROR_PARTIAL_COPY | ERROR_INVALID_OPLOCK_PROTOCOL |
ERROR_OPLOCK_NOT_GRANTED
The requested oplock was denied before caching rights were established
An oplock is a file-system caching agreement, not an ordinary byte-range lock. A client asks for read, write, or handle caching rights and the file system grants them only when existing opens, share modes, locks, and the underlying file system permit that level. This status means the request itself was denied; the caller must not assume that cached data or deferred writes are protected by an oplock.
Treat the failure as a capability decision for this open instance. A local application can normally continue with uncached or less aggressively cached I/O. Check whether the handle was opened for overlapped I/O, whether another process has the file open incompatibly, and whether the request was sent directly to a remote file instead of allowing the network redirector to manage remote oplocks.
What to inspect
- Record the requested oplock level and the handle access/share flags.
- List competing opens, locks, and filter drivers affecting the file.
- Continue without oplock-dependent caching or request a weaker level.
References
- Microsoft: opportunistic lock operations
- Microsoft: oplock types and break behavior
- Microsoft: FSCTL_REQUEST_OPLOCK
Looking for a different code? Search another status or error code.