ATIH 2012 [6154] "Access to the File is Denied" when backing up to network share
With ATIH 2012 build 6154 I keep getting "Access to the File is Denied" when trying to backup my PC to a network share on another computer.
See the attachment with the error message. I have tried many times pressing Retry, and also pressing Browse and selecting again the same folder. In either case, the problem does not go away, and the dialog just pops up again after some minutes.
I am running Windows 7 on both computers.
(And, in case you ask, yes I do have have full read/write access for the users on both computers to the network share in question; I tested it by creating a file using Windows notepad).
In your Knowledge Base you mention some similar problems, and you claim these were fixed in build 6131. However I am running build 6154 and the above mentioned issue exists in this build.
Does anyone have any ideas??
Hi, I also do have the same problem with backing up to a NAS mapped drive. My NAS is Synology DS 1511+ and I use ATIH 2012. I don't have anything to attach. Can't open support ticket, because of stupid Acronis policy customer can only open support within 30 days of purchase the force customers to pay for fixing their own bugs... I have nothing to attach.
THE REAL PROBLEM:
Basic function of any backup program is to be able to backup to a network share, it's fundamental demand in the backup business. This is prohiitive that software of this caliber can't do this right and software engineers can't resolve/program correctly the basic functions of file access in Windows NT. Acronis forces to use UNC directly, but this is known to be a slower method since 1990's. That's why mapped drives have been invented. What Acronis does besides simply calling OpenFileEx() and similar native Win32 APIs?
Acronis does most probably disconnect remote drives connection/credentials when selecting destination drive dialog resulting in further browsing it invalid or unusable, so people have all this problem with "path/file invalid" and "access denied" and need to manually remap and this results in backup bypassing mapped drive designation and backing up to UNC anyway. It lists all my backups done in this way and I have no more mapped drives in the system as those disappeared after using Acronis. Acronis should not be messing with those NT APIs. I do provide/type password when connecting ad-hoc to a NAS and mapping the drive manually by myself before running Acronis main UI, so the drive is nicely present. ATIH do not need to do anything else, but I imagine you do use a Windows Service to perform actual backup and storage access and services are sensitive into the context those are run within. What we see from UI supposed to work without problem, but the service needs to authenticate on a separate level before being allowed to access network drive (depends on process credentials: LocalUser or NetworkUser in Win NT/2000/XP/2008/7). So, this is real problem, that maybe customers should configure to run Acronis Background Service to run under a user account and password designated to access the server (NAS) and its drives. It seems doing it programatically fails on Acronis engineers side as they don't prompt for a password to pass to appropriate domain APIs from within a service level!. Either software should prompt and incorporate network API usage into proper manner or ask to store network credentials on a separate tab under backup task options dialog and then pass those along with the write operations on UNC.
Thread locked as duplicate, main NAS discussion thread here.