SSIS package fails to run as a SQL server Agent job but executes fine when run manually

I had to do the below when an SSIS package that I scheduled as a job failed. It runs fine when run manually. Do the following to successfully configure an SSIS package in a SQL Server agent job

1. Open BIDS and change the properties of the package, find an option called 'Encrypt all with password'.

2. Put in a password and DBA should know that.

3. After it is deployed as an SSIS package once again, go to the job, right click-properties-go to command line tab-it should ask you a password with what you have encrypted, put in that and save it, try re-running the job and it will successfully execute as a SQL Agent job. Else other option is to edit the job step as below to decrypt it using a SQL agent job:

"C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTEXEC.EXE"  /FILE "C:\SSISInit\Packagename.dtsx" /CHECKPOINTING OFF  /De "password" /REPORTING EWCDI /MAXCONCURRENT " -1"

The other option to schedule an SSIS package as a job is to run the package under a proxy account. Please search through this blog for info about that process