We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
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?
I'm having the same issue, and again using Version 5.26.2.0
I have now activated the "File & Project Handling" setting to Auto save and create a backup files (.BAK). All this is in the Edit/Configuration/...
I'm hoping that the backup file will help..... I have yet to determine if this is the case.
Is this a recognised bug with uVersion / arm?
Regards, R.
I have the same problem with my header file using MDK 5.26.2.0. Unless SOMEBODY submit the service ticket with active maintenance service, Keil (Arm) will not consider these issues seriously. (I tried to talk with their chatbot but they do not take any action.)
Hello Rowland,
I have seen some random reports of a similar issue coming in, but we still can't reproduce it. Every instance seems to be slightly different setup.
We assume that the PC is running some other processes in the background e.g. Virus Scanner, Windows Indexing Service, Software Version Control Systems, Onedrive. etc. - that may be causing a conflict.
If you could duplicate this issue in an acceptable time frame, we would be happy if you could make some tests with the Process Monitor from Sysinternals/Microsoft. You could add a filter to a folder where your header files are located (Filter: Path contains .... then Include). You could then start the recording, work with uVision and as soon as the problem shows up, you stop the recording and note the header file name which was reported in the error message. Then you could store the recording, create a support ticket and send it to us.
Kevin,
I have managed to capture the Sharing Violation error and had Sysinterals running.
So, I have a couple of files that may be of interest....
I've managed to compress one of the files to 12Mb, which I may be able to email...
Regards,
Rowland
Dear Kevin From Support,
Do you want these SysInternals log files?
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.
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.