Skip to main content

ATI failing with "Please close the application that may currently use the file"

Thread needs solution

Hi. I've just set up a new PC and retired the old one. I've moved ATI 2019 to the new machine and set up a backup. The backup writes to a NAS account - the same location and account used by the old PC (which is powered down now). Both the old PC and the new PC were/are scheduled to run the backup at 3:00 am. The old PC worked well and had no troubles unless the NAS was wonky. The new PC has trouble writing to the NAS share. I see the error shown in the snippet from the logs, below.

I also may see this error if I open ATI and click the Backup Now button. I see it if I don't have the share open on the desktop, and the backup runs fine if the share is open. (The old PC had no trouble running the backup and the share was not open there.) So it seems that ATI is having some trouble accessing the share on its own, but can access it if it's already open by me on the desktop.

When I Edit Credentials and click Test Connection I get a "Connection established" response. If I click the Connect button, the window closes without any error being displayed.

I've tried changing the password on the share and updating the ATI configuration accordingly, but that didn't help.

I'm at a loss to explain why I can connect to the share through the desktop but ATI can't (unless I've already connected). ATI is able to log out the share - if I connect to the share and run ATI, ATI will complete the backup, and then the share is logged out and I must log into it again from the desktop if I want to review the files there.

Any suggestions on where to look next will be appreciated.

Cheers,

Bob

 

Snippet from the logs:

2021-03-12T03:01:33:210-05:00 8420 I000B03F0: <bold>Create Backup Archive</bold><endl/><tabpoint value=30><indent value=4>From:    <indent value=10><textcolor value="navyblue">Disk 1</textcolor></indent><indent value=4><endl/>To file:    <indent value=10><textcolor value="navyblue">"\\FLINT\LuckyBackup\Lucky++ Disks C and D_inc_b1_s2_v1.tib"</textcolor></indent><indent value=4><endl/>Compression:    <indent value=10><textcolor value="navyblue">Normal</textcolor></indent><indent value=4><endl/>Exclude:    <indent value=10><textcolor value="navyblue">Files matching mask</textcolor></indent><indent value=4><endl/>Match criterion:    <indent value=10><textcolor value="navyblue">hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\Bob\AppData\Local\Temp, C:\Users\Bob\AppData\Local\Microsoft\Windows\INetCache, C:\Users\Bob\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\Bob\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\Bob\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\Bob\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\Bob\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\Windows\CSC, D:\xLights, D:\OBS-Captures, C:\EVE\SharedCache</textcolor></indent><indent value=4><endl/></indent><endl/>
2021-03-12T03:01:34:496-05:00 8420 I000101F8: Pending operation 173 started: 'Creating partition image'.
2021-03-12T03:01:34:690-05:00 8420 I00100000: Volume Tracker has failed to find changes on volume '\\?\Volume{ad4493b0-6182-4e1a-a520-b0e137ddcc4a}\'.
2021-03-12T03:01:34:737-05:00 11320 I00640000: Writing incremental version to file: Lucky++ Disks C and D_inc_b1_s3_v1.tib
2021-03-12T03:01:34:934-05:00 11320 E01E50023: Error 0x1e50023: Please close the application that may currently use the file: \\FLINT\LuckyBackup\Lucky++ Disks C and D_inc_b1_s3_v1.tib
| trace level: error
| line: 0x4d3f22948e29f19e
| file: c:\bs_hudson\workspace\790\products\imager\archive\impl\utils.cpp:199
| function: `anonymous-namespace'::GenerateGuiErrorWithPath
| line: 0x4d3f22948e29f19e, c:\bs_hudson\workspace\790\products\imager\archive\impl\utils.cpp:199, `anonymous-namespace'::GenerateGuiErrorWithPath
| $module: ti_demon_vs_17750
|
| error 0x40014: Access to the file is denied.
| line: 0x1d8eab676a3f6aba
| file: c:\bs_hudson\workspace\790\products\imager\archive\impl\operations\archive_message_callback.cpp:1169
| function: TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback
| line: 0x1d8eab676a3f6aba, c:\bs_hudson\workspace\790\products\imager\archive\impl\operations\archive_message_callback.cpp:1169, TrueImage::Archive::ArchiveMsgWriteCallbackProcessor::ProcessWriteCallback
| Path: \\FLINT\LuckyBackup\Lucky++ Disks C and D_inc_b1_s3_v1.tib
| $module: ti_demon_vs_17750
|
| error 0x40014: Access to the file is denied.
| line: 0xf35f747b3b21f903
| file: c:\bs_hudson\workspace\790\core\file\windows\winnt_dir.cpp:506
| function: winnt_dir::OpenFile
| line: 0xf35f747b3b21f903, c:\bs_hudson\workspace\790\core\file\windows\winnt_dir.cpp:506, winnt_dir::OpenFile
| function: CreateFileNoCacheW
| path: \\?\UNC\FLINT\LuckyBackup\Lucky++ Disks C and D_inc_b1_s3_v1.tib
| $module: ti_demon_vs_17750
|
| error 0xfff0: Access is denied
| line: 0xbd28fdbd64edb8f1
| file: c:\bs_hudson\workspace\790\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\790\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x80070005
| $module: ti_demon_vs_17750
 

0 Users found this helpful

Bob, welcome to these public User Forums.

I can only suggest focusing on the getting ATI 2019 to work with your NAS without having to map any Windows drive letter to the NAS first.

I personally do not ever map any drive letters to my own NAS as for me this represents a high risk when I want my NAS to store my important backup data.  I have a dedicated account that is unique to my NAS that is only used by Acronis for backups, where there is no Windows user account using the same name or password etc.  This works fine for me with all my scheduled backup tasks from multiple PC's on my home network.