"System Can't Find Path Specified" Error During Backup

kado897 said:

Glad it's sorted.
It threw me the first time it happened to me. I had set it up to backup specific folders and I had deleted one of these. Apparently when you do this backup gets very upset rather than just handling it. If it happens again you can get a clue I think by pressing more details or something like that and it tells you the folders that are causing the problem.

No, in my case pressing more details didn't tell me which folders. All it said was "can't find path specified". This time when I did the backup reconfigure, I unchecked the AppData folder, as I read someplace that this could cause problems. Anyway, I got a successful backup and am happy...........

kado897 said:

Durango said:

kado897 said:

Glad it's sorted.
It threw me the first time it happened to me. I had set it up to backup specific folders and I had deleted one of these. Apparently when you do this backup gets very upset rather than just handling it. If it happens again you can get a clue I think by pressing more details or something like that and it tells you the folders that are causing the problem.

No, in my case pressing more details didn't tell me which folders. All it said was "can't find path specified". This time when I did the backup reconfigure, I unchecked the AppData folder, as I read someplace that this could cause problems. Anyway, I got a successful backup and am happy...........

I've not heard of that one before but it is very unforgiving of the slightest problem.

After I did the backup reconfigure and got a successful backup, I decided to go back and check the AppData folder and then let Windows choose how to perform the backup (rather than me selecting which folders). This also resulted in a successful backup, so I am happy x 2.

MilesAhead said:

You can use this utility to find out if any paths on your system are too long:
TLPD | Free System Administration software downloads at SourceForge.net

Explorer won't let you create a new folder if the total length of the path is too long. But a file created via a program may push the total path length over the limit. By default TLPD searches all drives for paths longer than 200 characters.

I added a few tweaks to the source to enable searching even longer paths by using the "\\?\" prefix. You can get the modified source here:
SourceForge.net: TLPD: Update for Unicode?

But unless you're a sys admin the original binary should be fine for home use.

Hey, thanks. I'll remember that and give it a try.