Skip to main content

ATI 2019 - Error 0x40011: The specified file does not exist

Thread solved

I have been using Acronis backup since version 8 and have been satisfied until now with 2019 version.

Have searched the forum but no proposed solution has worked for me.

I have full backups on external USB drives. The USB dives all have static drive letters.

All drives (internal AND external) are formatted NTFS.

Tried to do differential backups yesterday and met the “specified file does not exist” error message. Clicking on “Retry” does nothing but return the error message.

Same thing happens when I attempt incremental backup.

The only backup scheme that works is FULL backup.

Any help appreciated.

Thanks in advance

0 Users found this helpful

Gar, welcome to these public User Forums.

Sorry but more information is needed to try to understand why you are seeing an issue with your differential & incremental backups?

Please confirm that you have the latest ATI 2019 build 17750 version - this can be checked on the Account page in the ATI GUI.

Next, please post copies of the logs created by your backup tasks - use the MVP Log Viewer tool to access the logs.

MVP Log Viewer & Custom ATI PE Builder available from Community Tools page.

Log Viewer

A simple application that allows viewing Acronis True Image service logs in a graphical user interface.

  1. Download the tool.
  2. Double-click to run it.
  3. Using date and time, find the log you want to check:

Howdy Steve

Thanks for the reply.

Yes, I have the latest ATI 2019 build 17750 version.

I thought the problem may have been my incorrectly setting up backup scheme. So I stuck with the default incremental scheme.

Same problem. Log files attached.

 

Attachment Size
503410-169274.log 4.71 KB
503410-169277.log 4.83 KB
503410-169280.log 4.84 KB
503410-169283.log 4.52 KB

Gar, the log files show that the backup archive files are being created successfully but that there is a problem with automatic cleanup which may be caused by a corrupted task script file.

I would recommend trying creating a new backup task for the same source data and using a different name with the same settings and see if this then works correctly?

Gar,

Just FYI, but if all drives are static letters, but anything new gets plugged in (say a new drive), it will pick up the next available drive letter automatically from Windows and that can change the static letter of another drive when plugged in if they both have the same assigned letter.

Also, anytime a disks partition scheme is modified (almost always with a major Windows update since it builds a new recovery partition), the source or destination in your backup task may no longer match up... technically it will look the same, but under the hood, the disk signature has changed.  In those cases, sometimes the fix is simply re-selecting the source and destination (again, even if it looks exactly the same in the GUI) and running the backup right after to ensure it commits the change and saves it to the task.

Thanks for the reminder Bobbo_3C0X1

I have a dedicated drive-letter system that ensures no two drives have same letter. Only changes when drives are "retired" then all relevant software is "notified" so to speak.

I appreciate the heads up on the disk partition scheme stuff.

These issues don't however, apply in this case.

Trying out Steve's suggestion.

Cheers

Steve Smith wrote:

Gar, the log files show that the backup archive files are being created successfully but that there is a problem with automatic cleanup which may be caused by a corrupted task script file.

I would recommend trying creating a new backup task for the same source data and using a different name with the same settings and see if this then works correctly?

Steve

Tried out but ATI 2019 returned error of:

"Failed to open data stream.Try to remove from the list, add it again by clicking "Add existing back up" and recreate the backup settings."

Logs attached.

Thanks

Attachment Size
503561-169354.log 4.75 KB
503561-169357.log 4.87 KB
503561-169360.log 4.87 KB
503561-169363.log 4.87 KB
503561-169366.log 4.87 KB
503561-169369.log 4.85 KB

Gar, thanks for the new logs which again show a series of successful backup archives being created on your U: drive but then encountering the error "Error 0x1e5000e: Failed to open data stream." when performing any additional actions configured for the task.

I would normally expect to see a reference to either validation or consolidation in the log but the error occurs before such reference is written.

Please can you provide details of the options you have set for Backup Scheme and if you have Validation set to run?

If you have enabled validation, then please try disabling this option on the Advanced options page and see if the same error is thrown?

Steve

Options set for backup scheme as follows:

Method = Incremental

Create a full version after every 7 incremental versions

Delete version chains older than 183 days

Automatic clean-up is on

Validation is not set

I also tried the same incremental backup scheme with smaller backup of another folder on different drives and still have issues.

Setting up with the default incremental backup scheme I get the first backup as full then as soon as its done ATI 2019 tries to do 6 incremental backups. Each time returning error message: Error 0x1e5000e: Failed to open data stream.

Logs attached

Later today I am going to uninstall ATI 2019 and re-install. Just in case there's an issue on that level.

Will feedback on that.

Really appreciate the help thus far.

Attachment Size
503628-169384.log 3.39 KB
503628-169387.log 3.41 KB
503628-169390.log 3.41 KB
503628-169393.log 3.41 KB
503628-169396.log 3.42 KB
503628-169399.log 3.42 KB

SOLVED

Here’s how.

I fully uninstalled ATI 2019 and re-downloaded the .exe file from my account on Acronis site.

  1.  Re-installed
  2. Checked the default exclusions list and noticed some Acronis files extensions on the list…namely *.tib and *.tib.metadata.
  3. Unchecked the “Exclude system files” box

Set incremental backups for different drives and folders and all worked as they should.

Will experiment with differential backups and post back here in a day or two.

Thanks a millions Steve.

Also thanks to Bobbo_3C0X1 for the reminders and heads-up.

Gar, great to hear this issue is resolved by the uninstall / reinstall of ATI - many thanks for sharing your feedback!

An update as promised... I have tried various backup schemes and all seem to be working as expected.

However, today while attempting to use mobile backup from my Android phone and tablet I met the "Your subscription has expired" message. I have a perpetual license for ATI 2019. And my mobile backups are NOT in Acronis cloud. I store them on my desktop.

Wondering if this may be connected to re-installation I had to do to sort out the previous issue?

I submitted a ticket to Acronis support on the matter. Will feedback here accordingly.

 

Gar, see forum topic:Service unavailable due to maintenance or the subscription has expired - where this has been flagged by Ekaterina back to Acronis RnD as an issue.

If you have access to the ATI 2020 Beta Forums, I also reported the same issue in forum topic: Bug: Existing mobile backup connection 'Unauthorised' after clean install.

I was able to resolve the issue by selecting to create a new backup from the mobile app and selecting the same destination laptop computer and scanning the QR code etc.

Cheers Steve

I set up new mobile backup and it worked on both Android devices.

I was still getting the error message: “Check your account credentials or activate subscription.”  But I ignored the message and set up fresh mobile backup by scanning QR code etc.

Does seem to be a bug somewhere!

Thanks again for the guidance.

 

Glad to hear the suggestion worked ok for you, thanks for the update.