SSIS Package containing XCopy will not run as Job in Mgmt Studio
Posted on 2008-06-22
I have an SSIS package which runs fine thru BIDS, as well as when I log on to Mgmt Studio and Execute it manually as a Package. However when set up as a Job, it doesn't seem to run, although it does not fail. It just continues to display "Executing." Research thus far seems to indicate that it is related to the particular step within the package which contains a literal filename path (I'm performing an XCopy). I've tried all different encryption options within the package security settings but it still doesn't run as a job. Does anyone know if I need to set up a Proxy Account, and if so, can you explain exactly how to do this? I am more of a developer than a DBA, but I'm hoping I can at least get enough information to work with our DBA toward a resolution.