Good morning:
I've worked with SSIS exhaustively in the past and this one is stumping me. I almost am leaning towards a configuration issue on the SQL server versus a deployment issue but wanted to run it by you first.
I have a SSIS package - created in BIDS 2008. SQL Engine and SSIS is 2008R2. The job has two connections - OLEDB connection to SQL Server and File connection to a folder. SSIS and the SQL Engine were installed by someone else and SQL Engine runs under Network Service and SSIS runs under Local System.
I created the package on a computer on a different domain but changed the owner value once I loaded it on the SQL server and deployed to the SSIS package store with DecryptSensitiveWithPassword, providing a password. I also tried deleting the package and job from SSIS and importing through the SSIS menu in SSMS, choosing DecryptSensitiveWithPassword. Although I don't believe I would need to given my connections, I have tried running as 32-bit (in addition to 64-bit) and I've tried setting up a proxy account. I've tried using other encryption methods. I've also tried using cmdExec and running DTEXEC from the command line. The SQL data source in the package uses a SQL account, not Windows auth. For testing I opened the EVERYONE group up to write to the local file folder where the files need to be read / written.
NOTHING WORKS. The package runs fine from BIDS on the same machine and it runs fine from the SSIS server (via SSMS) and through the command line. SQL Agent is the only thing not playing nice.
The latest error (cmdExec running DTEXEC):
dtexec /file "D:\DTS\FileTransfer.dtsx" /DECRYPT mypassword
Code: 0xC0010018 Source: Description: Error loading value "<DTS:ConnectionManager xmlns:DTS="www.microsoft.com/SqlServer/Dts"> ...
I've read and reviewed several other discussions including this here (http://social.technet.microsoft.com/Forums/en-US/sqlintegrationservices/thread/e13c137c-1535-4475-8c2f-c7e6e7d125fc)
BIG THANKS!