Using SSMS I created an export a query to Excel and saved it as a DTSX package. Imported this DTSX package into a BIDS project to make it run hourly and export a excel file
Most of the problems arise due to these situations:
Data source connection or File access issue (when the user running the sql agent doesn't have the right permissions to the db or to the destination file).
Package protection level (pwd are sensitive data, and sometimes are not copied depending on the protection level).
64bit issue (this a common one on XL exports. Since there's no Jet Driver for 64bit systems, when running on a 64bit OS you need to either use the 32bit DTEXEC in your sql job or set the "Use 32bit runtime" option, it's on the "Execution options" tab when you're creating a SSIS job step, check the image on link below for seeing it).
32Bit runtime option image
For information on this topic, have a look at this article, it has detailed information on situations when ssis packages run on BIDS but not on SQL jobs..
How do I troubleshoot SSIS packages failed execution in a SQL Agent job?
Hope this helps you..
Kind regards,