I've got a Foreach (file) Loop Container set to go across all the files in a folder on a remote server. These are existing shares across numerous servers. When I use the current share path to the documents (\\servername\share$\folder) it loops across all the files but the flat file source gives me 0 rows of data. If I share out the folder directly (\\servername\folder) then it loops across all the files and brings back all the data in those files. No errors either way, but if I use the \share$ in the path the file source can't seem to get a handle on the files. The Foreach Loop doesn't care either way. Is there a known issue with using a hidden share UNC, or am I looking at the wrong issue?

The culprit must be the account you are running the package under, do you run it under the same account you have made the admin share with? Or tweak the security to allow that account.Arthur My Blog

I'm running the code under my own account. I can get to the location via the run line, same path.

How do you execute the package?Arthur My Blog

Inside Visual Studio, just telling it to Start Debugging.

Now try running it off the file system say using DTExec please. Arthur My Blog

Swapped from a flat file source to a script task (source) and it's able to use either file path. Was only after the metadata of the files anyway (not the contents) so this works. Odd about the file source though.

Glad to hear I helped, I am sure the File Source will work, too. Yes, it requires a refresh, because it caches the metadata. But so we know, there is no problem getting files from the Admin/hidden shares.Arthur My Blog