Alright, so here's what I have going on. SSIS Package that queries data from our production system and drops them into CSVs. Have a VB script task that uploads them to a third party. Needed a multi-post HTTP post with authentication and a couple specific fields sent in the header for the 3rd party so had to do a custom VB script instead of using the web destinations.
I have a ForEach loop that goes through, uploads each file via the script and then deletes it. Works great in BIDS. But when I upload it to the SSIS Package store the upload portion doesn't work. But doesn't throw an error anything since the files are still deleted.
The Query portion works, spits out the CSVs. The Script Task does nothing but the files are deleted.
Threw on all sorts of SSIS logging into the package and the script. Threw a "Hello World" log into the first line of the script and it's never fired.
What I've done:
Created Proxies with full access, linked it to new Creds and SQL logins. Nothing. Made the SQL login have rights to everything, nothing. Run the package as the new Proxy execution account and as the service account. Even changed the account the SQL AGENT service runs on (New SQL server, allowed to mess it up right now). Ran the package as 32-bit nothing. Thought it was tied to the ScriptTask reference being set as "Copy Local = True," but changed that and nothing.
Works A-OK in BIDS AND I've used this same script at another client's environment and it worked fine there. I'm not sure what else to try. Any ideas? I can upload code portions if need be.
Best Answer
That occurred because VS 2015 was built to support only SQL server 2016 and you probably deployed the package under SQL Server 2014 or lower(unsupported versions).
With the latest version of Data tools in VS 2015, you can chose the targeted SQL server version in the package to allow SSDT to chose the correct .NET libraries used in the script component.
See this link for details