Lightly resurrecting this just to note that I had the same problem.

Forcing it to use the 32-bit executable didn't work, but I did find out that the job had been altered in SSMS 2008 when it's a 2005 database.

Recreating the steps through SSMS 2005 fixed the issue for me. Thanks for the pointers though! 🙂