Skip to main content

Access denied for logged on user to backup target folder in the network

Thread needs solution

The HD on a WIN8.1 system was broken. I had to set up the system complete again, because I had no backup.
The system got the same name then the broken one. I also created the identical user on the new system.
Then I installed and configured ACRONIS 2016. The backup target folder is on a server 2008 in my Workstation network. The backups of this workstation were created like sheduled. To this share I backup also all my other systems successful.
The broken HD I sent to a data rescue company to rescue the files. I got a USB HD with the rescued files and the old HD in a condition back, that I was able  to Boot from this HD. :-)
With the SAMSUNG Data Migration Tool I was able to restore the old system to a SAMSUNG SSD.
I installed now ACRONIS 2016 and configured a backup job. The backup target is also the 2008 Server network folder.

The backup quits and log says: (translated german to english)

"  True Image    05.06.2017 11:25:19   The Backup failed. Close the application which accesses the file: \\Server2008\d\Backup\Folder1\Kompletter WS01_full_b1_s1_v1.tib
12    True Image    05.06.2017 11:25:19    Access denied"

I can map the target folder in the context of the user which is logged on to the source system and I can create a file there. I compared the security settings with the other backup folders,- I guess they are simular.
This user has full access and is member of the Local Admin group of the target system. In the event log of the target system I can see that the user can log on:

SubjectUserSid S-1-0-0
  SubjectUserName -
  SubjectDomainName -
  SubjectLogonId 0x0
  TargetUserSid S-1-5-21-3280412416-1915016894-2504757713-1009
  TargetUserName suz
  TargetDomainName Server2008
  TargetLogonId 0x6cf44
  LogonType 3
  LogonProcessName NtLmSsp  
  AuthenticationPackageName NTLM
  WorkstationName WS01
  LogonGuid {00000000-0000-0000-0000-000000000000}
  TransmittedServices -
  LmPackageName NTLM V2
  KeyLength 128
  ProcessId 0x0
  ProcessName -
  IpAddress 192.xxx.x.xx0
  IpPort 49268

But 10 seconds later the logoff:

TargetUserSid S-1-5-21-3280412416-1915016894-2504757713-1009
  TargetUserName suz
  TargetDomainName MHSRV01
  TargetLogonId 0x6cf44
  LogonType 3

I guess in this 10 seconds checks ACRONIS if it is able to create a file. This was not successful.

Next ACRONIS tries to log on with "Guest / Anonymus":

PackageName MICROSOFT_AUTHENTICATION_PACKAGE_V1_0
  TargetUserName Gast
  Workstation WS01
  Status 0x0

If I add then "Everybody" on the security tab of target folder, with full access, the backup will be created.
But this will not be really secure.

Why the hell is ACRONIS not able to create the file in the user context?
Where can I enter credentials in ACRONIS to access to the network backup folder?
Normaly this is not neccessary,- but here it might be?
Can be the reason,  that the user account existed before on a other identical system with an other SID?
Does ACRONIS save such informations on the target?

Maybe it not an ACRONIS issue, but a Windows user account issue.

I hope somebody can give me a hint how to solve this issue.

 

 

 

 

 

 

 

0 Users found this helpful

Matthias, welcome to these user forums.

This does sound to be a credentials issue that you are describing.  

Please see KB 58004: Acronis True Image 2016: Troubleshooting Issues Related to NAS Credentials which may help you to better isolate the cause of the problem. 

Thank you for the welcome and the link to the NAS article. Now I know the places where Acronis stores the credentials.

I checked the REG key HKEY_CURRENT_USER\Software\Acronis\Connections\smb and the file 1232-076E-4E29-879B-4E7D8EB8FD42.tib.tis.
In both locations are no credential informations. I guess in the *tib.tis file, this tag must contain credentials:

<volume_location device_instance_id="" uri="\\TargetServer\d\Backup\BackupFolder\@task@.tib" volume_id="0" />

What did I make wrong, that the credentials were not entered?
Does it make sense to pick the credentials from a backup of the interim OS and to enter it into the current registry?
Is it enough to enter the credentials in the registry or is the complete 1232-076E-4E29-879B-4E9D8EB8FD42.tib.tis also neccessary?
Is there a tool to encrypt user and password Acronis conform?

Matthias, if you clear the stored credentials in the Registry for Acronis then go back into the configuration of your backup task in the main GUI, this should then prompt you to provide new credentials for your NAS.

There is no tool which would allow you to encrypt the credentials apart from doing this via the ATIH application when you configure your backup task.

In reply to by truwrikodrorow…

Thank you Steve. I'll try this. But there were no credentials stored. The key HKEY_CURRENT_USER\Software\Acronis\Connections\smb\TargetServerName|Password and |Username were without a value.
And I was never prompted for credentials??

When will be the 1232-076E-4E29-879B-4E7D8EB8FD42.tib.tis. created? How do the credentials come into this file?
Is it importand that this file also contains the credentials? Or are the credentials in the registry the importand one which will be entered into the file by a miracle? ;-)

Matthias, if you are not seeing the credentials in the registry as per the KB document, then these will only be created when Acronis does this as part of task creation.

The entries in the .tib.tis file are created when the backup task runs and relate to the backup files created on the target NAS drive and embeds the credentials for the NAS with each individual file name details.

On my ATIH 2017 system, I see as follows in the registry.

NAS Credentials.png

I would suggest that you may be best to make a clean start with Acronis if you are not being asked for the NAS credentials, creating new backup tasks for the NAS.

To do a clean install, first uninstall ATIH normally via the Control Panel, then download the Acronis Cleanup Tool (link in my signature) and run this as Administrator followed by restarting the computer, then reinstalling ATIH again.