This again links to previous questions I've asked, however. I am writing an SSIS package to manipulate data, some of it starts in and must end up in DBF files. I decided the best way to manipulate the data was to import it to SQL, do what I need to do and then export it back to the DBF Files. I've now done everything I need and need to save it back to DBF. I've tried various methods and found the easiest way is to create a package using the export wizard to move the data and then call the execute pacakge from within my SSIS package. The export wizard works on it's own fine but is erroring when called from within the SSIS package. ![alt text] THis is the set up of the execution package task. The error message I'm getting is: > Error: Error 0xC0014062. Failed to load the package "Export_actgchg.dtsx" from SQL Server "C:\\LEAN_EOM\\vamp". Make sure the package exist on the SQL Server and you have the correct credential to access it. Any ideas, gratefully received. : /upfiles/SD10.jpg
Do you mean that you can run it as a stand-alone package within the SSIS development environment, but not as a scheduled task? If so, then check the security context under which the scheduled task runs - does that have access to the appropriate directory?
As @ThomasRushton stated, the scheduled task doesn't have appropriate rights on file system. Run the SQL Server Configuration Manager and check under which account is running the SQL Server Agent Service. All the packages executed from within a Job (scheduled task) are executed under this account. This account needs to have appropriate right on the filesystem to access the dtsx package. Also the account uder which the Agent Service is running needs to have apropriate right on the destination directory, where you will output your dbf files, otherwise the data flow task will fail. If you are executing it from within SSMS, then it's running under account, under which the SSMS is running.. In most cases your account under which you are logged in. So you need to setup apropriate right on the file system for the Agent Service account.
Got the same error the other day. I was trying to edit the Sql agent job from my local ssms and it tried to find the package on my local drive instead of the server. RDP'd into the server and made the change there and it worked just fine. Hope that helps.