Salta al contenuto principale

'Error 0x40007: Error occurred while opening the file' but I can't figure out what file

Thread solved

I am running Acronis True Image 2021 v25,6,1,35860 on a Win 10 PC.

It is backing up to a Synology NAS.

Every time the backup runs I get this sort of log:

2021-03-23T22:05:00:785-07:00 18384 I00000000: -----
2021-03-23T22:05:00:785-07:00 18384 I00000000: ATI Demon started. Version: 25.6.1.35860.
2021-03-23T22:05:01:096-07:00 18384 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false; 
2021-03-23T22:05:01:100-07:00 18384 I00640002: Operation XXX started by schedule.
2021-03-23T22:05:01:198-07:00 18384 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false; 
2021-03-23T22:05:01:201-07:00 18384 I013C0000: Operation: Backup
2021-03-23T22:05:01:207-07:00 18384 I0064000B: Priority changed to Low.
2021-03-23T22:05:15:601-07:00 18384 I00010400: Child process has exited with code '0'.
2021-03-23T22:05:15:601-07:00 18384 I00640086: Execution of user command succeeded: ping
2021-03-23T22:05:15:652-07:00 18384 E00000000: Error 0x40007: Error occurred while opening the file.
| line: 0xf35f747b3b21fad4
| file: c:\jenkins_agent\workspace\ati-main-win\1173\core\file\windows\winnt_dir.cpp:971
| function: winnt_dir::OpenWin32Dir
| line: 0xf35f747b3b21fad4, c:\jenkins_agent\workspace\ati-main-win\1173\core\file\windows\winnt_dir.cpp:971, winnt_dir::OpenWin32Dir
| $module: ti_demon_vs_35860
2021-03-23T22:28:34:377-07:00 18384 I013C0006: Operation has succeeded.
 

The backup succeeds but I get the 0x40007 error and I can't see what file it is having problems with.

I thought it might be a problem with the NAS taking too long to wake up, so I added a set of pings to wake the NAS first, and this seems to be working, but I still get the error message.

Any thoughts ?

Nick

0 Users found this helpful

Nick, welcome to these public User Forums.

Your log shows that you are still using ATI 2021 Update #3 build 35860.

Please update to build #39184 where this error looks to be resolved for backups to NAS destinations.