FFS: Unresolved Conflicts "The items have different names"

[itman2000my]

Good morning.

Can FFS automatically handle this conflict? ie. filename PO240184 AL Aqsa Carpets.pdf != PO240184 AL AQSA CARPETS.pdf


The following items have unresolved conflicts and will not be synchronized:
Folder pair: E:\ <-> gdrive:\srv02.backup@worldvision.org.my\Drive E
6. FINANCE\Finance FY24\Purchase Order\PO\PO240184 AL Aqsa Carpets.pdf
6. FINANCE\Finance FY24\Purchase Order\PO\PO240184 AL AQSA CARPETS.pdf: Cannot determine sync-direction:
The items have different names, but it's unknown which side was renamed.
6. FINANCE\Finance FY24\Purchase Order\PR & Quotation\PO240184-AL Aqsa Carpets
6. FINANCE\Finance FY24\Purchase Order\PR & Quotation\PO240184-AL AQSA CARPETS: Cannot determine sync-direction:
The items have different names, but it's unknown which side was renamed.

[xCSxXenon]

If you use "mirror" syncing, FFS can probably handle that automatically. Honestly, the whole point of an "unresolved conflict" is because FFS can't handle it automatically, so it needs you to handle it yourself.

[itman2000my]

Im using update one way, source to destination and no deletes.
Hence, if the filename is different, ie, lower case vs upper case, etc. then FFS should just consider the file is 'NEW'.

TQ

[xCSxXenon]

Then you may want to disable "Use database to detect moved/renamed files"
The file IDs for the two are likely the same, so FFS knows they are the "same" file, but then throws the error because it doesn't know which is renamed.

[Zenju]

Then you may want to disable "Use database to detect moved/renamed files"

No, it's the opposite. Using the database prevents this conflict and correctly detects a direction. But only starting with the second sync, obviously, because it needs to compare against the former state. OP apparently synced these two folders for the first time, so FFS cannot use the DB yet.

[itman2000my]

Good morning. I disabled "Use database to detect moved/renamed files" as @xCSxXenon advice, but still getting the issue. Also, the sync hv been going on for sometime with "Use Database" ENABLE. I also got the same error.

As of last night sync, I got the below error:
The following items have unresolved conflicts and will not be synchronized:
Folder pair: E:\ <-> gdrive:\REDACT\Drive E
13. ALL SHARED FOLDERS\17. Finance\Event Collection Report\FY24\2024-09-14 Life Conference CEO posted
13. ALL SHARED FOLDERS\17. Finance\Event Collection Report\FY24\2024-09-14 LIFE CONFERENCE CEO posted: Cannot determine sync-direction:
The items have different names, but it's unknown which side was renamed.
13. ALL SHARED FOLDERS\17. Finance\Event Collection Report\FY24\2024-2-19 Hilton KL
13. ALL SHARED FOLDERS\17. Finance\Event Collection Report\FY24\2024-2-19 HILTON KL: Cannot determine sync-direction:
The items have different names, but it's unknown which side was renamed.
3. IMP\IMP Data\0. General\Orientation\Intro to WVM IP - POs Visit.ppt: Files have the same date but a different size.
Date: 19/09/2013 11:57:44 AM Size: 13,807,616 <-
Date: 19/09/2013 11:57:44 AM Size: 13,807,104 ->


Batch Job Setting:

<?xml version="1.0" encoding="utf-8"?>
<FreeFileSync XmlType="BATCH" XmlFormat="23">
<Notes/>
<Compare>
<Variant>TimeAndSize</Variant>
<Symlinks>Exclude</Symlinks>
<IgnoreTimeShift/>
</Compare>
<Synchronize>
<Differences LeftOnly="right" LeftNewer="right" RightNewer="none" RightOnly="none"/>
<DeletionPolicy>RecycleBin</DeletionPolicy>
<VersioningFolder Style="Replace"/>
</Synchronize>
<Filter>
<Include>
<Item>*</Item>
</Include>
<Exclude>
<Item>\System Volume Information\</Item>
<Item>\$Recycle.Bin\</Item>
<Item>\RECYCLE?\</Item>
<Item>\Recovery\</Item>
<Item>*\thumbs.db</Item>
<Item>*\.DS_Store</Item>
<Item>*\~$*</Item>
</Exclude>
<SizeMin Unit="None">0</SizeMin>
<SizeMax Unit="None">0</SizeMax>
<TimeSpan Type="None">0</TimeSpan>
</Filter>
<FolderPairs>
<Pair>
<Left Threads="10">E:\</Left>
<Right Threads="10">gdrive:\REDACT\Drive E|timeout=60</Right>
</Pair>
</FolderPairs>
<Errors Ignore="true" Retry="6" Delay="20"/>
<PostSyncCommand Condition="Completion"/>
<LogFolder>C:\FreeFileSync\logs</LogFolder>
<EmailNotification Condition="Always">REDACT</EmailNotification>
<GridViewType>Action</GridViewType>
<Batch>
<ProgressDialog Minimized="true" AutoClose="true"/>
<ErrorDialog>Show</ErrorDialog>
<PostSyncAction>None</PostSyncAction>
</Batch>
</FreeFileSync>

[gfreesync]

I have had this issue for the last month PIA for sure.
I was finally able to resolve the issue. I noticed that folder name on the computer had an upper case letter versus the backup device had lower case. With a recent window 10/11 case sensitivity for folders became an option. I did check to ensure it was not inadvertently turned on it was not. Now it is possible that the folder name was updated between backups TBH not sure. I did update the folder names to match case wise and that resolved the issue.

This sample came from ChatGpt.

To test use the command prompt (admin) on the folder in question.

fsutil file queryCaseSensitiveInfo "C:\path\to\directory"

I did confirm it was not enabled.

FWIW: I've had the same issue when changing folder names from the standard hyphen - to medium dash – ­
AltKey + 045 - Standard Hyphen
AltKey + 0150 – Medium Dash
AltKey + 0151 — Long dash

1. Archie Shepp – Three For A Quarter One For a Dime (medium dash)
versus
2. Archie Shepp - Three For A Quarter One For a Dime (Hyphen)

The backup software does not distinguish between the two and receive this error Warning.

Some files will be synchronized as part of multiple folder pairs.

[Zenju]

I disabled "Use database to detect moved/renamed files" as @xCSxXenon advice, but still getting the issue.

This is expected: viewtopic.php?t=11618&p=45818#p45325