Skip to main content

Failed to get archive URIs from location

Thread needs solution
Beginner
Posts: 1
Comments: 0

Hi, 

Recently I got an error with my Acronis (Version 11.5 build 11.5.38929) which is failed to get archive URIs from location. The errors are listed below:

 

Code: 10,551,496(0x00A100C8)
LineInfo: 0x9A79F20828BCCC4;

Module: archive_manager_plugin_vs_38929
Message: Failed to get archive URIs from location 'arl:/9268A143-1B1C-45F2-9891-F1B76A9E74E6/911B89C4-8444-42EC-A571-145C313BFFD3'.

Code: 10,551,496(0x00A100C8)
LineInfo: 0xB320396ADFE3B55;

Module: archive_manager_plugin_vs_38929
Message: Failed to get archive URIs from location 'arl:/9268A143-1B1C-45F2-9891-F1B76A9E74E6/911B89C4-8444-42EC-A571-145C313BFFD3'.

Code: 10,551,496(0x00A100C8)
LineInfo: 0xA0F87A51D6F9CC72;

Module: archive_manager_plugin_vs_38929
Message: Failed to get archive URIs from location 'arl:/9268A143-1B1C-45F2-9891-F1B76A9E74E6/911B89C4-8444-42EC-A571-145C313BFFD3'.

Code: 4,194,944(0x00400280)
LineInfo: 0xA1D3981537C68767;

Module: archive_manager_plugin_vs_38929
Message: Failed to open the metadata directory.

Code: 4,194,350(0x0040002E)
LineInfo: 0x3F26773FAB7BDA10;

Module: archive_manager_plugin_vs_38929
Message: Failed to open the backup location.

Code: 262,154(0x0004000A)
LineInfo: 0xF35F747B3B21F9DD;

Module: archive_manager_plugin_vs_38929
Message: Error occurred while creating the file.

Code: 65,520(0x0000FFF0)
LineInfo: 0xBD28FDBD64EDB8EE;

Module: archive_manager_plugin_vs_38929
Message: The specified network name is no longer available

Could you help me to get resolving this issue?

Attachment Size
Acronis Version.jpg 101.89 KB
0 Users found this helpful
Forum Moderator
Posts: 248
Comments: 7081

Hi!
Thank you for your posting!

1) using Windows Explorer, open the network share where you save backups
2) using the ping command, check connectivity to the machine/device where you save backups:
ping <hostname>
ping <IP address>
3) If you cannot connect to this machine/storage, check whether the machine is up and running. Reboot if necessary.
4) If the machine/device responds to ping by IP, but doesn't respond to ping by hostname, there are DNS issues in the network.
5) Make sure that the share was neither renamed nor removed.
6) Try creating a new vault on the same share\test a new backup