I have come across this problem many times. I have never been able to determine the cause (probably a bug in the way security information are passed to the package through SQL Server Agent??) but a work around is to create your scheduled job manually and use the dtsrun command in your job step. Hope this helps.