![sharing violation sharing violation](https://www.repairmsexcel.com/blog/wp-content/uploads/2019/08/excel-document-properties-ribbon2010-694-469.png)
That our service is locking the file itselves? How would I see this in ProMon logs?įile operations that happened before the sharing violation took place: 10:48:20 10:48:20,4800493 OurService.exe 3824 2596 domainname\domainuser 3100 IRP_MJ_DIRECTORY_CONTROL \\server\folder1\folder2\file.ext Read Metadata SUCCESS Type: QueryDirectory, Filter: 0AA35B070930437A8351A56941A46175.sm, 2: 0AA35B070930437A8351A56941A46175.sm But my understanding is that ProcMon would show me in its advanced output that there is a different process, but there is no. I am fully aware that the reason for sharing violation is typically an open handle - usually by a different process. Although this is running on an ESX server with Deep Security by Trend Micro, the folders are explicitly excluded from AV check.
#Sharing violation software#
Is there any chance to dig deeper and find the cause of this problem?ĪV software can be ruled out. However, the fix cannot be installed on Window Server 2008 R2 (error during installation).
#Sharing violation windows#
There is a KB article that referes to a similar issue and a fix for Windows Server 2008 R2: Last action before ProcMon shows the sharing violation succeeds: Our service was able to open and close the file shortly before the problem occurs. Running ProcMon on the application server (on a different day):ĭetail Desired Access: Generic Read, Dis, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: None, AllocationSize: n/aĪccording to ProcMon there is no other process on any of the servers accessing the file around the time the problem occurs. Sysinternal’s Process Monitor on the file server shows this:ĭetail Desired Access: Generic Read, Dis, Options: Non-Directory File, Complete If Oplocked, Attributes: N, ShareMode: None, AllocationSize: n/a, Impersonating: S-1-5-21-2753595274-792687809-3808857278-4148 The shared file resides on a dedicated Windows 2008 R2 file server, our service runs on a different application server, also under Windows 2008 R2 server. Win32 Error: CreateFile of document file failed. When running on Windows Server 2008 R2, sometimes our service encounters the following problem accessing a file: