I have quite a basic SSIS package that clears down a directory, loads a list of stored procedures into an object variable, then using a script task executes them one by one. The script task outputs each of the results into a CSV file and also generates a log file should any of them fail.
When executing the package locally it runs fine. After I export it to production and execute it the report displays a successful run but the script execution takes 0 seconds and generates nothing (including the log file). I have enabled full logging for the package and again, this shows a successful execution but it appears the script task is not running.
My first thought was a version mismatch between dev and production, which is still a possibility. I have set the deployment target version to 2014 (matching to production) as I am running SQL 2017 and VS 2017 locally.
Dev: Microsoft SQL Server 2017 - 14.0.2027.2 (X64) Developer Edition (64-bit)
Prd:Microsoft SQL Server 2014 - 12.0.4100.1 (X64) Enterprise Edition (64-bit)
Despite no errors, I thought I would check the permissions to the output and log directory. When executing from the SSIS catlog it uses my admin account and from the agent job it uses the SQL agent service account. Both of these have full access to the output directory, so I don't think this is the problem.
Any ideas?
Thanks, Ben