"Jenkins" File not found error after update to TI2021
About a week ago I implemented a Drive/Volume Backup for my system drive c:. For a couple of days it went well with this as the usual report:
2020-10-22T00:00:13:793+02:00 15480 I00000000: -----
2020-10-22T00:00:13:793+02:00 15480 I00000000: ATI Demon started. Version: 24.6.1.25700.
2020-10-22T00:00:13:859+02:00 15480 I00640000: Attribute für Backup-Reservekopie: format tib; need_reserve_backup_copy false;
2020-10-22T00:00:13:860+02:00 15480 I00640002: Aktion Samsung SSD 750 EVO 500GB MAT01B6Q wurde per Planung gestartet.
2020-10-22T00:00:14:016+02:00 15480 I00640000: Attribute für Backup-Reservekopie: format tib; need_reserve_backup_copy false;
2020-10-22T00:00:14:017+02:00 15480 I013C0000: Aktion: Backup
2020-10-22T00:00:14:018+02:00 15480 I0064000B: Priorität geändert in 'Niedrig'
2020-10-22T00:02:51:391+02:00 15480 I013C0006: Aktion erfolgreich.
With the update from TI2020 to TI2021 on 25th Oct an additional error (error opening file) occurs:
2020-10-26T00:00:14:028+01:00 17420 I00000000: -----
2020-10-26T00:00:14:028+01:00 17420 I00000000: ATI Demon started. Version: 25.5.1.32010.
2020-10-26T00:00:14:100+01:00 17420 I00640000: Attribute für Backup-Reservekopie: format tib; need_reserve_backup_copy false;
2020-10-26T00:00:14:101+01:00 17420 I00640002: Aktion Samsung SSD 750 EVO 500GB MAT01B6Q wurde per Planung gestartet.
2020-10-26T00:00:14:253+01:00 17420 I00640000: Attribute für Backup-Reservekopie: format tib; need_reserve_backup_copy false;
2020-10-26T00:00:14:254+01:00 17420 I013C0000: Aktion: Backup
2020-10-26T00:00:14:257+01:00 17420 I0064000B: Priorität geändert in 'Niedrig'
2020-10-26T00:04:10:845+01:00 17420 W00000000: Error 0x40007: Fehler beim Öffnen der Datei.
| line: 0xf35f747b3b21fad4
| Datei: c:\jenkins_agent\workspace\ati-main-win\787\core\file\windows\winnt_dir.cpp:971
| Funktion: winnt_dir::OpenWin32Dir
| line: 0xf35f747b3b21fad4, c:\jenkins_agent\workspace\ati-main-win\787\core\file\windows\winnt_dir.cpp:971, winnt_dir::OpenWin32Dir
| $module: ti_demon_vs_32010
2020-10-26T00:04:10:960+01:00 17420 I013C0006: Aktion erfolgreich.
Nevertheless the last line states a successful action. But errors are never good. What is this and how can I resolve it for a backup without errors? Checking the file system reveals that there isn't even a c:\jenkins_agent\ directory. As said this started since I updated from 2020 to 2021
So what's going on here?
Best
Philipp


- Log in to post comments

I'm seeing this same type of thing in the Emailed log file, but then it says that "the operation was successful". If I do a "Recovery" and look at the available files, the files I expect to be in the backup seem to be there. However, like the OP, I don't like a bunch of errors showing up.
| trace level: error | line: 0x1d8eab676a3f6abc | file: c:\jenkins_agent\workspace\ati-main-win\787\products\imager\archive\impl\operations\archive_message_callback.cpp:1171 | function: TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback | line: 0x1d8eab676a3f6abc, c:\jenkins_agent\workspace\ati-main-win\787\products\imager\archive\impl\operations\archive_message_callback.cpp:1171, TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback | Path: H:\Acronis Backups\Videos Incremental_inc_b1_s4_v1.tib | $module: ti_demon_vs_32010 | | error 0x40003: Error occurred while writing the file. | line: 0x7ceb2cdc9fb121ae | file: c:\jenkins_agent\workspace\ati-main-win\787\core\file\windows\win32_file.cpp:517 | function: win32_nocache_file::Write | line: 0x7ceb2cdc9fb121ae, c:\jenkins_agent\workspace\ati-main-win\787\core\file\windows\win32_file.cpp:517, win32_nocache_file::Write | function: WriteFileNoCache | $module: ti_demon_vs_32010 | | error 0xfff0: A device which does not exist was specified | line: 0xbd28fdbd64edb8f1 | file: c:\jenkins_agent\workspace\ati-main-win\787\core\common\error.cpp:307 | function: Common::Error::AddWindowsError | line: 0xbd28fdbd64edb8f1, c:\jenkins_agent\workspace\ati-main-win\787\core\common\error.cpp:307, Common::Error::AddWindowsError | code: 0x800701b1 | $module: ti_demon_vs_32010 2020-11-08T14:38:54:570-05:00 11396 I00040003: Error 0x40003: Reattempting the operation. Error: Error occurred while writing the file.. | trace level: information | line: 0x1d8eab676a3f6690 | file: c:\jenkins_agent\workspace\ati-main-win\787\products\imager\archive\impl\operations\archive_message_callback.cpp:103 | function: `anonymous-namespace'::TraceReattemptError | line: 0x1d8eab676a3f6690, c:\jenkins_agent\workspace\ati-main-win\787\products\imager\archive\impl\operations\archive_message_callback.cpp:103, `anonymous-namespace'::TraceReattemptError | $module: ti_demon_vs_32010 | | error 0x40003: Error occurred while writing the file. | line: 0x1d8eab676a3f6abc | file: c:\jenkins_agent\workspace\ati-main-win\787\products\imager\archive\impl\operations\archive_message_callback.cpp:1171 | function: TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback | line: 0x1d8eab676a3f6abc, c:\jenkins_agent\workspace\ati-main-win\787\products\imager\archive\impl\operations\archive_message_callback.cpp:1171, TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback | Path: H:\Acronis Backups\Videos Incremental_inc_b1_s4_v1.tib | $module: ti_demon_vs_32010 | | error 0x40003: Error occurred while writing the file. | line: 0x7ceb2cdc9fb121ae | file: c:\jenkins_agent\workspace\ati-main-win\787\core\file\windows\win32_file.cpp:517 | function: win32_nocache_file::Write | line: 0x7ceb2cdc9fb121ae, c:\jenkins_agent\workspace\ati-main-win\787\core\file\windows\win32_file.cpp:517, win32_nocache_file::Write | function: WriteFileNoCache | $module: ti_demon_vs_32010 | | error 0xfff0: A device which does not exist was specified | line: 0xbd28fdbd64edb8f1 | file: c:\jenkins_agent\workspace\ati-main-win\787\core\common\error.cpp:307 | function: Common::Error::AddWindowsError | line: 0xbd28fdbd64edb8f1, c:\jenkins_agent\workspace\ati-main-win\787\core\common\error.cpp:307, Common::Error::AddWindowsError | code: 0x800701b1 | $module: ti_demon_vs_32010
- Log in to post comments

Walt, if you are seeing errors followed by a successful completion message, then this simply means that the error handling for the task was able to get past the error being reported, but this doesn't change the fact that there were errors encountered.
In the error data copied above, the following key lines stand out:
Path: H:\Acronis Backups\Videos Incremental_inc_b1_s4_v1.tib error 0x40003: Error occurred while writing the file. error 0xfff0: A device which does not exist was specified Error 0x40003: Reattempting the operation. Error: Error occurred while writing the file..
It is possible that your H: drive became unavailable temporarily during the backup process due to power settings which allowed it to be 'suspended' due to inactivity, then took a short time to become ready again.
- Log in to post comments

Steve,
I guess that's possible . "H" is a USB 3 external drive. However, I was not backing up ANYTHING from C:, so I have no clue why the error appeared for the noted file.
I also observed that there are two backup files created: Videos Incremental_inc_b1_s4_v1.tib and Videos Incremental_inc_b1_s4_v2.tib. I don't normally see the "v2" file. The "v2" file is MUCH larger than the "v1" file.
As I said, when I started "Recovery", it indicated that the files I expected to be backed up were there.
One other quirk was that TI told me some crazy amount of time remained (like >8 hours). The backup took only about 25 minutes.
Walt
- Log in to post comments

Walt, the reference to c:\jenkins_agent\ in the logs should be ignored completely, this is not a location on your PC but within the code stream of the application and is used by the developers for tracing purposes.
The v1 and v2 file name suffices do suggest that the backup was interrupted then resumed again, either that or there is a maximum file size set or imposed by the destination media, but given you said v2 was larger than v1, that is not likely.
- Log in to post comments

Hi, Steve,
c:\jenkins_agent\workspace\ati-main-win\787\core\file\windows\winnt_dir.cpp:971 refers to internal Acronis diagnostic trace data and is of no value to users. It is used only by the Acronis developers to debugging their code as far as we understand.The Error 0x40007: Error opening the file. would normally reference the destination backup file that ATI is looking to open at the start of the backup operation.
Please check that the destination file(s) are all present and that the destination drive has not been changed?
thanks for your feedback.
Yes, all destination are present and the destination drive has never been changed. I'm observing this day for day ever since my Update from ATI2020 to ATI2021. Always concluding with the "success" message in the last line. So this seems to be something left behind by the developers in the 2021 update. Any idea when will this be corrected?
It may have no influence on the successful result of the backup but error messages are always ugly and "ignore them" feels not like a resolution.
Are there any infos from Acronis and/or the developers?
Best
Philipp
- Log in to post comments

Philipp, if an error is being reported, as with your log in the initial post, then these lines will be present because of the error. It may be that the destination location is a little slow to respond when ATI checks for the file being used but without seeing the whole log content, this is purely guesswork.
Please submit Feedback direct to Acronis reference the inclusion of these developer messages in user logs.
- Log in to post comments

I'm also getting these errors under the latest update to 2021.
2020-12-01T08:19:19:625-05:00 5396 I00000000: -----
2020-12-01T08:19:19:625-05:00 5396 I00000000: ATI Demon started. Version: 25.6.1.34340.
2020-12-01T08:19:20:919-05:00 5396 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2020-12-01T08:19:20:922-05:00 5396 I00640002: Operation DriveC started by schedule.
2020-12-01T08:19:21:038-05:00 5396 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2020-12-01T08:19:21:039-05:00 5396 I013C0000: Operation: Backup
2020-12-01T08:19:21:040-05:00 5396 I0064000B: Priority changed to Low.
2020-12-01T08:19:21:089-05:00 5396 E00000000: Error 0x40007: Error occurred while opening the file.
| line: 0xf35f747b3b21fad4
| file: c:\jenkins_agent\workspace\ati-main-win\1022\core\file\windows\winnt_dir.cpp:971
| function: winnt_dir::OpenWin32Dir
| line: 0xf35f747b3b21fad4, c:\jenkins_agent\workspace\ati-main-win\1022\core\file\windows\winnt_dir.cpp:971, winnt_dir::OpenWin32Dir
| $module: ti_demon_vs_34340
2020-12-01T09:29:21:404-05:00 5396 I013C0006: Operation has succeeded.
--------------------------------------------------------
2020-11-29T23:00:00:530-05:00 3560 I00000000: -----
2020-11-29T23:00:00:530-05:00 3560 I00000000: ATI Demon started. Version: 25.6.1.34340.
2020-11-29T23:00:00:571-05:00 3560 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2020-11-29T23:00:00:572-05:00 3560 I00640002: Operation DriveE (E) started by schedule.
2020-11-29T23:00:00:602-05:00 3560 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2020-11-29T23:00:00:603-05:00 3560 I013C0000: Operation: Backup
2020-11-29T23:00:00:604-05:00 3560 I0064000B: Priority changed to Low.
2020-11-29T23:00:00:623-05:00 3560 E00000000: Error 0x40007: Error occurred while opening the file.
| line: 0xf35f747b3b21fad4
| file: c:\jenkins_agent\workspace\ati-main-win\1022\core\file\windows\winnt_dir.cpp:971
| function: winnt_dir::OpenWin32Dir
| line: 0xf35f747b3b21fad4, c:\jenkins_agent\workspace\ati-main-win\1022\core\file\windows\winnt_dir.cpp:971, winnt_dir::OpenWin32Dir
| $module: ti_demon_vs_34340
2020-11-29T23:07:41:328-05:00 3560 I013C0006: Operation has succeeded.
------------------------------------------
as the others have mentioned it seems like the backup is working, but the error logs in the e-mail notifications are not desirable.
I'm backing up to an NAS shared folder.
- Log in to post comments

The last backup I ran did not produce these errors. I have upgraded to the latest build. To he honest, I don't know if the backup was before or after the upgrade (too many things for my old brain). In any case, I'm no longer seeing these.
- Log in to post comments