Skip to main content

Backup Failing with "Cannot open the backup"

Thread needs solution

Hi, I suddenly started seeing the following error trace with my backup:

2017-03-27 01:03:05:107 39280 D00000000: Error 0x0

| trace level: debug

| line: 0x0

| line: 0x0

2017-03-27 01:03:05:401 39280 E000B03E9: Error 0xb03e9: Cannot open the backup.

| trace level: error

| line: 0x65e40aa0b486f50

| file: k:\8029\products\imager\archive\impl\operations\archive_operation_backup.cpp:191

| function: TrueImage::Archive::BackupArchiveOperationImpl::Prepare

| line: 0x65e40aa0b486f50, k:\8029\products\imager\archive\impl\operations\archive_operation_backup.cpp:191, TrueImage::Archive::BackupArchiveOperationImpl::Prepare

| $module: ti_demon_vs_8029

|

| error 0x70027: Encryption has failed.
| line: 0x33004b92f00b77b1

| file: k:\8029\resizer\backup\imglist_persist.cpp:360

| function: resizer::ImageListReader::LoadImageList

| line: 0x33004b92f00b77b1, k:\8029\resizer\backup\imglist_persist.cpp:360, resizer::ImageListReader::LoadImageList

| $module: ti_demon_vs_8029

|

| error 0x4000d: The file is corrupted.

| line: 0x55daeaa529552e1c

| file: k:\8029\backup\crypt\recover.cpp:133

| function: `anonymous-namespace'::Md5CryptProcessor::Init

| line: 0x55daeaa529552e1c, k:\8029\backup\crypt\recover.cpp:133, `anonymous-namespace'::Md5CryptProcessor::Init

| $module: ti_demon_vs_8029

When I bring up ATI it shows a problem with the connection to the NAS device. My credentials test works fine and when I attempt to connect (from ATI) manually it indicates it can't open the backup file. I verified from Windows Explorer that the backup file is present and appears to be the proper size (looks to be the first file of a new chain).

What's going on here?

TIA for any help.

0 Users found this helpful

The latest MVP Log Viewer will hide all the lines starting with | as these are only really intended for the Acronis developers and have little meaning to us mere human readers!

I would recommend trying to do a Validation for your backup task that produced this log and see how this goes and whether it too gives any error messages?  

The lines that would concern me are:

| error 0x70027: Encryption has failed.

| error 0x4000d: The file is corrupted.