I cannot open a backup scheme while the network destination is offline.
I start ATI 2017 and select a file based backup scheme. The destination is a NAS which is offline, but I'm not interested in accessing the actual backup file. I want to make a change to the backup scheme only. When I click on either "Files and folders" or Options, I get a message box that says "Error occurred while opening the file." and the error code is 0x00040007. I click on ignore, but I can't access the backup scheme.
I have one Disk based backup that has never run. When I try to edit that one, I get a message "Error occurred while creating the file." But when I ignore that I can still edit the backup scheme.
Is this normal? I don't recall that happening in ATI 2014 which was my last version.
Oh yeah... this is a Windows 10 Pro machine.
Thanks.


- Anmelden, um Kommentare verfassen zu können

It doesn't make sense that this should be normal. What if I want to change the destination because of a problem with my NAS? I can't do it. There's no way I can change anything about the scheme.
- Anmelden, um Kommentare verfassen zu können

Bruno, I have just checked this behaviour on my laptop running ATIH 2017 New Generation (build 6116) where I create a backup to a removable USB drive then disconnected the backup drive.
At that point I am not allowed to make any changes to the task configuration without the removable drive being reconnected.
What I was able to do is to click on the options to the right of the task name and choose to Clone settings which then created a duplicate of the locked task prefixed by (1) where I could modify any of the settings, including the Source or Destination or any of the Options. This is possible because the new cloned task has not been executed for the first time. So using this method, I could choose a different NAS or other backup destination.
- Anmelden, um Kommentare verfassen zu können

Thanks very much for verifying this, Steve. I've been doing lots of configuration on a new PC and at least I know now that I didn't screw anything up to cause this error.
I suspected the Clone settings would do it... just hadn't gotten around to it yet.
- Anmelden, um Kommentare verfassen zu können

You are welcome Bruno, I am not sure that I like this change in behaviour either, but guess that it doesn't really affect me very much as most of my backup targets are either local or on the network plus I only tend to do scheduled backups on my desktop / tower systems which are plugged in permanently to the network etc.
- Anmelden, um Kommentare verfassen zu können