Normal
NAS shouldn't be a problem tough. I have all my songs on a NAS since years.I had a quick look into the code. As we are running into this error, we are aborting the scan.The reason for doing that is that if we have a general error we would loop forever.It might be worse though to implement some kind of counter and only abort if we continue to have such an error without a succsessful access in between.So once you have figured out, which file / folder caused the trouble and you shortened it, the processing on the NAS will continue.You would have had this error also on a local drive, but there you have the drive letter instead of the NAS UNC path and this caused the file name to be shorter than the 260 characters. And therefor it worked,
NAS shouldn't be a problem tough. I have all my songs on a NAS since years.
I had a quick look into the code. As we are running into this error, we are aborting the scan.
The reason for doing that is that if we have a general error we would loop forever.
It might be worse though to implement some kind of counter and only abort if we continue to have such an error without a succsessful access in between.
So once you have figured out, which file / folder caused the trouble and you shortened it, the processing on the NAS will continue.
You would have had this error also on a local drive, but there you have the drive letter instead of the NAS UNC path and this caused the file name to be shorter than the 260 characters. And therefor it worked,
