Direkt zum Inhalt

E0004000D: Error 0x4000d: The file is corrupted.

Thread needs solution

Does anyone have any idea what the subject error message means, and how to fix it?  I received it about 3 seconds after an incremental  backup job started, and then the job ends.  What file is corrupted?  One of the files  being backed up? The tibx file? 

There is link that says "Click here for more information" but that takes me to the Acronis Support Center page that says "There is no information about this error available now"  

 

I've seen this before and had to clone the backup job and start over with a new full backup. 

0 Users found this helpful

What version / build of ATI are you using here?  Is it ATI 2021 build #32010 (latest) as per this forum or something older?

There is a new log viewer tool that has now been made available by Acronis via the Community Tools KB page.  See the link in my signature for the MVP Assistant tool.

If you have Disks & Partitions backups created on ATI 2020 or later using .tibx files, then look in the Backup Worker logs.

If you have Files & Folders backups using .tib files (or Disk backup using same) then look in the Demon logs.

The logs are the best place to try to identify which file is being reported as being corrupt?

Yes I have the latest version. , Yes  I have the log viewer. But how do I display the "Backup Worker" logs?  I click on "Log Type"  I get a long list, but none say anything close to "Backup Worker" I clicked on the Help button, but that shows text that doesn't even fit inside the display box.

It sounds like your are suing the original log viewer. You need the new MVP Assistant Tool.

 

Well this is strange.  I installed the MVP Assistant Tool and found the Backup Worker logs. Thanks.

I have 2 backup jobs. One is a Disk and Partition for my C drive.  The other is a Files & Folders for an external USB drive.   It’s the C drive (Disk & Partition) backup that failed. 

The log says the archive it was trying to access was the tib File for the external (Files and Folders) job. I can see that if ATI was expecting a tibx file and found a tib file, it would get confused.  How the backup destination changed is mystery.

 

 

Difficult to say why this type of 'confusion' happens but the ways to resolve it depend on what you want to do?

You could take the option to Delete the 2 backup jobs, just removing the settings only, then use the option to Add existing backup and select the most recent backup file for the task.  The added task would need to be reconfigured and the task name edited (if adding .tib tasks) to remove the extra file name characters.

The second option would be doing the same initial Delete / remove settings as above, but then create two new backup tasks to new destination folders and using new names.

Note: after removing the task & settings, you could do some 'pruning' of your backup files to make more space on your storage drive if needed.