cvoss85 (5/26/2016)

---

I have an SSIS package which includes a foreach loop to find a file and then archive it to a different folder once other steps are completed.

When I execute the package in Visual Studio 2012 Shell, the file is found and is eventually archived. However, I want this to be part of a job in SQL Server Management Studio 2014. So I execute the package there, and it succeeds, but the file was not found...thus it is still in the same source folder.

I'm not sure if there is something I should look for in the connection managers/parameters within the SSMS package configuration screen, or if there is a disconnect between each when it comes to loops (sort of like 32-bit versus 64-bit runtime, I think).

So question is...why would this happen?