Skip to main content

Upgraded from Trueimage 2015 to 2017 - BUGS PART 1

Thread needs solution

I upgraded from the 2015 version, my existing path pointed to a UNC path like, and it refused to authenticate even though I use the correct username and password:
\\192.168.1.50\Backups\Acronis\MyPC

This does not work either:
nas://192.168.1.50/Backups/Acronis/MyPC

It turns out I have to substitute the IP ADDRESS for SYNOLOGY.HOME and it works:
\\SYNOLOGY.HOME\Backups\Acronis\MyPC
or
nas://SYNOLOGY.HOME/Backups/Acronis/MyPC

This worked in 2015 and not in 2017. Please fix, the paths should work with an IP address like previous versions.

Can anybody confirm this?
 

Thanks...

0 Users found this helpful

Alex, there have been a number of issues in this area with both forms of network drive addressing where it works one way for some and the other way for other users.

Please see KB documents: 
59051: Acronis True Image 2017: Connection to NAS fails with errors "Connection failed", "Failed to check credentials", "Cannot find files and folders".
57992: Acronis True Image: NAS Is Not Detected

You should also ensure that you have the latest build #5554 installed for ATIH 2017 for fixes for other known issues.

Steve Smith wrote:

Alex, there have been a number of issues in this area with both forms of network drive addressing where it works one way for some and the other way for other users.

Please see KB documents: 
59051: Acronis True Image 2017: Connection to NAS fails with errors "Connection failed", "Failed to check credentials", "Cannot find files and folders".
57992: Acronis True Image: NAS Is Not Detected

You should also ensure that you have the latest build #5554 installed for ATIH 2017 for fixes for other known issues.

Thanks. I've logged a support ticket on this as well.

Yes I saw these workarounds, it's related but I'm not sure it's the same exact issue. Regardless it was working perfectly in 2015 and now it's not working in 2017, litterally an upgrade from 2015 to 2017 causes the behaviour. They need to release a patch via the usual distribution methods (automatic update) and I'd like Acronis to confirm they are doing this in the near future, this is not an acceptable situation IMHO.

NB running Windows 10 64 bit.

Alex, I would suspect that you may be advised to do a clean install for ATIH 2017 - we have seen some strange issues which that approach has resolved for other users who have upgraded from earlier versions.

The method of doing a clean install is to uninstall normally, then run the Acronis Cleanup Tool (link in my signature below), restart to complete the action, then do a fresh install of the latest full installer from your Acronis account with 'run as administrator'.  
Notes: The cleanup tool will also remove Acronis Disk Director plus remove all backup tasks and task history.  You can backup your task configurtion by saving a copy of the C:\ProgramData\Acronis\TrueImageHome\Scripts folder.

I took your advise. Consider the issue resolved - I very much appreciate your help Steve!!!

If Acronis support is reading this, please put in some decent cleanup code in TrueImage when upgrading. Bad upgrade... bad! And please check the two other URL's that I gave you (different issues).

Thanks again :)

Alex, thanks for this feedback, glad to hear that this issue was resolved by the clean install.

I've reproduced this issue now on two computers.

Should Acronis developers wish to fix this and relieve their support and customers from hassle they will need to test as below:

* Upgrade from Acronis 2015 to 2017
* Upgrade from Acronis 2014 to 2015 to 2017.

One or both of these scenarios should reproduce this issue. The symptoms are in the OP.

Thanks.

Alex, this is a user forum where the Acronis developers are very rare visitors, if at all, so you will need to either raise a support ticket or use the Feedback tool in the GUI to bring this issue to their attention.

The FAQ for ATIH 2017 does state the following: 

If you already have Acronis True Image 2016 or Acronis True Image 2015 installed, there is no need to remove the old version and reinstall the software. Start the installation file of Acronis True Image 2017 and install the product. After upgrade, create a new bootable media.

If you already have Acronis True Image 2014 or older versions, you need to delete these first and then install Acronis True Image 2017.

The next question to ask here is whether your ATIH 2015 was an upgrade from an earlier version, in which case it is likely that something carried over from the same?

"Alex, this is a user forum where the Acronis developers are very rare visitors, if at all, so you will need to either raise a support ticket or use the Feedback tool in the GUI to bring this issue to their attention."

Please see post #2. As I've already stated I have raised a supprt ticket and pointed to this thread, and yes I gave them the report dump via that tool. So everything I write here in this thread support should take notice of.

"The FAQ for ATIH 2017 does state the following: 

If you already have Acronis True Image 2016 or Acronis True Image 2015 installed, there is no need to remove the old version and reinstall the software. Start the installation file of Acronis True Image 2017 and install the product. After upgrade, create a new bootable media."

Yes these are good workarounds, the devs however need to fix these issues though in their upgrade scripts (cleanup code). Hopefully they will read this thread to understand what I mean.

To summarise again for support who should be reading this thread because I created a ticket pointing to this thread: 

I've reproduced this issue now on two computers.

Should Acronis developers wish to fix this and relieve their support and customers from hassle they will need to test as below:

* Upgrade from Acronis 2015 to 2017
* Upgrade from Acronis 2014 to 2015 to 2017.

One or both of these scenarios should reproduce this issue. The symptoms are in the OP.
A workaround has been posted and works. Issue still needs fixing in the upgrade scripts.

Thanks.