When running a package in Visual Studio that is using COZYROC File Transfer Task and a File Connection Manager pointed to Example - E:\Some_Directory, the package runs fine. However, after deploying the package to SQL Server Agent, the following error message is encountered in the job: "Local path is not a file path or you do not have permission to access it". The error message is coming from File Connection Manager. Attempts to use the UNC path results in same error message. If you navigate to the directory directly from the machine running the job you might be able to access the path E:\Some_Directory, and this gives the perceived impression that the necessary permissions are given to this directory and the job should therefore be able to access the directory without error.  Further investigation shows that removing COZYROC File Transfer Task from the equation and using the same File Connection Manager in conjunction with Microsoft's File System Task produces the same error message when deployed and run in SQL Server Agent job.

'Local path is not a file path or you do not have permission to access it.'

If you’re running the package via a scheduler such as SQL Agent, you may run into perceived permission problems, or reports that files cannot be found. The issue with schedulers such as Agent is that they run under a “service account” that does not have access to mapped network drives. Creating a proxy account and assigning it to the SQL Server Agent job would likely address the issue.

Please refer to the following link for more info:

https://masudprogrammer.wordpress.com/2015/12/10/ssis-ssis-mapped-network-drives/