Acronis 2016 Build 5620 issues with SMB network locations
Posting here as unable to get any direct support from Acronis (see previous post)
I am trying to backup files on a smb network share to a local external hard drive. The host machine (which is running Acronis and where the removable drive is) is Windows 10. The remote server that hosts the smb files that I am trying to back up is a Linux box with Samba server. Previous versions worked fine when I did this process. The file shares are all available in Windows and there are no authorization errors. Acronis 2016 allows me to freely browse the shares when selecting the source files.
Starting the backup process results in an error:
Access to the file or folder is denied (0x40014) and The user name or password is incorrect.
No options in the dialogue to change any stored passwords that Acronis might have for this network location and nowhere in the GUI that I can set this information it seems.
Re working the look of a product is great but if it removes functionality, slows the GUI down and leads to this sort of issue I would have preferred to stay with the UI that actually required a little skill to use, but actually worked properly.
Any thoughts anyone? Am I missing something?
Regards,

- Log in to post comments

Geoff,
True Image 2016 has a problem with SMB servers and logon credentials. Some users have issues with credentials, others have issue with the app recognizing their devices, some have both.
The application uses Windows credentials for local access to perform the disk level functions of the application. This is handled by the requirement that UAC is activated on program start and must be acknowledged in addition to certain functions require admin log on to run.
You should be able to solve your issue by adding your SAMBA server username/password credentials into Windows Credentials Manager. To access the credential manager simply use Windows search feature to locate it. Once located open file and look for your SMB server. I'll bet you won't find it. If that is the case then you will see that it is possible to add a device to the manager so, select ADD to add your server. You can add it by hostname or IP address with hostname being preferred. Enter your server credentials and apply your actions which will add your server to the list and save your credentials.
If your shares are user/password protected which it sounds like they are when you select a share now you will get a credentials logon box. This logon info is compared against what you just entered in the Credentials Manager to authenticate and then upon match you are granted access. This logon will last as long as the current network session lasts.
If at some point in the future you have need to change your credentials for the device you will need to access the Windows Credentials Manager and enter the changes there.
- Log in to post comments

Hi Enchantech
Thanks so much for your help with this - you were indeed right. There were no Samba credentials in my Windows 10 installation after the upgrade from Windows 7. I created an entry for the server in question and then restarted Acronis True Image and recreated the backup job. Annoyingly it didn't ask for credentials when I browsed the network drive that I was trying to back up - which suggested that it was caching credentials somewhere.
I eventually found them in the registry (usual registry disclaimer for everyone - if you edit your registry and get it wrong you can destroy your Windows operating system). So for others (and based on Enchantech's lead) if you are having similar problems and know what you are doing, Acronis 2016 (or a previous version - Im not sure), stores your credentials in this key for smb shares:
HKEY_CURRENT_USER\SOFTWARE\Acronis\Connections\smb\name-of-your-server
I deleted this key and re-started Acronis True Image. This time it asked for my credentials, verified them and established the connection. Looking at the key structure again I'm pretty sure that 2016 recreated a different set of values - a new subkey called UseNTAuth with a value of (0) appears to have been created which I don't remember being in the key I deleted. My suspicion is that 2016 handles this authentication differently from the version that originally wrote this key and this is why it was falling over.
Not entirely sure if this has solved the issue. The backup seems to have started and there are no errors in the logs, but is still at the 'Calculating Time remaining' and 49.5 KB processed stage. It may be just enumerating the files so I'm keeping my fingers crossed. I'll let you know. Thanks again both for your help.
Regards,
Geoff.
- Log in to post comments

Update - this did indeed work for me and the backup completed fine. Thanks again.
- Log in to post comments

Geoff,
Glad you got it working and thanks for the registry tip. Looks like Windows has some fault here as well which I suspected. There have been similar issues with this in previous versions of TI and Windows so, not sure of the reason why these issues occur.
- Log in to post comments