Errors referring to access to the job folder

When job is created, Agent starts monitoring the configured directory. If Agent cannot create the path or the folder is missing for a reason, Agent will give the following errors, list includes but is not limited to: 

Can't open the destination folder
Default folder location is not yet selected, undefined path macro
The queried directory path on the disk may have a different letter case than requested

Can't open the destination folder

It means that the shared folder is missing from computer or Agent was not able to create it. The error appears after the job is configured, if the Agent, in the course of syncing, does not find the share in its place. Check job's info and see share location for the Agent or its group. Then check Agent's drive and see if the folder is indeed located there.

In the Agent UI the error is reported as "Folder not found" 

For Sync Job:

Step 1. Restart the agent in the job run. It will create new share as per job's settings. Files will be re-downloaded from other agents.

Step 2 . Edit the job and point the agent to another folder. Use this option if the folder was moved to another location on computer, or if you want agent to sync a different folder. Once reconfigured, the agent will scan the folder, build folder tree and merge it with that on other agents. When merging, agents will compare files' hashes. Files with matching hashes won't be re-synced.

For transfer jobs:

Step 1 . Recheck paths in job configuration and make sure these are correct and don't have invalid tags or symbols. If all is OK, restart the job. 

Default folder location is not yet selected, undefined path macro

This error appears if the Agent was not able to resolve the mentioned path macro into a directory in a job. 

It usually happens if %FOLDERS_STORAGE% path macro is used, since there's no default resolved location for it as for other macros. The resolved path is to be defined in the Agent configuration file or in the Agent UI -> User Controlled > Default folder location. Therefore, Agents that connect to MC without config file (using IP address only) and don't have UI enabled (for example, Linux Agents don't provide UI) don't know not know how to resolve it. 

Possible solutions are:
1) don't use this macro for the Agents that connect to MC without config file. Use either a direct path or another macro when configuring the job.

2) use the config file. Download the config file from Management Console or create it manually:

- create a text file and name it sync.conf;
- put the following json there, minimal working is

{"folders_storage_path": "%DOWNLOADS%"}

This sets %FOLDERS_STORAGE% to be the same as %DOWNLOADS% path macro. You can use any macro you want or put direct path. Note: the correct syntax for Windows requires double slash, like this:
{"folders_storage_path": "D:\\My Folder\\Documents\\foo"}

Or for a Linux agent:
{"folders_storage_path": "/home/admin/My Folder/foo"}

- place JSON to C:\Program Files\Resilio Connect Agent (or the non-default installation path used) and restart the Service. On Linux, restart the process with --config /home/admin/correct/path/sync.conf parameter. 

3) Enable user interface (Linux Agents don't support it, including NAS) in the Agent config file and define the macro there.

The queried directory path on the disk may have a different letter case than requested

The error message usually appears for the job folders accessed via UNC paths. It appears if the job path on the MC and the job folder on the storage itself are different in the lettercase. 
To fix it, update the job or the folder on the storage so that the lettercase in the path matches. 

Error code is SE_FS_NO_FOLDER