8/27/2013

SSIS Master Package Protection Level Setting = DontSaveSensative

So now that we have 6 SSIS packages working, I was asked to schedule the job on SQL Server SQL Agent.

Sounds easy.  I tested all 6 packages individually, ran as expected.

Then ran the "Master Package" which calls the 6 other packages and it failed.

So looking at the most trusted advisor for solving problems, Google found this solution:

http://social.msdn.microsoft.com/Forums/sqlserver/en-US/74ecba4a-0986-476a-b168-cb13a48c4e82/calling-child-packages-from-master-package-is-failing-when-ssis-package-is-scheduled-to-execute-from

And sure enough that solved the issue.  You have to change the "Protection Level" to "DontSaveSensative"

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.