Skip to main content

Suddenly, 2010 backup fails "specified file does not exist"

Thread needs solution

Vista 32-bit. ATI Home 2010, build 5055.

I've done a lot of searching here and elsewhere, and seen similar error messages, but they don't seem to be exactly what I have happening. My daily incremental file backup has suddenly started failing with this "specified file does not exist" message. It lists the path and file and it's correct, that file no longer exists in that location, if it ever did.

After I click "ignore" the backup continues and apparently runs successfully. But it now hangs on this error every day. It's backing up files and folders to a USB drive, which is in fine working order. Again, the backup runs after I ignore this file. I haven't made any changes in configuration, though I did delete and move a lot of large files around.

Saludos, Mig

0 Users found this helpful

Check and see if your incrementals are all in the correct date or name order.

If you see any that either have long string of letters and numbers either by itself or with the correct file name attached, this may be the problem.

Have you manually deleted any of the incrementals via Windows Explorer or other file manger?

Do you use consolidation?

Nothing like that. Just a nice orderly set of daily .tib files going back to October. Dates and file names are all good. I've never deleted any of them.

I don't know if it uses consolidation, but I don't believe so. I don't remember selected it either way.

Saludos, Mig

I had that happening to me too last week. The log file referred to a missing file that never ever existed. I don't know why it was suddenly deciding to look for this TIB file that I have never seen in my collection (and I got tons of free space available).

I ended up having to delete the backup task and create a new one. Now it works as expected.

Every year, we hear of things or softwares that have problems with Febuary and the leap year or lack thereof (think of the Zune or PS3). I've grown weary of that date. I wonder if ATI2010 had an issue with it.