February 19, 2010 at 1:04 pm
I have a job that needs to access files on our network. Of course the job runs fine in ssis, but when put in to an agent job to schedule it it can't map and it errors saying can't find the path. I've create a proxy user that has permissions on the network but It still won't run as it doesn't know the shares exist when running in agent I think.
I tried to run a bat file that maps the share before running the task but it hangs up so I must not have set that up right.
Anyone have any tips on doing this?
Mike
February 22, 2010 at 10:06 pm
Assuming you have a domain user running sql server agent service. Then can you have permissions granted to that user?
February 22, 2010 at 10:39 pm
Have you checked the job history info on the failing job?
It should give you a clear description of the issue, in which step etc.
If its a permission issue, and you are using a domain account to run it, make sure you save the package with a password and not only a key.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
February 24, 2010 at 7:23 am
In the SQL Agent Job Step properties the account shown in the "Run As" must have the appropriate network permissions. By default this is the account that is running the SQL Agent windows service but you can also set up a proxy account to be used.
It sounds like you are trying to use a mapped drive letter. I don't think that will work. You should use the UNC path instead, like, "\\servername\sharename\..."
February 24, 2010 at 9:01 am
Thanks all, using a UNC to map in a variable solved the initial issue.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply