Skip to content
English
Manage and Create Tickets
  • There are no suggestions because the search field is empty.

ServerSync Two-Way Sync Uploads Stalling with "Case Sensitive Path Check Failed" Warnings Due to Folder Name Case Mismatches

Original Question or Issue:

 ServerSync two-way synchronization stopped working unexpectedly. The customer reported that files from the local folder were no longer being uploaded to FileCloud, although synchronization had previously been functioning normally. 

Environment:

  • Product - FileCloud ServerSync
  • Version - 23.242.0
  • Platform - Windows

Steps to Reproduce:

  • Configure multiple ServerSync folders using Two-Way Sync.
  • Allow synchronization to run normally.
  • Observe a scenario where uploads from the local folder to FileCloud stop unexpectedly.
  • Review ServerSync logs during the affected timeframe.
  • Restart the ServerSync service.
  • Observe that synchronization resumes successfully.

Error or Log Message:

Observed in ServerSync logs:

Case Sensitive Path Check Failed

Defect or Enhancement Number:

 

Cause:

Development analysis identified multiple folder path case mismatches between the local file system and the corresponding folders stored in FileCloud.

These mismatches generated:

Case Sensitive Path Check Failed

warnings in the ServerSync logs.

At the time of investigation, there was insufficient logging available to definitively determine whether the case-sensitive path validation warnings directly caused the upload synchronization interruption.

The root cause of the upload stall could not be conclusively established from the available logs.

Resolution or Workaround:

  • Verify that local folder names exactly match the corresponding FileCloud folder names, including uppercase and lowercase characters.
  • Review ServerSync logs for any "Case Sensitive Path Check Failed" warnings.
  • Restart the ServerSync service if uploads appear stalled.
  • Collect the following for further investigation if the issue reoccurs:
    • Complete ServerSync logs from the AppData directory
    • syncclientconfig.xml
    • Approximate timestamp of the issue
    • Examples of affected folders and files

Notes: