Skip to main content

Why does ATI 2017 suddenly access removable drive K:??

Thread solved

Hi!

   Why does ATI 2017 suddenly try to access files on removable drive K:?

   Drives H: - K: are the four removable drives in my memory card (MS, SD, CF, SMC) reader. The card reader has been present in the computer since before ATI 2017 was installed, and the backup in question has been running fine weekly for about nine months, until suddenly today ATI tried to access drive K:. Naturally ATI encountered an error, since there was no card in the card reader. Even if there had been, the file hadn't been present, that ATI was searching for.

The log file also says that the the backup was terminated by user. This is impossible. I was fast asleep at 05:21 today.

Attachment Size
ti-rpc-client.0_0.log 5.59 KB
0 Users found this helpful

Magnus, there is no reference to your removable drive K: in the log you posted - the references to K: shown in the log are internal messages from the Acronis code and the backup did complete successfully but hit a problem when attempting to perform a validation of the new backup file.

07/07/2019 05:12:40 :961  The following backups have been successfully created: G:\My disks_diff_b6_s6_v1.tib
07/07/2019 05:12:41 :027  Validate Backup Archive Location: G:\My disks_diff_b6_s6_v1.tib
07/07/2019 05:12:41 :037  Pending operation 4 started: 'Validate Backup Archive'.
07/07/2019 05:21:19 :780  Error 0x1e50023: The specified file does not exist: .
07/07/2019 05:21:19 :786  Cannot perform this operation in quiet mode. (0x103F1)

The normal backup log files are of type ti_demon rather than ti-rpc-client so not sure if there may be any other information in the ti_demon log for this task?

Thanks for the input Steve.

I looked in the ti_demon files instead. There was still an error message saying My disks_diff_b6_s6_v1.tib couldn't be found during the scheduled backup and during the manual validation there was an error (see below) approximately 42 minutes into the validation.

0x40001: Error occurred while reading the file

After I shut down and restarted the computer, the validation was successful though. The computer behaved oddly during shut down though. Power wasn't completely shut down (a USB light kept shining) until I disconnected the USB hub from the USB port. Odd!

Magnus, thanks for the update.  I guess the old adage applies here that is common for lots of support teams - do a power off / on or try again after restarting the PC etc...!

Glad the validation is now running successfully!