Unable to run task in SSIS

This is a follow-up to the following thread:

I have created a credential and proxy. I then created a job with the one step being to run a specific SSIS task. On this step, I assigned the proxy I created as who the task should run as. I ensured that the account that was used has full control over the destination folder that the task will be accessing. I also gave the account the sysadmin role in the SQL Server database. The task fails when I tell it to run. The task failure refers me to the History log which contains nothing that helps me determine why it fails.

The task runs fine through BIDS. When I try and run it manually from the SQL Server using dtexec it fails with a "unable to access folder" error at the first file system task. This is why I am trying to run it using the SQL Server agent.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

lapolikoAuthor Commented:
I found that I CAN  manually run the task by selecting the task at the File System store and then selecting run. (I.E. using dtexec). It still will not run as a job.
lapolikoAuthor Commented:
I found the solution:

The standard security on an SSIS package is "EncryptSensistiveWithUserKey" which only allows the user that created it to be able to run in as long as there is sensitive information (passwords) stored within the package.

A workaround that I am using is that I changed the package security to "EncryptAllWithPassword" which protects the entire package with a password. When you set the package as a job step, go into the properties of that job step, click on the "Command Line" tab and you should be prompted for the password. After you enter the password, the /DECRYPT switch should show up in the command line and the job should then be able to run under a different user.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.