Hello,
When I copy a bunch of files from my NAS(Drive Y:// to my internal drive (Drive E://) i very often receive the error message 267 (foldername is not valid). If I try to do this with the explorer there is no issues at all.
How can I resolve this please?
If you click Retry a few times, does it make any progress, or does it remain stuck on the same file?
If I click 'Retry' sometimes it will continue, but most of the times it keeps stuck , even after clicking more then 10 times.
What kind of NAS is it?
The issue is probably with the NAS itself, since it's claiming the path doesn't exist (but it does exist, and works after a retry sometimes, which makes no sense).
A Process Monitor log of what happens when the error message appears (and info on which filepath the error was for) should be able to confirm that, or reveal more details about what's going wrong.
Hello Leo,
sorry for the late reaction, but tried myself some things out. Is it possible it has to do with a buffer or smething? If the error occurs, and i wait a while (few seconds) before i click 'continue , things work fine. Only if i click ammediatly to continue, the error keeps returning. I will try to make this week a log file and hope there is a solution for it.
Btw, it is a Asustore NAS AS1004T
Sounds like files remain in the directory for a moment even though the request to delete them has succeeded and completed.
That can happen if something else has opened a file while allowing it to be deleted. (The delete will succeed, but the file won't actually be gone until the first thing closes it. At least, those are the semantics on Windows itself.) But it might also mean something else is happening on the NAS side. The logs should reveal what it is.
If there are media files in the folder in question and you were inside it before deleting it, it's possible Opus itself has them open to extract metadata from them (depending on which columns etc. are turned on). But it could also be something other than Opus opening the files (e.g. virus scanners, or tools that were operating on the files).
Hello Leo,
I made the logfile today while copiying a whole bunch of files from the NAS to my harddrive and the errors keep occuring. The logfile should be included . I had again different interruptions at 14.56, 14.57, 15.00, 15.01, 15.02, 15.04, 15.05 and 15.08.
Logfile.zip (33.2 MB)
Would it be possible to save the log in the Native Process Monitor Format (.PML) format the guide specifies? The CSV format is missing lots of essential information.
We also need to know the paths of the files which had the errors so we can locate the right entries in the log. Timestamps can also help locate the right moment that file was accessed, but we need to know the path as well to be able to find the right thing. (There are often thousands of events per minute to look through.)