Serious Error: Target folder "\\ServerName\F$\PCName" already existing.

[parkerh]

Using Windows 7 batch file triggered on daily schedule by Landesk. Task runs under domain account which is Admin account on all PCs and on Server. Process works fine on most PCs, but many are getting the error shown below. Is this bug, a know problem, and/or is there a possible workaround?

In the first warning, cannot find the folder, the folder does already exist.
The second error appears as bug, because it should not be an error if target already exists.
*************
8:06:51 PM] Info: Starting comparison
[8:07:11 PM] Error: Cannot find the following folders:
\\ServerName\F$\PCNAME\
You can ignore this error to consider each folder as empty. The folders then will be created automatically during synchronization.
[8:07:26 PM] Info: Synchronizing folder pair:
D:\
\\ServerName\F$\PCName\
[8:07:26 PM] Serious Error: Target folder "\\ServerName\F$\PCName" already existing.
[8:07:26 PM] Error: Synchronization completed with errors

[Zenju]

The second error is a safety mechanism: FFS did not find the folder when doing the comparison, but during creation it turns out it is actually existing. If FFS would ignore this error it would continue synchronization based on the wrong assumption that the folder is empty.

[parkerh]

Thank you for quick response, and your reply makes sense. Now I have to solve the first problem, as the server share does exist, when FFS says it does not. The problem probably is due to network contention. Is there a timeout parameter within FFS that can be increased? Will Retry count impact the detection of the target (network) folder?

[Zenju]

If the reason why the folder was not found the first time is only temporary, then setting a retry count and delay in FFS'S global settings should help.