Yet another quick one for you. One of my colleagues was trying to set up a job to run a DTS package (yeap, I know, a bit of a last century stuff). Whenever he ran the package from the command line, everything was running fine. However, when he ran the same package from within a job, it failed.
Apparently the answer is very simple in our case, as documented in this article. Just to summarize for you: on a 64-bit system, whenever you run the package from the command line (cmdexec), it calls the 32-bit (x86) version of the tool. Whenever you run it from SQL Server agent, it calls the64-bit of the tool.
I hope this helps.