Failed to open backup nas: Check your network connections.
hi there,
siwtched from TIB 2019 to 2020, snce then problems creating backups on my NAS (synology) worked fine with 2019.
here some infos:
2020-04-02T15:20:45:673+02:00 5424 I00000000: ----- 2020-04-02T15:20:45:673+02:00 5424 I00000000: ATI Demon started. Version: 24.5.1.22510. 2020-04-02T15:20:45:705+02:00 5424 I00640000: Attribute für Backup-Reservekopie: format tib; need_reserve_backup_copy false; 2020-04-02T15:20:45:706+02:00 5424 I00640002: Aktion AMOREMIO wurde per Planung gestartet. 2020-04-02T15:20:46:090+02:00 5424 I00640000: Attribute für Backup-Reservekopie: format tib; need_reserve_backup_copy false; 2020-04-02T15:20:46:091+02:00 5424 I013C0000: Aktion: Backup 2020-04-02T15:20:46:091+02:00 5424 I0064000B: Priorität geändert in 'Niedrig' 2020-04-02T15:20:47:582+02:00 5424 E00040019: Error 0x40019: Fehler beim Backup. | Ablaufverfolgungsebene: Fehler | line: 0xaa33a143c434a5f5 | Datei: c:\bs_hudson\workspace\23\home\backup_worker\impl\backup_worker.cpp:167 | Funktion: `anonymous-namespace'::ReturnCodeToError | line: 0xaa33a143c434a5f5, c:\bs_hudson\workspace\23\home\backup_worker\impl\backup_worker.cpp:167, `anonymous-namespace'::ReturnCodeToError | Archive3Code: 0x138d | Name: | $module: archive3_adapter_vs_22510 2020-04-02T15:20:47:743+02:00 5424 E013C0005: Error 0x13c0005: Aktion mit Fehlern beendet. | Ablaufverfolgungsebene: Fehler | line: 0x9f2c53c72e8bced8 | Datei: c:\bs_hudson\workspace\23\products\imager\demon\main.cpp:738 | Funktion: main | line: 0x9f2c53c72e8bced8, c:\bs_hudson\workspace\23\products\imager\demon\main.cpp:738, main | $module: ti_demon_vs_22510
Any Solutions?
Thanxs
Rudolf


- Log in to post comments

Thanxs Enchantech,
the fix in the link does not work for me, so I send you more specific Infos:
Failed to open backup nas://MAMAEPAPAE.FRITZ.BOX/Meine Backups/Amore/AMOREMIO.tibx. Check your network connections.:
https://kb.acronis.com/errorcode/
Ereignis-Code: 0x006400D5+0x01E50005+0x01E50015+0x01E5001A+0x0004000D
in the annex the backworker log:
2020-04-05T07:39:29:635+02:00 10996 I00000000: >>> --id=10001 --action=browse --agent="Acronis True Image 2020 24.5.1.22510 Win" --archive="smb://MAMAEPAPAE.FRITZ.BOX/Meine Backups/Amore/AMOREMIO.tibx" --ar-loc-username="XXXXXXXXXX" --ar-loc-password=*
2020-04-05T07:39:30:612+02:00 9492 I00000000: type=log; level=err; message=an error has occured while connecting to '\\MAMAEPAPAE.FRITZ.BOX\Meine Backups\Amore\', returned error = '1326', last error = '1326';
2020-04-05T07:39:30:618+02:00 9492 I00000000: type=log; level=inf; message=ar#1: opening archive path="\\?\UNC\MAMAEPAPAE.FRITZ.BOX\Meine Backups\Amore\/AMOREMIO.tibx" in readonly mode;
2020-04-05T07:39:30:652+02:00 9492 I00000000: type=log; level=wrn; message=pcs_errno_to_err: Failed to convert errno 1326 to pcs error. Return PCS_ERR_UNKNOWN value.;
2020-04-05T07:39:30:652+02:00 9492 I00000000: type=log; level=inf; message=pcs_dirent_first(\\?\UNC\MAMAEPAPAE.FRITZ.BOX\Meine Backups\Amore\) failed: 1326 (pcs_err=4095);
2020-04-05T07:39:30:652+02:00 9492 I00000000: type=log; level=err; message=ar#1: failed to find archive files: -5005 Input/output error;
2020-04-05T07:39:30:652+02:00 9492 I00000000: type=log; level=err; message=ar#1: failed to open archive path="\\?\UNC\MAMAEPAPAE.FRITZ.BOX\Meine Backups\Amore\/AMOREMIO.tibx" mode=readonly uuid=00000000000000000000000000000000, err=-5005 (Input/output error);
2020-04-05T07:39:30:652+02:00 9492 I00000000: type=log; level=err; message=unable to open archive file (err -5005);
2020-04-05T07:39:30:652+02:00 9492 I00000000: type=retcode; value=5005; id=10001;
2020-04-05T07:39:30:653+02:00 10996 I00000000: >>> --id=1 --action=backup --action=cleanup --action=metainfo --disk-backup --agent="Acronis True Image 2020 24.5.1.22510 Win" --archive="smb://MAMAEPAPAE.FRITZ.BOX/Meine Backups/Amore/AMOREMIO.tibx" --ar-loc-username="XXXXXXXXXX" --ar-loc-password=* --source="\\local" --exclude-wildcard="hiberfil.sys" --exclude-wildcard="pagefile.sys" --exclude-wildcard="$Recycle.Bin" --exclude-wildcard="swapfile.sys" --exclude-wildcard="System Volume Information" --exclude-wildcard="*.tib" --exclude-wildcard="*.tibx" --exclude-wildcard="*.tib.metadata" --exclude-wildcard="*.~" --exclude-wildcard="*.tmp" --exclude-wildcard="C:\\Users\\olala\\AppData\\Local\\Temp\\*" --exclude-wildcard="C:\\Users\\olala\\AppData\\Local\\Microsoft\\Windows\\INetCache\\*" --exclude-wildcard="C:\\Users\\olala\\AppData\\Local\\Mozilla\\Firefox\\Profiles\\*\\cache2" --exclude-wildcard="C:\\Users\\olala\\AppData\\Local\\Mozilla\\Firefox\\Profiles\\*\\OfflineCache" --exclude-wildcard="C:\\Users\\olala\\AppData\\Local\\Opera Software\\Opera Stable\\Cache" --exclude-wildcard="C:\\Users\\olala\\AppData\\Local\\Opera Software\\Opera Stable\\Media Cache" --exclude-wildcard="C:\\Users\\olala\\AppData\\Local\\Google\\Chrome\\User Data\\Default\\Cache" --exclude-wildcard="C:\\Windows\\CSC" --machine-id="656E9088-89F1-49C2-A221-97E6E0E13466" --resource-id="2124891B-87C2-4C67-95D1-24341BD335BE" --resource-type="entire-pc" --vss-mode="vss" --backup-scheme="full" --keep-versions=1 --keep-first-slice
2020-04-05T07:39:46:504+02:00 9492 I00000000: type=log; level=err; message=an error has occured while connecting to '\\MAMAEPAPAE.FRITZ.BOX\Meine Backups\Amore\', returned error = '1326', last error = '1326';
2020-04-05T07:39:46:504+02:00 9492 I00000000: type=log; level=wrn; message=watchdog: pcs evloop #0 was not working for 15 sec;
2020-04-05T07:39:46:504+02:00 9492 I00000000: type=log; level=inf; message=ar#1: opening archive path="\\?\UNC\MAMAEPAPAE.FRITZ.BOX\Meine Backups\Amore\/AMOREMIO.tibx" in append mode (create);
2020-04-05T07:39:46:535+02:00 9492 I00000000: type=log; level=wrn; message=pcs_errno_to_err: Failed to convert errno 1326 to pcs error. Return PCS_ERR_UNKNOWN value.;
2020-04-05T07:39:46:535+02:00 9492 I00000000: type=log; level=inf; message=pcs_dirent_first(\\?\UNC\MAMAEPAPAE.FRITZ.BOX\Meine Backups\Amore\) failed: 1326 (pcs_err=4095);
2020-04-05T07:39:46:535+02:00 9492 I00000000: type=log; level=err; message=ar#1: failed to find archive files: -5005 Input/output error;
2020-04-05T07:39:46:535+02:00 9492 I00000000: type=log; level=err; message=ar#1: failed to open archive path="\\?\UNC\MAMAEPAPAE.FRITZ.BOX\Meine Backups\Amore\/AMOREMIO.tibx" mode=append uuid=00000000000000000000000000000000, err=-5005 (Input/output error);
2020-04-05T07:39:46:535+02:00 9492 I00000000: type=log; level=err; message=unable to open archive file (err -5005);
2020-04-05T07:39:46:535+02:00 9492 I00000000: type=retcode; value=5005; id=1;
2020-04-05T07:39:46:535+02:00 10996 I00000000: >>> exit
2020-04-05T07:39:46:550+02:00 10996 I00000000: >>> exit
hope you find a solution
- Log in to post comments

I notice you have in use Fritz.box. We helped another user of TI 2019 with issues similar to yours. The end result was faulty firmware update to the Fritz. Not sure that it will be of help but the link to that thread is Here
- Log in to post comments

I do have the same error and no Fritz.box. After a lot of searching it looks like the error 1326 in ATI means wrong username or password.
Because the password works during the "Test connection" and several other tests I was very sure that the password is correct, which hints that there may be an encoding or transfer issue while passing it around between (ATI) components. This is mostly the case if the password contains non-ASCII characters. So I checked the password of my backup user and found that indeed it contained non-ASCII characters.
Long story short, after I changed the password to only contain characters of the ASCII (http://ascii-table.com/) table I can finally backup my stuff.
So while the same user and password worked in ATI 2018 it looks like ATI 2020 is taking us back to the late 1980s, password encoding wise ;-).
- Log in to post comments

rbrunhuber, welcome to these public User Forums.
Please submit Feedback direct to Acronis with your conclusions as above using the tool provided in the ATI GUI.
- Log in to post comments

Steve Smith wrote:Please submit Feedback direct to Acronis with your conclusions as above using the tool provided in the ATI GUI.
Ok will do. In addition I found that the password problem is not an issue when you upgrade from 2018 to 2020.
- Log in to post comments

Please make that known to support in feedback as well.
- Log in to post comments

Out of interest, what character(s) did you have in your password that was not shown in the linked ascii table?
- Log in to post comments

The bad boy in this case was §.
- Log in to post comments

Thanks for the response. The Section sign is an extended ASCII symbol, wonder if all extended ASCII symbols are invalid?
- Log in to post comments

rbrunhuber wrote:The bad boy in this case was §.
rbrunhuber, thank you for pointing the issue! We've created a task for fixing (internal ID for reference TI-179916 backup to network shared folder fails if credentials have non-ASCII character)
- Log in to post comments

Thanks Ekaterina. Nice to know that this will be fixed.
- Log in to post comments

Hi,
my password includes also a non ASCII character and the backup to the network drive fails as well with the 2020 version of Acronis true image. Is there any update version already available for download which fixes the issue?
Thanks!
Regards
Martin
- Log in to post comments

Martin Hahn wrote:my password includes also a non ASCII character and the backup to the network drive fails as well with the 2020 version of Acronis true image. Is there any update version already available for download which fixes the issue?
Unfortunately there is no update yet. Independent of Acronis and the update: The best you can do is really try to stay in the ASCII range. You can create really strong passwords with this character set too, that satisfy the common password policies. Generally speaking length is more important than a huge character pool for strong passwords.
To be honest: These issues have been around for so long and keep coming up again and again that even if it gets fixed in ATI it's still a good idea to not use the non-ASCII characters in passwords anywhere.
- Log in to post comments

rbrunhuber wrote:..These issues have been around for so long and keep coming up again and again ...
This is why the failure is unexpected in year 2020, decades after the extended ASCII code gots introduced.
- Log in to post comments

Martin Hahn wrote:rbrunhuber wrote:..These issues have been around for so long and keep coming up again and again ...
This is why the failure is unexpected in year 2020, decades after the extended ASCII code gots introduced.
The problem is that all the "new" encodings, like the whole unicode family are bit-compatible to the ASCII part, but not to extended ASCII. So if not everybody agrees on the encoding of e.g. a config file you will have issues. I'd wish that these problems were gone for good by they keep appearing and I'm just sick of spending my time debugging these issues.
My advice: Accept that passwords are limited to ASCII or get bitten again, and again, and again, and again, ...
I'm still convinced that these issues should be fixed in ATI and every other software, therefore I write bug reports and if necessary help people fix this stuff. But I guess I can't write enough bug reports to get rid of all these problems.
- Log in to post comments