Acronis 2021 - Access to file is denied

Franz, what type of backup is this?  If it is an Entire PC or Disks & Partitions backup, then look in the Backup Worker logs not the Demon ones, as those logs hold a lot more detailed entries versus the stripped down content of Demon logs.

One option for isolating this issue would be to do the same backup (source) to a local drive, i.e. USB external drive, which would eliminate any files in the source selection if successful.

Thanks for the response, Steve,

I am trying to make a full backup of a whole disk with the exceptions defaults plus some own exceptions.

Backup-Worker logs - I am not sure, what is meant with that.

More detailed log view regular says:

08.11.2022 21:34:33: +01:00 22204 I00000000: -----
08.11.2022 21:34:33: +01:00 22204 I00000000: ATI Demon started. Version: 25.10.1.39287.
08.11.2022 21:34:33: +01:00 22204 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
08.11.2022 21:34:33: +01:00 22204 I00640002: Operation KIOXIA-EXCERIA SSD ECFA15.3 started by schedule.
08.11.2022 21:34:33: +01:00 22204 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
08.11.2022 21:34:33: +01:00 22204 I013C0000: Operation: Backup
08.11.2022 21:34:34: +01:00 22204 E00040014: Error 0x40014: Access to the file is denied.
| trace level: error
| line: 0xaa33a143c434a604
| file: c:\jenkins_agent\workspace\ati-main-win-ati\529\home\backup_worker\impl\backup_worker.cpp:182
| function: `anonymous-namespace'::ReturnCodeToError
| line: 0xaa33a143c434a604, c:\jenkins_agent\workspace\ati-main-win-ati\529\home\backup_worker\impl\backup_worker.cpp:182, `anonymous-namespace'::ReturnCodeToError
| $module: ti_demon_vs_39287
|
| error 0x40014: Access to the file is denied.
| line: 0xc8d8731ce106f9cb
| file: c:\jenkins_agent\workspace\ati-main-win-ati\529\archive\ver3\adapter\error.cpp:61
| function: `anonymous-namespace'::ConvertArchive3Error
| line: 0xc8d8731ce106f9cb, c:\jenkins_agent\workspace\ati-main-win-ati\529\archive\ver3\adapter\error.cpp:61, `anonymous-namespace'::ConvertArchive3Error
| $module: archive3_adapter_vs_39287
08.11.2022 21:34:34: +01:00 22204 E013C0005: Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bcedb
| file: c:\jenkins_agent\workspace\ati-main-win-ati\529\products\imager\demon\main.cpp:741
| function: main
| line: 0x9f2c53c72e8bcedb, c:\jenkins_agent\workspace\ati-main-win-ati\529\products\imager\demon\main.cpp:741, main
| $module: ti_demon_vs_39287

Start: 08.11.2022 21:34:33
Stop: 08.11.2022 21:34:34
Total Time: 00:00:01

I also started the same backup now to a USB-HDD. It started perfectly as I am used to. So the cause must be in the LAN connection to the NAS. But I have not changed anything there.

And is has made a backup without hickupping on the USB-external disk......

When creating a new backup to the NAS, I can find the destination directory through the Acronis GUI either after entering the IPaddress or offered as a NAS connection. But that does not make a difference. Stops shortly after starting, backup files with size 0 are created in the destination directory.

Connection and credentials to destination checked, are ok, connection established.

???

Franz47,

Are you continuing to use an existing backup task on a new machine?

If this is the case then I recommend that you follow the steps outlined in the Link below to remedy your issue.

Link

No, I created new backups from scratch

Did your username/password or destination change?  Newly created tasks should always be configured to a new backup folder.  If the same folder is used as previously created for other backups this can and does confuse the application and produce such errors.

Franz, has anything changed on your NAS recently, i.e. security changes?

Franz, check this prior posting from a few years back. A solution is posted which may help you.

I am very close to giving up....

What now baffles me completely:

I have deleted all users, groups, network shares etc from the NAS and created 1 single user with all possible rights.

I have the previous machine still running with an Acronis True Image 2019 installation. When checking credentials with a user/password combination which I have deleted from the NAS, it accepts them as connection and at least starts to backup. Maybe it will fail later but now it has been running about 15 min. When looking with Explorer in the directory where the backup is going, I can see a file growing in size. So the backup seems to work with credentials not any more existing on the NAS.

Then I try again with the 2021 on the new machine, create the whole backup from scratch, enter the user/password combination on the NAS which I had created as single user in addition to the admin. Connection ok. I can see the tree to the destination, create a new folder. When starting the backup - error again - access to file denied and a 0-sized backup file in the destination folder.

Or is my understanding of credentials when creating a backup wrong? I understand that the credentials of the NAS should be entered.

Franz, from what you wrote above, it sounds like there is some caching of credentials for your NAS going on, especially if you have deleted the same accounts on the NAS itself?

Are the shared folders on the NAS you are backing up to created as public shares?  If so, then Acronis may be accepting stored credentials while still backing up to public shares.

On my own Synology NAS, my backup storage folders are only accessible by using a dedicated NAS account / credentials.  I have no public shares on the NAS and only the dedicated NAS account user & password is entered into ATI for the backup tasks when selecting the destination.  Note: I have no matching user account on my Windows computers, so there can be no confusion over the account needed for the destination NAS.

I am still struggling without success for many hours. 

The NAS log says, apparently whenever the problem happens

smbd: CIFS: [ip-address of computer] connected to [destination folder name] as user [username]

smbd: CIFS: [ip-address of computer] closed the connection to service [destination folder name]

Does that hint at who is terminating the connection? The computer or the NAS?

Franz47,

I am going to take a guess here.  I am betting that your NAS dates back to 2014 or earlier.  I am also going to bet that your NAS is using SMB 1 and/or CIFS shares.

CIFS is obsolete and SMB 1 has been deprecated by Microsoft.  The new standard is SMB 3.0.  If your NAS does not support SMB 3.0 or at least SMB 2.0 you are likely going to have to upgrade your NAS.

My thinking here is that Windows detects your connection as insecure and closes the connection shortly after the connection is established.

Hi Enchantech, thanks for Your input.

I had thought about that too. As much as I remember, I had activated SMB1 on the new Win10 computer.

I enabled for sure again with Powershell as admin

Set-SmbServerConfiguration -EnableSMB1Protocol $true

I then double checked with Powershell as admin with

Get-SmbServerConfiguration | Select EnableSMB1Protocol

the answer was

EnableSMB1Protocol
------------------
              True
 

Then I checked to make a backup. Credetials accepted, connection accepted. Looked like starting to backup as usual, but after maybe half a minute "Access to the file is denied, edit connection settings etc"......as usual

When checking connection setting confidentials ok, connection ok.

The NAS latest NAS log lines (Asrock ist the destination folder)

Unfortunately this was not the solution

Franz47,

What version of Windows 10 are you running?  If you are still using 20H1 there is a known issue with enabling SMB 1 on that version.  Upgrading to 20H2 reportedly fixes the issue.

Problem solved....

I hav another piece of the same NAS. I checked whether it worked - it did. No error message when creating a backup.So the SMB1 protocol works on my computer.

Then I started to compare in detail the configs of the two NAS devices (D-Link DNS-320)

I created a network share on the NAS

Then I noticed that on the working NAS that in application management -> AFP service and NFS service were inactivated.

These items were activated on the nonworking NAS. I deactivated them and then the backup process worked as ever before.

Thanks to everybody trying to help!

Problem solved....

I have another piece of the same NAS. I checked whether it worked - it did. No error message when creating a backup.So the SMB1 protocol works on my computer.

Then I started to compare in detail the configs of the two NAS devices (D-Link DNS-320)

I created a network share on the NAS

Then I noticed that on the working NAS that in application management -> AFP service and NFS service were inactivated.

These items were activated on the nonworking NAS. I deactivated them and then the backup process worked as ever before.

Thanks to everybody trying to help!

Franz, glad to read of your success in resolving this issue.  NAS configuration is complicated by the number of variations of NAS that can be involved but thanks again for sharing your solution which may be of help to other users in the forums.

Great news Franz.  Glad to hear of your success and tha SMB 1.0 is working.  You may wish to consider moving beyond SMB 1.0 of your NAS devices support SMB 2.0/3.0 as it is an insecure - unsupported protocol long past its life span.

To run a computer without backup felt like leaving my home without mobile phone in the pocket. Not really dangerous but can cause some problems...so I am content everything runs again.

Moving to new devices does not seem worth the money for me as a private household. The backup NAS is off power and network most of the time.

Being curious I tried to find out which NAS devices support which SMB protocol. Searching some manuals for the string "SMB" resulted in no hit at all in several manuals, once I found SMB without further definition and once I found SMB2 and SMB3. But mainly the kept that stuff very secret.

Franz,

I had a look at the manual for the D-Link DNS-320.  This appears to be an older device using CIFS for network shares thus only supporting SMB 1.0 protocol.

You can verify this using Windows PowerShell.  From an admin PS prompt type Get-SmbConnection -ServerName XXXXXX where X is the hostname of the device such as DNS-320.  If PS gives no output then the connection is not active thus using Explorer to open a connection to a share on the device should trigger output from PS.  In the PS output look for Dialect for example 1.0.  This would confirm that connection is using SMB 1.0 which I suspect is what you will find.