Getting a critical error not to be one
4 posts
• Page 1 of 1
Getting a critical error not to be one
Awhile back I had a thread about runs marked as failures, but I can't find exactly what you suggested for getting around the problem - or what I did at the time. In this case, it's a single error during the past two runs:
---
\Windows\SoftwareDistribution\EventCache\{80795D73-5E72-4BD4-9902-9CA52F1CC853}.bin
Failed to copy from Left : Safe copy failed. Failed to rename temp file: File is locked (I:\Windows\SoftwareDistribution\EventCache\{80795D73-5E72-4BD4-9902-9CA52F1CC853}.bin): The process cannot access the file because it is being used by another process.
---
What can I do to get this reclassified? I looked at the list before OKing the final run sequence, but didn't find this file, although it is easy to miss among so many. Thanks,
---
\Windows\SoftwareDistribution\EventCache\{80795D73-5E72-4BD4-9902-9CA52F1CC853}.bin
Failed to copy from Left : Safe copy failed. Failed to rename temp file: File is locked (I:\Windows\SoftwareDistribution\EventCache\{80795D73-5E72-4BD4-9902-9CA52F1CC853}.bin): The process cannot access the file because it is being used by another process.
---
What can I do to get this reclassified? I looked at the list before OKing the final run sequence, but didn't find this file, although it is easy to miss among so many. Thanks,
- highstream
- Enthusiastic

- Posts: 13
- Joined: Mon Apr 30, 2012 4:50 pm
Re: Getting a critical error not to be one
Your previous question was about re-classifying errors about files it planned to copy having disappeared since the scan, so could not be copied (because they don't now exist). That's a special case.
You can't re-classify the error you just quoted, as it's a failure to copy files - that do exist - because the file on the Destination/Right is in use, so cannot be overwritten. That's a Critical Error in our philosophy.
You can possibly work round it by de-selecting that location from the scope, so the profile doesn't try. Or, if you can figure out what has the file open, close it.
You can't re-classify the error you just quoted, as it's a failure to copy files - that do exist - because the file on the Destination/Right is in use, so cannot be overwritten. That's a Critical Error in our philosophy.
You can possibly work round it by de-selecting that location from the scope, so the profile doesn't try. Or, if you can figure out what has the file open, close it.
- Dave Wilkins
- 2BrightSparks Staff

- Posts: 6963
- Joined: Thu Jan 04, 2007 10:02 am
Re: Getting a critical error not to be one
I finally found the file. It was labeled Missing, Prompt Me. I chose Skip for now and the run then succeeded. Given the message, does that seem a reasonable choice. So far we (two forums) haven't figured out why it's a problem from the backup drive.
- highstream
- Enthusiastic

- Posts: 13
- Joined: Mon Apr 30, 2012 4:50 pm
Re: Getting a critical error not to be one
Selecting Skip will only work for that particular run. You may want to consider Skip And Exclude (or, go into the Choose dialog and de-select (Exclude) it manually first, which is what I meant: that way, you won't need to be in attendance when the profile runs next)
Figuring out why the file on the Right is in use/locked (according to Windows) is not something we can do for you. It's sometimes related to AV software scanning things, but could ba a lot of things.
Figuring out why the file on the Right is in use/locked (according to Windows) is not something we can do for you. It's sometimes related to AV software scanning things, but could ba a lot of things.
- Dave Wilkins
- 2BrightSparks Staff

- Posts: 6963
- Joined: Thu Jan 04, 2007 10:02 am
4 posts
• Page 1 of 1
Return to SyncBackSE V6/V5 (commercial)
Who is online
Users browsing this forum: No registered users and 2 guests