Check the environment the respective jobs are running under - as a quick and dirty hack, dump out the contents of the %ENV hash (sort on keys first), and compare. Generally, cron jobs often run under root's uid, which has a greatly restricted environment, possible because it doesn't execute a .profile script at the beginning of a session like a logged in user would.

I may well be wrong, but that would be a good first place to start.