Errors with file permissions

Different operating systems (Windows or Linux) handle file permissions in

its own way. In general, if some permissions are absent, program is not able to either read some files, acquire a unique lock or write files to some location.

In case of different errors, you can encounter the following notifications in the Management console.

1. There is not enough permission to access the file

Error code SE_FS_FILE_PERMISSIONS_ERROR.
Resilio Connect agent shows an error in the Management console if it doesn't have enough permissions to read some files in the job. The error looks like the following:

Note

If you need a list of all files locked, you should check the agent's event log.

2. Don't have permissions to write to the selected folder.

Error code SE_FS_NO_PERMISSIONS.
For Synchronization job it's not necessary to create the directory in advance, admin can point it to a non-existing folder and the Agent will create path to it. In case of agent could not create job's path due to access error, you will see the following error

This means that the agent was not able to create a job's folder and you need to check the agent's permissions.

3. File '%s' is locked (renamed to "File is opened by another application, agent can’t process it" in 4.1.0)

Error code SE_FS_LOCKED_FILES.
This is a Windows-specific error as Linux doesn't offer an exclusive file lock. If you encounter such error, it means that some other application obtained an exclusive lock on file in the sync job.

As a simple proof that the file is locked indeed, try opening this file in the notepad. You should see the following warning.

To find out what exact process locked the file, Process Explorer from Sysinternals Suite is the best. Run Process Explorer as an Administrator and open Find -> Find Handle or DLL...

Paste in the file's path and press the Search button, you should see the process which locked the file.

4. Unable to list folder children.

Error code SE_OPERATION_ABORTED

Job type-specific

You can only encounter this error in either distribution or consolidation jobs.

It happens when one or more sub-folders of the folder added to the job don't have read permission. Check the troubleshooting section below for more info.

Another possible reason is that file was deleted from source during transfer before it was actually delivered to the destination.

Troubleshooting permissions errors

Basically all permissions errors boil down to one thing - the user that runs the agent does not have read or write permissions to the mentioned objects. Below are some specific steps to troubleshoot.

WINDOWSLINUXOS X

In Task Manager, check the User who is running Resilio Connect Agent.

Knowing the name of the file which reports not enough permissions, go to file's properties -> Security -> Advanced -> Effective Access

Check the user who is running Connect Agent

and see if the user has enough permissions for the files in the job

Also, it's possible to try and open the file in Terminal, most likely the same error will pop up:

Find the PID of Resilio Connect agent either in the Activity Monitor or Terminal: Then you can check folder permissions in the Finder.

Extended file attributes

MacOS supports extended file attributes. They are not shown in the find, but you can check them from the Terminal using xattr command.