Failed: The system cannot find the path specified.
Posted: Mon Feb 09, 2015 8:51 am
For a few weeks we are having several problems with several servers that are running BestSync Ultimate licenses.
Problem 1:
When we turn on the feature Backup, the entire tasks fails. If you look in the log file of the task you see the message “Failed: The system cannot find the path specified.” In the column Backup. If we disable the backup feature most of the task runs successfully.
Problem 2:
Backup is disabled, but still the message “Failed: The system cannot find the path specified.” is returned while the source (sFTP) is reachable and can be moved via WinSCP, so there is nog right or access problem. For this problem is no workaround.
Problem 3:
Same message “Failed: The system cannot find the path specified.” But all files are move to the correct destination, backup folder and mover from the source. But still the task log gives this message.
We are using multiple sFTP, BestSync, DFSr and NAS servers. So there is no shared component that is coursing this problem. The problems started a few weeks ago.
At than we where using a 2012 and a 2014 version. Last week we update to the latest version.
Is there an option for detailed logging?
Problem 1:
When we turn on the feature Backup, the entire tasks fails. If you look in the log file of the task you see the message “Failed: The system cannot find the path specified.” In the column Backup. If we disable the backup feature most of the task runs successfully.
Problem 2:
Backup is disabled, but still the message “Failed: The system cannot find the path specified.” is returned while the source (sFTP) is reachable and can be moved via WinSCP, so there is nog right or access problem. For this problem is no workaround.
Problem 3:
Same message “Failed: The system cannot find the path specified.” But all files are move to the correct destination, backup folder and mover from the source. But still the task log gives this message.
We are using multiple sFTP, BestSync, DFSr and NAS servers. So there is no shared component that is coursing this problem. The problems started a few weeks ago.
At than we where using a 2012 and a 2014 version. Last week we update to the latest version.
Is there an option for detailed logging?