The path could not be found - File System

​The Path 'X' Could Not Be Found (File System)

Error Example:

Error reading from entity '<entityName>': The path '<folderPath>' could not be found! Please specify a valid directory and check access rights.

Cause:

The path given in the Directory parameter does not exist, or possibly the user doesn't have access to it.

This seems very common with net drives with using the syncing service, as the local system account used by the service usually doesn't have rights to the folder. 

Another possible reason is that the password has been changed but the service account of the Layer2 Cloud Connector Service has not been updated.

Resolution/Workaround:

You should check that the location is accessible from the machine hosting the Cloud Connector. Then you should verify the account that will be syncing (either the manual user or the account on the sync service) has access to all the content in that location.

For issues specifically with sync service permissions, see the Advanced Troubleshooting section of Troubleshooting Scheduled Sync Issues.

Noted that permissions are handled differently with the service if using the IP address or the netname of the device (for network shares). With the IP, even if the service was properly set with an account with full access, it would still error unless I added 'Everyone' permissions to the folder. Switching to the netname would cause the error to go away.

If you are using the select statement to query the file system, directories with spaces in the name MUST have double-quotes ​ around them. For example:

select * from "\\l2nas\Firma\Vorlagen zur Überarbeitung"

In case you changed the password of the user, please update the service account of the Layer2 Cloud Connector Service and restart the service.