Skip to main content

Error 0x40019: Error occurred while backing up.

Thread needs solution

My backup job is failing. The error message is not exactly enlightening to the user.

2020-02-11T09:58:46:510-10:00 19440 I00000000: -----
2020-02-11T09:58:46:510-10:00 19440 I00000000: ATI Demon started. Version: 23.5.1.17750.
2020-02-11T09:58:46:528-10:00 19440 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2020-02-11T09:58:46:529-10:00 19440 I00640002: Operation My files started manually.
2020-02-11T09:58:48:816-10:00 19440 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2020-02-11T09:58:48:818-10:00 19440 I013C0000: Operation: Backup
2020-02-11T09:58:48:819-10:00 19440 I0064000B: Priority changed to Low.
2020-02-11T09:59:03:695-10:00 19440 I000B03F0: Create Backup Archive From:      C:\Users\username\Desktop\
D:\Data\
C:\Users\username\AppData\Local\MediaMonkey\
C:\Users\username\AppData\Roaming\MediaMonkey\
C:\Users\username\AppData\Local\Packages\Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe\
 To file:       "My files_inc_b22_s5_v1.tib" Compression:       Normal Exclude: System files 
2020-02-11T09:59:11:082-10:00 19440 E00040019: Error 0x40019: Error occurred while backing up.
| trace level: error
| line: 0xce542e14da203c26
| file: c:\bs_hudson\workspace\790\archive\backuper.cpp:1031
| function: Archive::BackupOperation::Execute
| line: 0xce542e14da203c26, c:\bs_hudson\workspace\790\archive\backuper.cpp:1031, Archive::BackupOperation::Execute
| $module: ti_demon_vs_17750
|
| error 0x40003
| line: 0xce542e14da203bdc
| file: c:\bs_hudson\workspace\790\archive\backuper.cpp:957
| function: Archive::BackupOperation::ProcessItems
| line: 0xce542e14da203bdc, c:\bs_hudson\workspace\790\archive\backuper.cpp:957, Archive::BackupOperation::ProcessItems
| $module: ti_demon_vs_17750
|
| error 0x40003
| line: 0xce542e14da2039cd
| file: c:\bs_hudson\workspace\790\archive\backuper.cpp:430
| function: `anonymous-namespace'::BackuperHelper::ProcessTraverser
| line: 0xce542e14da2039cd, c:\bs_hudson\workspace\790\archive\backuper.cpp:430, `anonymous-namespace'::BackuperHelper::ProcessTraverser
| Path: C:/Users/name/AppData/Roaming/MediaMonkey/MediaMonkey.ini
| $module: ti_demon_vs_17750
|
| error 0x4001f: Invalid usage.
| line: 0x35f34aff8801b59b
| file: c:\bs_hudson\workspace\790\archive\data_reader.cpp:562
| function: Archive::ReadBlockItem
| line: 0x35f34aff8801b59b, c:\bs_hudson\workspace\790\archive\data_reader.cpp:562, Archive::ReadBlockItem
| $module: ti_demon_vs_17750
2020-02-11T09:59:17:339-10:00 19440 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bcec0
| file: c:\bs_hudson\workspace\790\products\imager\demon\main.cpp:714
| function: main
| line: 0x9f2c53c72e8bcec0, c:\bs_hudson\workspace\790\products\imager\demon\main.cpp:714, main
| $module: ti_demon_vs_17750

0 Users found this helpful

Your error looks to be directly related to the file: 

C:/Users/name/AppData/Roaming/MediaMonkey/MediaMonkey.ini

Given that you are including AppData files in your backup, it is possible that the MediaMonkey application was processing the same file when the backup was attempted, preventing ATI from working with it?

Understand your comment but that is what the log is showing, so perhaps something else on your computer was locking that file at the time, i.e. perhaps an antivirus scan etc?

Have you retried the same backup again since the error?

I deleted and re-created the job yesterday. It runs the full fine, but the incremental step failed again this morning. Same error almost entirely. Which doesn't give me much confidence in the error logs.

What happens if you manually run the backup?  This seems really unlikely, but maybe there is something locking the file at the time the backup is scheduled.  The full backup may take a long time to get to the problematic file (giving time for the locking task to complete and free the file) but an incr backup gets to the file while it is locked.

Manual gets the same result.

This has been working since I did my Win10 clean install in September after a hardware upgrade. It used to work whether MM was open or not.

The only thing that works is deleting the Full so that it's not creating an incremental. That's phenomenally dumb since 10 seconds before it errors out.

I'll try differential.

Differential executed this morning without an error.

Same folders backed up. I made some minor changes in MediaMonkey, so the config files for that (the DB and .ini) are included in the backup.

It's good that the diff backup worked but I don't understand how a diff would work but an incr would fail (or that a full would work but an incr would fail). My impression is that this has to be a timing problem.  I wouldn't expect anything but MediaMonkey to take exclusive control of the .ini file.

I see that MediaMonkey has a service that will run in the background if enabled.  It has something to do with syncing with external devices.  Do you have that enabled?  I suppose it might lock the .ini file.

The issue would occur after a fresh reboot and my phone was not connected at the time. The background process is likely the DLNA functionality, but as I am not really sure what that is except for streaming across the local network, which I don't do, I can't say more.

Since differential is fine by me I haven't really put any more effort into troubleshooting it.

All I can say at this point is

¯\_(ツ)_/¯