Hello,
I am currently using a µvision V5.26.2.0 and sometimes I can't save source file ( h , cpp ).
When it happened the pop ups window showing this message:
"Encountered a sharing violation while accessing {Path to me source file}"
The only one way that can change this behavior is to restart the µvision IDE.
Can I do something else?
Experiencing the same issue. Windows 10, uVision 5.26.2.0, only .h files affected. Running as admin seems to fix it, at least I haven't experienced it again (yet)...
Same situation, I have tried running under Admin, but this did not solve the problem.
Regards, R.
Restarting the application makes it go away, because Windows closes all handles owned by the application/task as it tears it down.
The issue is the app fails to CloseHandle() on the file, likely a Mapped View, and owned by the Pager, perhaps a premature exit of a function which might otherwise have closed it.
Don't think Admin makes much difference in this, as it's effectively owned by the Kernel.
Would agree it is mostly likely to be seen in .H due to the dependency changes those would make.
Other theory is task doing dependency checking wins race condition with task saving file.
Dear Kevin From Support,
Do you want these SysInternals log files?
Regards,
Rowland
I've seen these sharing violations since upgrading to uVision 5.26.2. I'm running a Windows 10 machine with Trend Micro antivirus, which is managed centrally.
I ran Process Monitor. It seems to show a sharing violation between uv4.exe and tmbmsrv.exe.
3:23:27.3855127 PM UV4.exe 2832 QueryNetworkOpenInformationFile C:\Users\u100137\path\to\file.h SUCCESS CreationTime: 10/10/2018 8:39:57 AM, LastAccessTime: 10/11/2018 12:38:53 PM, LastWriteTime: 11/6/2018 12:33:02 PM, ChangeTime: 11/6/2018 12:33:02 PM, AllocationSize: 32768, EndOfFile: 31682, FileAttributes: A 3:23:27.3855278 PM UV4.exe 2832 CloseFile C:\Users\u100137\path\to\file.h SUCCESS 3:23:27.3857638 PM UV4.exe 2832 CreateFile C:\Users\u100137\path\to\file.h SHARING VIOLATION Desired Access: Generic Write, Read Attributes, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: None, AllocationSize: n/a 3:23:27.3860568 PM TMBMSRV.exe 6288 CreateFile C:\Users\u100137\path\to\file.h SUCCESS Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened 3:23:27.3860897 PM TMBMSRV.exe 6288 QueryNetworkOpenInformationFile C:\Users\u100137\path\to\file.h SUCCESS CreationTime: 10/10/2018 8:39:57 AM, LastAccessTime: 10/11/2018 12:38:53 PM, LastWriteTime: 11/6/2018 12:33:02 PM, ChangeTime: 11/6/2018 12:33:02 PM, AllocationSize: 32768, EndOfFile: 31682, FileAttributes: A 3:23:27.3861051 PM TMBMSRV.exe 6288 CloseFile C:\Users\u100137\path\to\file.h SUCCESS
Adam,
Have you managed to disable: tmbmsrv.exe and prove that the sharing issue is resolved?
I have Trend Micro antivirus, which is managed centrally too.
for about a week I did not have the issue anymore.. Vague Theory: Micro Soft patch started sharing problem, now with another patch it disappeared?
I have reported this to support. They are working on it (they already had a case opened with the problem). I will get a notice from them once they figure this out I can also confirm that running in admin has no change. I have also just changed my development PC a week ago, the problem also occurs on this fresh installation (all files/projects are local disk, no SVN etc etc)
Afternoon Carsten,
Do you have Trend Micro antivirus installed and tmbmsrv.exe running?
Rowland, nope, none of them. In fact, the workstation right now is just a basic Win10 installation, nothing fancy (yet)
ups, happened again.. so vague theory is false :)
I don't have the ability to disable TrendMicro, even for a short period. I tried killing it from Task Manager and that didn't work. I could try one of the SysInternals tools to really zap it. I suspect it would respawn pretty quickly.
From some of the other comments in this thread, Keil is aware and has a support ticket open. I'm hoping for a fix soon. I think I can always fall back to editing outside Keil, and build/debug in Keil while I wait for the fix.
I'm not using Tread Micro, this is a self-induced resource leak, or race condition.
Oh my has this issue been resolved already?
I m using uVision 5.26.2 and in one of the occasions it destroyed my few hours of work.
How can this destroy hours of work ? In my case, when I get the "sharing violation" I just press CTRL-A and CTRL-C, closes uVision, opens it again (the file that had sharing violation even has the focus after uVision is re-opened) and press CTRL-A and CTRL-V, and all is on track again ?