November 13, 2008 at 10:40 am
I created a SSIS package to import data from a CSV file from a different server and when I ran it in SSIS, it was fine.
The file location is \\server1\inteface\import1.csv
I put it in a job to run the SSIS package and when I ran the job, it failed to recognize the location of the CSV file.
Do I need to move the file to the local drive?
November 13, 2008 at 10:52 am
Loner (11/13/2008)
I created a SSIS package to import data from a CSV file from a different server and when I ran it in SSIS, it was fine.The file location is \\server1\inteface\import1.csv
I put it in a job to run the SSIS package and when I ran the job, it failed to recognize the location of the CSV file.
Do I need to move the file to the local drive?
The account under which the SQL Agent service is running needs access on share \\server1\inteface\import1.csv.
When you run the package yourself, you seem to have this access, but when you run it as a job, it is the SQL Agent account that needs these rights.
Is this a network account or LOCAL SYSTEM?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
November 13, 2008 at 11:01 am
It is a network account and it can access the file when I sign on using that account. But when I put it in the job and it failed to recognize the file.
November 14, 2008 at 1:24 pm
Loner (11/13/2008)
It is a network account and it can access the file when I sign on using that account. But when I put it in the job and it failed to recognize the file.
I don't know if that's possible, but can you do the following?
RDP to the machine hosting the SQL Agent service as the SQL Agent account.
Launch BIDS, try to run the package.
Are you getting the same error?
Also, can you see that network share where your file is located, while RDP'd as the agent account?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
November 14, 2008 at 2:05 pm
Yes I remote control to the server and run the package under my window logon and it is running fine.
Then I set up the job to run the package using my window logon and it fails.
November 16, 2008 at 5:10 pm
If you've confirmed that the file source is accessible under the context of the account running SQL Server agent, check the same thing on the destination folder (I assume that is is a folder local to the machine running SSIS).
hth,
Tim
Tim Mitchell
TimMitchell.net | @tmitch.net | Tyleris.com
ETL Best Practices
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply