November 25, 2010 at 1:02 am
Hi,
I have a package that will take latest files from [FTP path] archive to the root folder. I have read, write permission for this folder. The package runs on my local as expected.
But when i schedule this package in SQL Server Agent [job], it throws Access to the path is denied error. I have scheduled this job using my account.
Can any one tell me, why the package not runs using my account?
---
November 25, 2010 at 1:05 am
Do you mean that the SQL Server Agent service is using your own personal credentials to run?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
November 25, 2010 at 1:09 am
yes, i am the owner of this. Its runs using my personal credential. Moreover, if i run this package using dtexec command its running fine here.
November 25, 2010 at 1:11 am
Does the path include drive letters? If so, can you use a UNC path instead?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
November 25, 2010 at 1:15 am
Phil Parkin (11/25/2010)
Does the path include drive letters? If so, can you use a UNC path instead?
No this path not have such. its like \\<ipaddress>\<folder name>
November 25, 2010 at 2:38 am
I have sort out the issue now.
I have tried with domain name rather than ip address. Then my agent job is working fine now. But i don't know why it is not taking ip address.
Thanks Phil! :w00t:
November 25, 2010 at 2:42 am
Well done. I have no idea either 🙂
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
November 25, 2010 at 2:50 am
yes, i am the owner of this. Its runs using my personal credential. Moreover, if i run this package using dtexec command its running fine here.
However it looks like the SQL Server Agent startup account does not have access to the path specified. Can you double check if the SQL Server Agent is starting with an ID which has sufficient privileges?
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
November 25, 2010 at 2:54 am
Adiga (11/25/2010)
However it looks like the SQL Server Agent startup account does not have access to the path specified. Can you double check if the SQL Server Agent is starting with an ID which has sufficient privileges?
If you read the rest of the thread, you'll see that using domain name in the path, rather than IP address, resolved the problem. Perhaps you can suggest why?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
November 25, 2010 at 3:00 am
Phil Parkin (11/25/2010)
Adiga (11/25/2010)
However it looks like the SQL Server Agent startup account does not have access to the path specified. Can you double check if the SQL Server Agent is starting with an ID which has sufficient privileges?
If you read the rest of the thread, you'll see that using domain name in the path, rather than IP address, resolved the problem. Perhaps you can suggest why?
May be I was slow in drafting my response. Many updates in the mean while 😉
Even I am not sure how using the Domain name resolved the issue.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply