I installed Syncthing on two Windows servers to run like DFS, using version 2.0.10 on both.
I had permission issues initially, which I no longer have by adjusting them.
But now, I get this type of message on certain files (not all...) on the original server:
BCB\ARGUS\2025\Offres Fetes fin d'année\Argus LMO Cal Avent.indd syncing: finishing: setting metadata: Access denied.
And on the target server, I do have a file that copies itself called: ~syncthing~Argus LMO Cal Avent.pdf.tmp
but it won't name it the same as on the source server.
If I change the extension from .tmp to .pdf, the file opens fine.
How can I fix this problem?
Syncthing creates a tmp file and then renames it when the sync is complete. If it’s an existing file, Syncthing renames the tmp file to the correct name, overwriting the previous version of the file.
It seems likely that Syncthing has permission to write but not overwrite files.
Thanks for your answer,
Yes you’re right, but it use my account that is domain admin.
I had right problems before, I explicitly give it full control rights to folders, subfolders and files, and the problem is still here
File permissions can be super weird on Windows. Use Get-ACL in PowerShell or icacls in the Command shell to see what those permissions are in that directory, and for the individual files.
I also recommend that you confirm that the process owner of Syncthing is the account you think it is; from an elevated Command or Powershell prompt, use tasklist /v | findstr sync to confirm that. If you use a not-elevated shell, you won’t use the user that owns the process.
I agreed with @calmh — for each Folder, click on Edit / Advanced and let us know your settings. I recommend that you try turning off Sync Ownership and Send Ownership. If that doesn’t work, considering turning on Ignore Permissions