Typically this type of problem is caused by environment variables that are set in a login shell, but are missing or different than those set for jobs running under cron.
You nailed it, Bill. Running the cron from root's personal crontab worked fine. Must have been environment variable related.