Mysterious Write Error 0x1e50023 on Full Backup...my solution
I had a very mysterious error that cropped up a couple years ago. I've posted about this before but I have now figured out what to do about it so here is my tale...
On a scheduled full backup which had been working well, it suddenly developed a write error. In my case, the error was Error 0x1e50023: Cannot access backup file \\NAS... \System_full_b41_s1_v11.tib. Please ensure that you entered the correct credentials for the network share.
When this happened, it would repeat attempt 5 times, 30 seconds apart and then fail the backup task. I had turned off the option to repeat on error but it was still doing that.
There was nothing wrong with the credentials.
Note the _v11.tib in the file name, which of course is incorrect. as the file ends in _v1.tib. This symptom has been reported and discussed ad nauseam.
Every time I started the backup task manually it worked perfectly.
Once it started to fail, it would do so often but not every time. This was a weekly full disk backup.
The problem never occurred on my File and Folder backups.
My wife's PC, running ATI 2018 did not have this problem, but after updating hers to ATI 2019 (last year) the issue started there.
Countless times I recreated the backup tasks, but the problem kept coming back.
By looking into the NAS logs, I was able to determine that when the problem occurred True Image was correctly connecting to the NAS. But, it did not actually create the .tib file that it then could not access. So failing to create the file seemed to be the crux of the problem,
After about two years of frustrating attempts and holding my breath every week wonder if the backup would work, and then going in to manually start it, I finally have found an answer and the backups have been running fine for months now.
The solution was that I created a batch file that I run using the Windows Task Scheduler. It was a bit tricky because there are actually four separate backup tasks involved... a weekly and a monthly for each of 2 drives. They run every Monday, but the third Monday of the month it does the Monthly version instead of the Weekly version. The batch file runs the appropriate backup jobs by explicitly calling True Image with the /script option. This requires the script GUID so that means I have to be careful about not changing the backup task which might change the GUID.
I turned off all scheduling of the task within True Image.
My conclusion is that the bug is in the True Image Scheduler. I tried every way around it, looking into scheduler options, restarting the scheduler before backup time, etc. I don't know what the bug is and I was hoping I could figure out what triggered it within True Image, but I could not. Therefore, just eliminate True Image scheduler from the equation.
Hopefully this may help someone else get by a similar error.
