sync.ffs_lock stopping the batchjob?

[echdareez]

Hi there,

Had a job with a client and asked him to support first with the Donation edition. So he did and went off to create an automated sync job (at the base a Powershell script which checks which PC it is being run and if the USB drive is connected and so on... )

PC1 went flawlessly and modified the PS script for PC2. But noticed that the step which runs Freefilesync with the batchjob, didn't do a thing. Thought it was the context or the quotes but... after digging through it, I noticed that Freefilesync gave the following error when I tried to start that job manually (Portuguese people so copying as I saw it) :

The Portuguese text:
"Aguardando enquanto o diretório está em uso: C:\sync.ffs_lock"
or, more naturally in English:
"Waiting because the directory is currently in use: C:\sync.ffs_lock"

I have a hunch that this same behaviour is why FFS is apparently not 'starting'. So I did an "attrib -s -h -r C:\sync.ffs_lock" and also a Remove-Item C:\sync.ffs_lock - restarted the PC, restarted FFS and ... same error...

Would appreciate any pointers to troubleshoot this :-)
Dimi

[Plerry]

Read the LockDirectoriesDuringSync description.
When the LockDirectoriesDuringSync flag is set to "true" (the default value), you must have write access to both the left and right base location.
By the way: the same holds if you checkmark "Use database file to detect changes" (the default value) in your Synchronization Settings (F8).