Help diagnosing STATUS_SHARING_VIOLATION via SMB2 as generated from a windows 2016 server

simon wilks 1 Reputation point
2022-09-08T11:06:55.047+00:00

Morning

Im getting read only errors when a file clearly is not open in computer manager from the server.

Doing a wire shark we are seeing

SMB2 29359 STATUS_SHARING_VIOLATION Create Create Response, Error: STATUS_SHARING_VIOLATION

Coming from the server

What logs / debug can we do on the server to understand why the server is pushing this response out to the client please?

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,368 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Gary Nebbett 5,721 Reputation points
    2022-09-09T08:00:39.68+00:00

    Hello Simon,

    This is an example of the maximum amount of server-side SMB2 tracing that I can easily obtain - it seems to show that the STATUS_SHARING_VIOLATION is detected solely by the file system. Nothing SMB2 specific seems to happen in the detection:

    239424-image.png

    I would suggest first checking what happens when you try to open the file directly on the file server and then set about tracking down which other process(es) have opened the file.

    Gary

    0 comments No comments