11.0.1: Root Dirs Read - Error New Files Exist At Source And Destination

English Support for Syncovery on Windows.
Post Reply
M_Meyer
Posts: 25
Joined: Mon May 04, 2020 8:18 am

11.0.1: Root Dirs Read - Error New Files Exist At Source And Destination

Post by M_Meyer »

Hi,
today, I updated to 11.0.1 from 10.16.6.
Now, I get
"Root Dirs Read - Error New Files Exist At Source And Destination - Canceling Due To Exact Mirror Configuration @ 0000000002ADAF80 Checkpoints: BuildFLE/BuildFLE, preparation not OK."
for one profile.
The logfile does not show affected files.

What can I do to resolve this?
tobias
Posts: 1933
Joined: Tue Mar 31, 2020 7:37 pm

Re: 11.0.1: Root Dirs Read - Error New Files Exist At Source And Destination

Post by tobias »

Hello,
this is a new feature in Syncovery 11. Please check the Exact Mirror configuration dialog. There are new settings on the tab sheet "Newer Files On Destination Side".

Most likely, you chose the radio button "Reverse Copying Direction if Situation is 100% Clear". But the situation is not 100% clear - newer files exist on both sides.

The old Syncovery 10 behavior would be "Overwrite Newer Files - Replace With Files From Source Side".

Maybe you can change the radio button and then run the job manually in Attended Mode and look at the Sync Preview to determine if the error was justified, i.e. there is really a file with a newer modification date and time on the destination or not.
tobias
Posts: 1933
Joined: Tue Mar 31, 2020 7:37 pm

Re: 11.0.1: Root Dirs Read - Error New Files Exist At Source And Destination

Post by tobias »

Unfortunately even for a manual run, you need to change the radio button to "Overwrite Newer Files".

I will add an interactive prompt what to do for manual runs.

The canceling was more intended for scheduled runs.
M_Meyer
Posts: 25
Joined: Mon May 04, 2020 8:18 am

Re: 11.0.1: Root Dirs Read - Error New Files Exist At Source And Destination

Post by M_Meyer »

I have checked - the setting is already "Overwrite newer files - replace with files from source side"
I have now changed the setting to "Leave such files alone - do not replace", ran the job manually in Attended Mode and confirmed overwriting the files.

But it is strange - with this "Overwrite newer files" setting, it should not occur, right?
tobias
Posts: 1933
Joined: Tue Mar 31, 2020 7:37 pm

Re: 11.0.1: Root Dirs Read - Error New Files Exist At Source And Destination

Post by tobias »

Hello,
yes correct, it should not occur ... probably there is a bug. I am testing this some more now. Could you maybe send the log file where it happened to support@syncovery.com?
tobias
Posts: 1933
Joined: Tue Mar 31, 2020 7:37 pm

Re: 11.0.1: Root Dirs Read - Error New Files Exist At Source And Destination

Post by tobias »

Maybe it was a bug migrating the old profile, I think if you edit the job once and choose "Overwrite Newer Files" it will be fine in the future.
donw146
Posts: 3
Joined: Fri Apr 10, 2020 6:59 pm
Location: Canada

Re: 11.0.1: Root Dirs Read - Error New Files Exist At Source And Destination

Post by donw146 »

I had the same problem. Editing the affected profiles, entering exact mirror config, confirming Overwrite newer files - Replace With Files From Source Side was checked and clicking OK fixed the problem.
tobias
Posts: 1933
Joined: Tue Mar 31, 2020 7:37 pm

Re: 11.0.1: Root Dirs Read - Error New Files Exist At Source And Destination

Post by tobias »

Hello,
many thanks, I will make sure that old profiles are loaded correctly in the next update.
M_Meyer
Posts: 25
Joined: Mon May 04, 2020 8:18 am

Re: 11.0.1: Root Dirs Read - Error New Files Exist At Source And Destination

Post by M_Meyer »

tobias wrote: Fri Oct 18, 2024 12:46 pm Hello,
yes correct, it should not occur ... probably there is a bug. I am testing this some more now. Could you maybe send the log file where it happened to support@syncovery.com?
Logfile is sent - just in case it is still needed...
tobias
Posts: 1933
Joined: Tue Mar 31, 2020 7:37 pm

Re: 11.0.1: Root Dirs Read - Error New Files Exist At Source And Destination

Post by tobias »

Hello,
many thanks, yes this was helpful to confirm what happened. It's fixed in version 11.0.2.
Post Reply