Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
predi
Starting Member
2 Posts |
 Posted - 2009-05-21 : 05:58:08
|
| Hi, I have a SSIS package which is called from a job. The package tries to access network files. The problem is that when package is executed from the job it fails and says that the path does not exist. BUT, when I call the package from Integration services it executes normaly and DOES find the network path. Both the job was executed as SQL Server Agent, and the package manually from Integration services was executed as SQL Server Agent. But the results are different. How can this be?P.S. SQL Server Agent account DOES have access to that path. |
|
|
svicky9
Posting Yak Master
232 Posts |
Posted - 2009-05-26 : 12:24:17
|
| How did you configure the SSIS package source in the job?file system or sql server? If file System did you give the UNC path or drive like C:\<>\<>..http://www.sqlserver007.com |
 |
|
|
Sequin
Starting Member
25 Posts |
Posted - 2009-06-03 : 10:38:20
|
| It is probably due to the account that the SQL Server Agent service uses - if it is set to "local system", it cannot access network drives on other servers - it can only see it's own drives.Create a domain user for the SQL Server Agent with permissions for the required network locations, and set this as the login credentials for the service on the server, then stop and restart the service |
|
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2009-06-14 : 12:08:04
|
| SQL agent need to run in domain account. Domain account needs to have full permission to access the path. |
|
|
|
|
|
|
SQL Server Agent can't access network from a job