Using the new version 3.11 of the sync app i have the following issue:
I create a sync pair which should sync from a network share to a folder within the encrypted remote folder. When doing so I get the error message A folder watcher error has occurred (234) for \SERVERNAME\Foldername\Subfoldername. The same error occurres when using a network driveletter.
Do I miss something? Can’t the new app sync/backup from a networkshare?
I have the same problem and opened a ticket. My network share is a mapped drive to my NAS which worked in V2. They changed their approach in how they identify files changes to enable the Windows App (assuming that is what you are using) to synch. After much questioning, they identified the limitation depending on how they call a Windows API.
Open a ticket and include that others have replied with the same problem. You can refer to my ticket, Ticket [#LYS9CMLF], as that is where we are chasing the problem.
My experience is that synch pair will not synch anything until they resolve the problem. I am too dead in the water at this time. Can you confirm that is the case for you?
Yes. I have the same configuration and the same problem as you. For Windows, I know that it can track any file exchange within a journal. But these journals can only be used with local drives. I hope they have not used this mechanism. I will open a ticket and refer to yours as well. Thank you very much for your reply!
It is very sad to see that an “improved” version kills a functionality that was present in an older version…
Can anybody confirm that the problem also exists when using Linux?
If under Linux there is not such a problem I would create a Linux-VM and let it run 24*7 to sync.
IceDrive has provided me with a special debug version that apparently generates extended debug information.
I tried it out and gave them the log file. I hope they can fix the problem.
Thanks for the update. I need to reach out within my ticket and ask for the .exe of version 2.x so I can reinstall with the version to get everything working again. I have been dead in the water for 8 or 9 days with no synching of content.
They have not offered an alternative as they investigate but I am risk when my NAS data is not stored in the cloud timely.
This is now week number three. Since then, I haven’t had a chance to back up my NAS data to my IceDrive.
This is so bad. You at IceDrive shouldn’t be surprised if users migrate and switch to a competitor.