True Image 2015 - "The Specified File Does Not Exist"? Help, Please!
I have been running True Image for many years. I currently have the 2015 edition running.
I noticed that it stop doing automated backups in November. Why, I don't know. I noticed that when I tried to do a manual backup I got the mesage "The Specified File Does Not Exist". I also noticed there was an update to the 2015 edition so I did the update bringing it to the latest version, build 6613. No change. I still get that message. If I say Ignore, it counts up to 387.9MB processed that then stops. All I can do is quit the backup.
How do I fix this?
I am backing up to an external USB drive where there is enough room. I am using Windows 8.1.
All help greatly appreciated!
Thanks... Paul
Attachment | Size |
---|---|
acronis_error_1.jpg | 65.32 KB |
acronis_error_2.jpg | 48.7 KB |

- Log in to post comments

I still need to try your suggestions. The weird thing is that it has run for more than 6 months without any issues. Then all of a sudden it decided to quit! Without even a warning. If I hadn't checked I still wouldn't know.
---Paul
- Log in to post comments

Paul,
The most frequent cause of your problem is that the user has inserted a flash drive or some device which has consumed the original drive letter and a new drive letter has been assigned to the storage disk. So, the first place to look is that the storage disk to see if the correct drive letter is still assigned.
Next place to look would be to RIGHT click on the task name on your main menu. There should be an option "open location".
You can click on this option to open into the storage folder and see if all the S# (slice #) are still present associated with the last full backup B#.
Another place to look is at the log file found at C:\ProgramData\Acronis\TrueImageHome\Logs
Cause of the failure can often be found listed there.
Look at the log file named "service" for your November last backup. This log file can be opened in Notepad.
If you have updated to a newer version since the last backup created, your best solution is probably to create a new backup task with a new name pointing to a new storage folder--assuming that sufficient storage space exists for new backups. You should try all the steps above to find the cause so you can perhaps avoid future issues with the same task.
This link may also be of interest.
http://forum.acronis.com/forum/64640
The backup task also offers email notification for the success/failure of your backups. This should be configured into any new task creation.
- Log in to post comments