Have you check the permissions of the account that runs the SQL Server Agent as already suggested? In order to be sure it is a permission issue you can also try to set your account to run the SQL Server Agent on a development Server and run the package from there.
