felix-x1t3-11 (Windows 11 Pro) <---> EC2 (Windows Server 2019)
There is no improvement, but also no additional errors.
I can imagine that the access denied errors stem from an application locking them (Windows, sigh), but then I would expect them to go away once I close the application. That did not happen, and I think they also appeared right away after the initial sync.
Something perhaps important: On felix-x1t3-11 and on linux.f76.eu, the shared directory is nested in another share. I have done that before, without issues. For security reasons, I don’t want to share everything to EC2.
No, when files are locked, you should see an error message saying The process cannot access the file because it is being used by another process. In your case, Syncthing has no permissions to access the files.
It happily syncs into a new directory, and then it suddenly complains about permissions. I never had that issue before, but then this is the first time that I run Syncthing on Windows Server 2019, and I realize that it set up its own user.
I cannot see what is the problem, but Windows permissions are too complex for me. Here is some info about the permissions for the first failed file:
I see now that the windows installer linked from the Syncthing web site, is provided by a third party. There is a lot of documentation that I didn’t read. In particular, when Syncthing is installed for all users and runs as user SyncthingServiceAcct, additional configuration is necessary, to avoid permission issues. However, I still don’t understand what went wrong, because I had all files in SyncthingServiceAcct’s user directory.
Anyhow, in the end, I reinstalled Syncthing as user Administrator. That makes more sense on this single-user (and single purpose) system, and it solved the issue.
