So are you trying to connect as a SQL Server named user, by passing username and password credentials?

Any time that an SSIS job works in SSDT, but not in SQL Agent, your first suspicion should be that there is a permissions problem.
Does the SQL Agent service/proxy...

Hello Scott
I won't download the solution just yet, because I believe I understand the issue you are having.
As I cryptically implied in my earlier message, configuration of data...

If you are working with project-level parameters and connections, your packages need to be deployed to SSISDB.
Once you have this, use SSISDB environments to configure your connections per environment.

One of those minor irritations. If you do a 'View History' for a SQL Agent job which is failing, why do you always have to resize the window at the...

OK, if you know that your VB.NET application is the only way that entries in the tables you mention can be changed, best practice is that you code whatever stored...

Yes, the variable's value should be available to all tasks in the package, given that the variable is scoped at package level. What makes you think that it is not?...