move Error 101
Hi DF,
I try to move files (no renaming method, only move) but receive an Error 101.
Output folder: /Volumes/Foto/Original/Diverse Orte/2025.07.31_Do Stift Admont/<Img DateCreate:yyyy.mm.dd> <Substr:1:2> NEF
Folder is created correctly by Advanced Renamer.
But move ends in Error 101.
Any suggestions to solve?
Alexander
I try to move files (no renaming method, only move) but receive an Error 101.
Output folder: /Volumes/Foto/Original/Diverse Orte/2025.07.31_Do Stift Admont/<Img DateCreate:yyyy.mm.dd> <Substr:1:2> NEF
Folder is created correctly by Advanced Renamer.
But move ends in Error 101.
Any suggestions to solve?
Alexander
Hi Alexander,
I played around with this and found that if there's a space after "NEF" the folders are made but the files aren't moved (error 101); so make sure there's not a trailing space in your "Output folder:" field.
If not try changing the forward slashes to backslashes, then simplifying the Output folder: directory structure. Maybe just, i.e., assuming drive c:
Output folder: c:\test\<Img DateCreate:yyyy.mm.dd> <Substr:1:2> NEF\
If that works I'd undo and start adding back the original folder structure, one subfolder at a time, undo-ing each success before adding another subfolder. If it fails before the final step that may give an indication of where the problem lies. If the original simplified structure fails then there's some problem in creating that specific end folder; you might try creating a simplified end folder structure an THEN using rename batch mode to change the folder name to what you want.
These are all just suggestions with very little information; hopefully something here will help. If not I'd suggest contacting Kim directly through the support link above.
Good luck my friend!
DF
I played around with this and found that if there's a space after "NEF" the folders are made but the files aren't moved (error 101); so make sure there's not a trailing space in your "Output folder:" field.
If not try changing the forward slashes to backslashes, then simplifying the Output folder: directory structure. Maybe just, i.e., assuming drive c:
Output folder: c:\test\<Img DateCreate:yyyy.mm.dd> <Substr:1:2> NEF\
If that works I'd undo and start adding back the original folder structure, one subfolder at a time, undo-ing each success before adding another subfolder. If it fails before the final step that may give an indication of where the problem lies. If the original simplified structure fails then there's some problem in creating that specific end folder; you might try creating a simplified end folder structure an THEN using rename batch mode to change the folder name to what you want.
These are all just suggestions with very little information; hopefully something here will help. If not I'd suggest contacting Kim directly through the support link above.
Good luck my friend!
DF
Reply to #1:
You get the error 101 when the operating system cannot move the file. There can be many reasons why, such as the file being in use.
Since you are moving to a subfolder of /Volumes I assume you are using mac. What is Foto? Is that a USB device or something? Moving files between devices with Advanced Renamer is not recommended, and Windows will actually prevent this. Have you tried to copy the files instead? Does the move work when moving to a folder on the same device?
You get the error 101 when the operating system cannot move the file. There can be many reasons why, such as the file being in use.
Since you are moving to a subfolder of /Volumes I assume you are using mac. What is Foto? Is that a USB device or something? Moving files between devices with Advanced Renamer is not recommended, and Windows will actually prevent this. Have you tried to copy the files instead? Does the move work when moving to a folder on the same device?
Reply to #3:
Ah, so it's a restriction in Windows that prevents moving files to other drives! Good to know. Is that a UAC thing?
Ah, so it's a restriction in Windows that prevents moving files to other drives! Good to know. Is that a UAC thing?
Sorry for too less information.
I'm working on MAC.
There is no space after NEF and also an added "/" doesn't change the error
"/Volumes/Foto/Original/Kopenhagen - 2025.06/<Img DateCreate:yyyy.mm.dd>_So Z8 NEF/"
The directory is created always very well, therefore write permission is available.
"/Volumes/Foto" is a SSD direct connected to MAC.
Error 101 also happens when folder is available.
Copy is working without errors. :-) Move -> Error 101 :-(
Why is move not working?
(The only reason for this job is to spread after vacation all photos from SSD to folder (Date Camera NEF, Date Camera JPG)
What data can I gather to identify the root cause of the problem?
Best, Alexander
I'm working on MAC.
There is no space after NEF and also an added "/" doesn't change the error
"/Volumes/Foto/Original/Kopenhagen - 2025.06/<Img DateCreate:yyyy.mm.dd>_So Z8 NEF/"
The directory is created always very well, therefore write permission is available.
"/Volumes/Foto" is a SSD direct connected to MAC.
Error 101 also happens when folder is available.
Copy is working without errors. :-) Move -> Error 101 :-(
Why is move not working?
(The only reason for this job is to spread after vacation all photos from SSD to folder (Date Camera NEF, Date Camera JPG)
What data can I gather to identify the root cause of the problem?
Best, Alexander
Reply to #4:
When you move within the same volume, the file data isn't affected, only the file table is updated. When moving to another volume, the system will copy the file and then delete the original. That is usually not a problem when doing it manually, but as part of a batch process it has some risks attached. If something goes wrong, it is not as easy to clean up afterwards. When moving within the same volume, the operation is atomic, but between volumes it is not. That is why I have chosen not to support it.
When you move within the same volume, the file data isn't affected, only the file table is updated. When moving to another volume, the system will copy the file and then delete the original. That is usually not a problem when doing it manually, but as part of a batch process it has some risks attached. If something goes wrong, it is not as easy to clean up afterwards. When moving within the same volume, the operation is atomic, but between volumes it is not. That is why I have chosen not to support it.
Reply to #6:
Hello Kim, so „Error 101“ is meant to be interpreted as „not allowed“? Is that correct?
Hello Kim, so „Error 101“ is meant to be interpreted as „not allowed“? Is that correct?
Reply to #7:
The program will make all kinds of checks before performing the file operation, like checking if the file exists and the new filename and location is valid. If every check goes fine but the operating system still fails to perform the file operation you will get this error. It is the OS that says the operation is not allowed or cannot be performed for other reasons.
The program will make all kinds of checks before performing the file operation, like checking if the file exists and the new filename and location is valid. If every check goes fine but the operating system still fails to perform the file operation you will get this error. It is the OS that says the operation is not allowed or cannot be performed for other reasons.