I have a Data Flow and a Script Task in a For Each container. When I use the Debug option to run it, everything works great. When I run the SSIS package as a job, it succeeds, but gives me the "File enumerator did not find any files that matched the file pattern, or the specified directory was empty." error. All signs point to a permissions issue, BUT, the SQL Agent account has permission to the folder. I have even moved it to another folder that the same id imports from in other jobs, with the samre result. The path is in the package, not in a config file.

It's just importing each ".csv" file from a folder into a table. The script task is renaming and moving the files.

At this point, make sure that you have granted the service account access to all parent folders of the one you are trying to scan. The enumerator will run into issues if it can't read a parent directory.Phil Brammer | http://www.ssistalk.com | Twitter: http://twitter.com/PhilBrammer

It has access to the parent folders. Also, the same job is writing files to the same folder it won't import from.Brent

It indeed sounds like a permission issue. Two suggestions to test: 1) Use Process Monitor (Successor of filemon) to check what files are requested (and by whom, with or without success): http://technet.microsoft.com/en-us/sysinternals/bb896645 2) Use a Script Task (before the foreach) to check whether you can access a certain file in that folder. With a try catch you will get some info if it fails. (Example of accessing a file: file props and try opening. And and a try catch example in a Script Task)Please mark the post as answered if it answers your question | My SSIS Blog: http://microsoft-ssis.blogspot.com