In addition to opc.three's comments, you probably also need to configure a SQL Server proxy to run your SSIS package using a job. That proxy account will also need permissions to whatever files/folders your package will access.

Also the path to the problem file indicates it is sitting in some User's Desktop - a pretty unlikely location for external files on a production system. I would suggest also looking at implementing package configurations.