Kostas,
As you suggested I just upgraded from SyncBackSE ver. 6 to ver. 7. Since I did that I've had 2 problems.
The first is that the SyncBackSE icon does not appear in the system tray. I checked that the icon was set to display as described in your help topic "The SyncBack icon is not shown" and found that Windows was set correctly. All icons for other applications that I expect to see are visible. The SyncBackSE options "Minimize to tray" and "Minimize on close" are set. The icon is not shown whether or not SyncBackSE is open. Previously with ver. 6 the SyncBackSE system tray icon was always displayed.
Secondly the original problem is still there. Last night when SyncBackSE ran it stalled backing up from internal drive F: to external USB drive O:. It shows the backup item as running but no I/O was occurring on drives F: or O:. When I view drive O: (the target drive) with the explorer I can navigate the directory structure but if I go too deep I get an error. If I cycle power to O: I can then navigate the drive from the explorer completely with no problems, but SyncBackSE stays stalled. It never finishes the backup, never does I/O to O:, and never reports an error. If I click the Stop icon it closes the log and shows the backup aborted, and I can then run the backup successfully.
As I said previously I'm having problems with USB external drives not working right on this PC so that's not a surprise. I'm working on that but haven't yet figured out how to fix it. However other programs that access USB drives detect that an error has occurred and report the problem. SyncBackSE just stalls, doesn't do subsequent backups, and never reports anything.
I had this same problem with ver. 6, but it was worse because I could not stop the stalled backup or clear the running status. It's nice that I can now clear the error, but it's a problem that SyncBackSE stalls without completing the stalled backup or subsequent backups and without indicating an error.
How can I get SyncBackSE to stop and report an error when this problem with drive O: occurs?
Thanks,
Mike
As you suggested I just upgraded from SyncBackSE ver. 6 to ver. 7. Since I did that I've had 2 problems.
The first is that the SyncBackSE icon does not appear in the system tray. I checked that the icon was set to display as described in your help topic "The SyncBack icon is not shown" and found that Windows was set correctly. All icons for other applications that I expect to see are visible. The SyncBackSE options "Minimize to tray" and "Minimize on close" are set. The icon is not shown whether or not SyncBackSE is open. Previously with ver. 6 the SyncBackSE system tray icon was always displayed.
Secondly the original problem is still there. Last night when SyncBackSE ran it stalled backing up from internal drive F: to external USB drive O:. It shows the backup item as running but no I/O was occurring on drives F: or O:. When I view drive O: (the target drive) with the explorer I can navigate the directory structure but if I go too deep I get an error. If I cycle power to O: I can then navigate the drive from the explorer completely with no problems, but SyncBackSE stays stalled. It never finishes the backup, never does I/O to O:, and never reports an error. If I click the Stop icon it closes the log and shows the backup aborted, and I can then run the backup successfully.
As I said previously I'm having problems with USB external drives not working right on this PC so that's not a surprise. I'm working on that but haven't yet figured out how to fix it. However other programs that access USB drives detect that an error has occurred and report the problem. SyncBackSE just stalls, doesn't do subsequent backups, and never reports anything.
I had this same problem with ver. 6, but it was worse because I could not stop the stalled backup or clear the running status. It's nice that I can now clear the error, but it's a problem that SyncBackSE stalls without completing the stalled backup or subsequent backups and without indicating an error.
How can I get SyncBackSE to stop and report an error when this problem with drive O: occurs?
Thanks,
Mike
Statistics: Posted by MikeA01730 — Mon Jun 06, 2016 5:42 pm