the new version fix the error on Windows 10. However, it has the same error "the system cannot find the path specified" when running on Windows Server 2012R2
This also happens to some people using Server 2016. I've been unable to recreate the problem myself using Server 2016.
I don't have any evidence for what might be causing the problem. No person opening a trouble ticket on https://helpdesk.karenware.com has ever reported back that they checked the ACL Security permissions on the Destination Folder and its parent (perhaps they didn't find anything weird).
On Windows 10, the problem was the permissions inherited from the default root drive permissions being in a weird order. The user running Replicator didn't effectively have Read/List permissions for part of the parent root of the Destination Folder, so Replicator was failing when it checked for the existence of source folders and files as children of the Destination Folder. It could be fixed by changing the permissions, but in the end a solution was to have Replicator try to create every folder in the Destination first without checking whether or not it was already there. Obviously, this doesn't fix whatever problem is causing Replicator to fail on Server 2012R2 and 2016.
I tested 2016 as a stand along server, not in a domain controller situation.
I have also added "everyone" full control but the same error occur. I tested in a domain controller and member server of Windows 2012 but same error.
PS: Running in Windows 2003 server no problem at all.
Thanks for checking that. Hmm.
Is the Everyone permission the first one in the access control list?
Is that permission on the folder containing your Destination Folder?
If so, I continue to be stumped. I guess it could have something to do with the domain system, but Replicator makes Win32 calls which should be transparent to all that.
Please try using raw UNC file path prefix \\?\ before the name of the Source Folder and Destination Folder as a work around. For instance:
This has been reported to work for a user running Windows 8.1
Removed from the milestone for release v3.7.4 which was more of a hassle than one might think: Had to unlock it so I could edit the task (being Admin isn't enough), then I set up a custom policy so Sam could edit it again (needed custom policy because if Administrators wasn't in the policy then I couldn't save it). Also made public so people could see it. I've changed the default visibility of the Default space to be publicly visible.