|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Tuesday, February 26, 2013 3:32 PM
Points: 1,
Visits: 4
|
|
have an SSIS package that takes files and moves them over to an FTP site. When I am running it inside Microsoft Visual Studio, it finds the directory that I have put in the package and moves the files to the FTP.
But when I set up an SQL Server Agent job to automate the package to run daily, it fails because it looks for the files in the C:\Windows\System32 directory instead of the D:\MyFiles\ directory where they are located. And because the files are not there, the package fails to run.
When running the scheduled daily SQL Server Agent job, the package should look at the location D:\MyFiles\ directory that I built into the package just like it does when I run it in Visual Studio.
Can anyone help? I have worked on this two days trying to figure it out. Any help would be greatly appreciated.
Wade
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 1:46 PM
Points: 6,730,
Visits: 11,783
|
|
When the package runs on the server it does not have access to your drives. Does D:\MyFiles exist on the server?
If you want more help zip your SSIS package and attach it to this thread (see "Edit Attachments" button).
__________________________________________________________________________________________________ There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Believe you can and you're halfway there. --Theodore Roosevelt
Everything Should Be Made as Simple as Possible, But Not Simpler --Albert Einstein
The significant problems we face cannot be solved at the same level of thinking we were at when we created them. --Albert Einstein
1 apple is not exactly 1/8 of 8 apples. Because there are no absolutely identical apples. --Giordy
|
|
|
|