On one server (Windows 2012 VM + SQL 2012, fully patched) it executes correctly, producing the file and updating a table with the record count.
On another server (same as above but physical instead of virtual) the package runs to completion but writes 0 for the record count and does not write an output file.
It doesn't give any indication of errors, it simply produces no output.
If I execute the SQL query in SSMS, I see the expected results displayed.
When I upgrade the package on the problem server, no errors are noted, but I get the same results (no output, no errors).
When I opened the project in VS 2012 and allowed it to upgrade, it said that all 3 script components required upgrading, so I allowed it. When I installed the resulting ispac file into an SSIS Catalog on the problem server, that package is then successful (produces output).
On another server (same as above but physical instead of virtual) the package runs to completion but writes 0 for the record count and does not write an output file.
It doesn't give any indication of errors, it simply produces no output.
If I execute the SQL query in SSMS, I see the expected results displayed.
When I upgrade the package on the problem server, no errors are noted, but I get the same results (no output, no errors).
When I opened the project in VS 2012 and allowed it to upgrade, it said that all 3 script components required upgrading, so I allowed it. When I installed the resulting ispac file into an SSIS Catalog on the problem server, that package is then successful (produces output).