Profile > Last Result: FAILED (not started)

[p1ea]

Just started getting this error whenever attempting to start a profile that's been working until just a few days ago, though no changes were made. This happens whether starting on schedule or manually in background mode. No log file or email alert of the failure is generated, though I feel there should be, as I would not have known about the problem had I not had a need to go to the UI to make a change to another profile.

When starting manually in attended mode, I get the following error:

Code: Select all

Access to these paths was not possible:
sftp://backup.server.com/backups/baksrv1/FILES/2013 .: The system cannot find the path specified.
sftp://backup.server.com/backups/baksrv1/FILES/2013 ..: The system cannot find the path specified.


However, there is no "2013" folder neither on the source nor destination. Nor has there ever been in the past. All files are in the root dir of that profile "FILES". After clicking continue on the above dialog, I'm presented with the Preview window, listing most files with a RENAME action such as:

Code: Select all

2103 B2D000170.bkf        RENAME TO B2D000170.bkf
2103 B2D000171.bkf        RENAME TO B2D000171.bkf
...


This is repeated for all files within the folder. Looks like Syncovery realizes they're the same files and suggests renaming them on target to match the source, but the source does not have the "2013" prefix in the filenames.

At the end of the list, there is:

Code: Select all

Filename       Action        Right Date
2013 .         DELETE        12/5/2013 11:40 AM
2013 ..        DELETE        12/3/2013 10:02 AM


This suggests these files exist on both sides, but there isn't.

Thanks for your time,
Peter

[p1ea]

Interesting... I restarted the server and the Syncovery service won't come up without anything logged anywhere. I was just browsing through some of the older emailed logs and noticed it was down to 2 days on the last one I received, which would put it at 0 today. I actually considered this before, but it says there are 27 days left for evaluation on the Ordering tab, so I dismissed that possibility.
This is a somewhat cryptic way to let users know their eval expired, no? Reporting weird failures during job runs; not having anything logged or displayed when the service shuts down; showing 27 days left in the GUI.

Anyway, Syncovery has been working good until now, so I will be buying it. Just wish I didn't have to spend two days of my time troubleshooting the weird error.

[superflexible]

The weird errors from your first message are not related to an expired evaluation period. The scheduler not running might be, although the GUI should also show you the remaining time.

Please let me know if problems remain. The sftp errors may have to be analyzed with more detailed logs.