Actually, it turned out to be the old NTLM double hop situation. Worked around it by reconfiguring my package connections (which reference a second server) with SQL Server authentication.

I'm trying to execute an MSSQL ssis package from a Control-M job. I use the command line format to execute the dtexec utility.... dtexec /SQL [server] / [package] The problem is that the connections in my package are defined using Windows Integrated security. When the package tries to connect, I get...