Skip to main content

Problems with upgradeing from 2017 to 2019 version

Thread needs solution

On my work laptop I have upgarded to 2019 and pointed to where our new backups are being stored and created a new setup ect. but it wont accept My credentials. So try to look around on the forums and couldnt find anything. So today I ran the Acronis uninstaller to do a clean install of 2017, set it up as before and and backed up fine. Upgraded to 2019 and it wont let me access the back up and keeps saying connection failed everytime I try to back it up.

0 Users found this helpful

Peter, welcome to these public User Forums.

I am not aware of any reason why your upgrade from ATI 2017 to 2019 should cause your backup credentials not to be accepted?

I would suggest trying a clean install of ATI 2019 (as you did with 2017) and see if that works correctly?

If you still have an issue, then more information would be needed to better understand exactly what you are doing and what credentials are involved?

Hi Steve, Thanks for the reply. I have just done a clean install of 2019 and still the same problem. All I am doing is to do a back up to our file server using my Windows 365 credtials which as i have said before works fine with 2017. I can map the Drive fine in windows as well. Cheers.

Peter, this is strange and a new issue to me as I cannot think of any good reason why your credentials should not be accepted if they work correctly with the older ATI 2017 application for a backup task to the same file server location.

I can only suggest reviewing the information provided in KB 58004: Acronis True Image 2016: Troubleshooting Issues Related to NAS Credentials which still applies to later version of ATI.

If that still does not help resolve this issue, then please open a Support Case direct with Acronis to let them investigate more directly with you.

Hi Steve,

                  Thanks for  the help it as a setting on the server with local permissons and not allowing all the PCs to see the file server. All sorted now on this issue.

Peter, good to read that the issue is all sorted now, thanks for the feedback.