Sorry, I mis-read that. What command in the job is actually issuing the error? Do you have the complete error log from the package execution?