Error 0xb042f: Destination is unavailable. Acronis 2020

Pierre, thanks for introducing this as a new topic.

Please create the Acronis System Report zip file and then send me a private link to where I can access it (via such as OneDrive etc), and I will look to see if there is anything else that stands out for this issue?

The other approach here would be to raise this as a new Support Case direct with Acronis Support, who in turn, will most probably suggest trying a Repair Install at a minimum, then followed by a full clean install (if the problem continues) before then collecting various dumps and trace data.

A couple of questions:
Did you have a prior version of ATI installed before upgrading to ATI 2020, if so, which one?
If you had a prior version, was that also upgraded from one or more earlier versions?

Just trying to get a better feel for the history here given am not seeing other users reporting this issue with the combination of error messages (destination & network combination)?

One good thing with recent versions of ATI is the ability to export backup task settings to a zip file and later import it back again to minimise the effects of doing a clean install, but this is predicated on having a working configuration prior to exporting it. 

Pierre,

Have you tried creating a new backup task, not modifying the script file, and running the new task?  This will verify if in fact the tibx format is indeed a part of this issue or not.

Question, You say you upgraded from Win 7 to Win 10 and after that the backup task failed.  This task, was it run prior to the upgrade to create the base Full backup file and then run again after the Win 10 upgrade which resulted in failure?

If the above questions answer is yes, then I suspect that something has/was changed by the Win 10 upgrade which caused this issue.  What exactly remains to be found.

@Steve,

In order to recreate the problem (to send you a report), I will need to create another backup job with an unmodified script. I hope that the two backup jobs will not interfere with one another (they shouldn't). I'll schedule this new one at 3am while the first one runs at 1am.

Now, because this machine is a client's machine, I can only access it (remotely) late in the evening, when no one is on it. So that limits my ability to work on it.

Yes I have thought of raising a ticket with Acronis Support, but past experience made me hesitate. This user forum (and you in particular) has been more helpful than Acronis Support.

Regarding prior versions, as far as I can tell, there was none. There was some other (non-working) backup software, not from Acronis, which I had removed. If there was a prior version of ATI and it has been removed before my time, I don't know, but it is a possibility. I understand why you are asking. The issue is that the previous IT person passed away, and then the client called upon me.

@Enchantech,

Regarding creating a new backup task, well, out of the 3 failures, I think (but not 100% sure) that at least one of them was a recreation of the backup task. Basically I will have to try again, and I need to create a new backup task based on Steve's recommendation (see above).

Regarding the Win7-Win10 question, ATI 2020 was installed AFTER the upgrade.

Stay tuned.

Will be interesting to see how a new task behaves.  I'm thinking it should work just fine.

Hi Steve and Enchantech,

I created a new task last night (for 3AM) and it failed in exactly the same way as before. The email I received is timestamped 3:24am so that's about the right timing, same as before. For the record, here is the content of the email:

===== Begin =====

2019-12-28T03:00:00:444-05:00 380 I00000000: -----
2019-12-28T03:00:00:444-05:00 380 I00000000: ATI Demon started. Version: 24.5.1.22510.
2019-12-28T03:00:00:522-05:00 380 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false; 
2019-12-28T03:00:00:522-05:00 380 I00640002: Operation TIBX Test started by schedule.
2019-12-28T03:00:06:194-05:00 380 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false; 
2019-12-28T03:00:06:194-05:00 380 I013C0000: Operation: Backup
2019-12-28T03:00:06:225-05:00 380 I0064000B: Priority changed to Low.
2019-12-28T03:24:08:894-05:00 380 E000B042F: Error 0xb042f: Destination is unavailable.
| trace level: error
| line: 0x5d5406763c32a94
| file: c:\bs_hudson\workspace\23\products\imager\archive\impl\operations\utils.cpp:582
| function: TrueImage::Archive::MakeDestinationUnavailableError
| line: 0x5d5406763c32a94, c:\bs_hudson\workspace\23\products\imager\archive\impl\operations\utils.cpp:582, TrueImage::Archive::MakeDestinationUnavailableError
| Path: F:\Acronis TIBX Backups\
| StrId: 
| $module: ti_demon_vs_22510
|
| error 0x2160015: A backup error.
| line: 0xa340ffd3416335cf
| file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\da_api\backup.cpp:353
| function: da_backup::Commit
| line: 0xa340ffd3416335cf, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\da_api\backup.cpp:353, da_backup::Commit
| $module: disk_backup_vs_650
|
| error 0x40015: Network disconnected.
| line: 0x8af64b2c0920f7ff
| file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\resizer\archive3\archive3_error.cpp:193
| function: `anonymous-namespace'::ConvertArchive3Error
| line: 0x8af64b2c0920f7ff, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\resizer\archive3\archive3_error.cpp:193, `anonymous-namespace'::ConvertArchive3Error
| $module: disk_backup_vs_650
|
| error 0x29b1399: Network operation failed
| line: 0x30ba355f9fd4ffbd
| file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\resizer\archive3\utils.cpp:364
| function: `anonymous-namespace'::ArchiveWriterImpl::CoroutineFunc
| line: 0x30ba355f9fd4ffbd, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\resizer\archive3\utils.cpp:364, `anonymous-namespace'::ArchiveWriterImpl::CoroutineFunc
| function: archive_stream_write_shbuf
| path: \\?\F:\Acronis TIBX Backups\/TIBX Test.tibx
| $module: disk_backup_vs_650
|
| error 0xfff0: The semaphore timeout period has expired.
| 
| line: 0x30ba355f9fd4ffbd
| file: c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\resizer\archive3\utils.cpp:364
| function: `anonymous-namespace'::ArchiveWriterImpl::CoroutineFunc
| line: 0x30ba355f9fd4ffbd, c:\jenkins_agent\workspace\mod-disk-backup\650\product\core\resizer\archive3\utils.cpp:364, `anonymous-namespace'::ArchiveWriterImpl::CoroutineFunc
| function: pcs_co_file_writev
| path: \\?\F:\Acronis TIBX Backups\TIBX Test.tibx
| code: 0x80070079
| $module: disk_backup_vs_650
2019-12-28T03:24:09:441-05:00 380 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bced8
| file: c:\bs_hudson\workspace\23\products\imager\demon\main.cpp:738
| function: main
| line: 0x9f2c53c72e8bced8, c:\bs_hudson\workspace\23\products\imager\demon\main.cpp:738, main
| $module: ti_demon_vs_22510

===== End =====

So I created a system report, which can be found here: https://drive.google.com/file/d/1BKwHW1KU9IodRjAOgA9jJU_NowmCnO5d/view?…
Let me know when I can remove the file.

I looked at it and already see some things that don't make sense (to me anyway). In the disk.txt file, on line 20, it says:

Free letters:       ----EFGHIJKLMNOPQRSTUVWX--

That is REALLY strange. The OS drive is C:, there is a DVD-RW drive at D:, a DVD drive at E:, and the external USB drive is F:, as shown in Disk Management and File Explorer. So how on earth could ATI report that E and F are free letters? If ATI is looking for the backup destination on D:, well, sure enough, it's not going to find it. The backup configuration shows the destination on F: in the GUI, AND in the script file.

Here are 4 lines from the script file:

                    <volumes_locations>
                        <volume_location partition_id="" uri="F:\Acronis TIBX Backups\TIBX Test.tibx" volume_id="2983872007" />
                        <volume_location partition_id="" uri="F:\Acronis TIBX Backups\TIBX Test.tibx" volume_id="0" />
                    </volumes_locations>

Another strange thing. In the groups.txt file, the only line shows:

group: "None" domain: "MARTIN-420"

The machine is configured for a Workgroup. Where on earth is ATI seeing a domain? Could that explain the unexplained network error?

I will let the experts ponder on the rest of the report data.

Thanks for your help.

Pierre, thanks for the system report zip file.  Looking at the information from this doesn't throw any more light on this issue.  I can see no other errors being posted other than those already reported here.  The backup looks to proceed normally for over 20 minutes then hits an issue which looks to be mis-reported as being associated with your network.

I cannot see any associated errors being reported in the system or application event logs, nor in the other ATI logs.

The main backup_worker log with much better detailed information still says the same (see copy attached below).

The options at this point are:

Open a Support Case direct with Acronis and provide them with the System Report zip file along with a link to this forum topic.

Test the same backup to a different backup drive (if you have the option to do so).

Try doing the actions described in KB 60915: Acronis True Image: repairing program settings - starting with forcing a rebuild of the internal Acronis Database, then a Repair Install and if still no change, doing a clean install of ATI (after exporting your backup configuration to a zip file).

Pierre,

Have a look at the link below, it might lead you to a resolution:

Semaphor timeout error

Enchantech wrote:

Have a look at the link below, it might lead you to a resolution:

Semaphor timeout error

There are some peculiarities in that article.  The author uses the term "driver" when I think he means "drive" or "device".  I may be wrong about his meaning, but I'm pretty sure he does not mean the code needed to support I/O for a device.

Then he says

As you might know, transferring huge files is possible only if the actual drivers are formatted into NTFS

I'm guessing he is trying to say that an NTFS drive supports larger files sizes than FAT32 so if the source is a large file in NFTS that cannot be handled by FAT32, make sure the destination is NTFS. 

Would this be a problem with ATI?  I assumed ATI would write a series of 2GB files if a backup destination is FAT32.  It would probably make sense to convert the destination to NTFS (if there are no contraindications), but save the data before you format the drive.

Patrick,

I agree, there are bad wording and I agree that drive in place of driver is meant in several places.  The article does provide a reasonable place to start for troubleshooting and is why I provided it.

Another suggestion would be to change the USB connection of the external drive to a different port if available or try replacing the cable.  Large data transfers that take long periods of time can trigger this error and often improving connection speed will solve the issue.

  I had the same problem as the OP using ATIM 2020 on Windows 10:  the backup would start, a partial *.tibx file would be written, and then the backup would fail with the "Ensure that destination is accessible" message.

  I tried it about 3-4 times in the past 24 hours, and I experienced the same result each time.

The 0xb042f error code is shown below in my "MVP Log View v 2.10" log output.

  I was using an external USB drive, and I was always able to go to the backup folder and create a new (temporary) folder in the same location.  This was my way of convincing myself that the backup drive and folder were actually accessible.

  Anyway, I solved the problem by simply unplugging my USB cable from the back of my computer and re-inserting.

  I re-inserted the USB cable into the same original USB port that it had been in previously - so this was not about changing the USB port used.

  When I re-tried the backup, it went through just fine.

  Perhaps someone with much more knowledge on the subject can explain why this worked.

  I don't really believe this was about a loose USB connection.

  I am only speculating here, but it feels more like the cycle of un-plugging/plugging the USB cable re-initialized or "woke up" something (the USB connection state, some USB port monitoring software/demon?).

I have no idea what that "something" would be, so maybe someone with more knowledge can flesh out the details or completely debunk my guess.

  What's strange is that I was always able to go into the backup folder and create a new folder using Windows File Explorer each time it failed, so the drive was always "accessible" in a general way.

2/10/2020 8:23:11 PM: -----
2/10/2020 8:23:11 PM: ATI Demon started. Version: 24.5.1.22510.
2/10/2020 8:23:11 PM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2/10/2020 8:23:11 PM: Operation <foo_bar_backup_name_changed> started manually.
2/10/2020 8:23:12 PM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2/10/2020 8:23:12 PM: Operation: Backup
2/10/2020 8:23:12 PM: Priority changed to Low.
2/10/2020 8:28:06 PM: Error 0xb042f: Destination is unavailable.
2/10/2020 8:28:06 PM: Error 0x13c0005: Operation has completed with errors.

Start: 2/10/2020 8:23:11 PM
Stop: 2/10/2020 8:28:06 PM
Total Time: 00:04:55