August 31, 2010 at 2:53 am
I have a package that reads a file from a Network share, when I run it (the package through a SQL Agent JOb) as myself the SSIS package completes successfully. When I change the job to use a proxy account I get an error similar too:
the file name "\\xxx\xxxx\xxxxx\xxx.ext" is not valid
The proxy account seems to have the neccessary permissions on the network share, I can see the folder and the file when I sign in as the proxy account.
Can anybody please explain to me why the SSIS package can't see the file when run using a proxy but has no problem when I change the proxy to run under my account, and the Proxy account appears to have the correct permissions when I sign in as it and map to the network share it can see the file?
Gethyn Elliswww.gethynellis.com
August 31, 2010 at 9:43 am
There are multiple levels of permissions, share and file system permissions. You referenced share permissions, so those appear fine. does the proxy user have permissions at the file level?
CEWII
August 31, 2010 at 3:00 pm
It appears so, the proxy can see the file and open it, its only reading from it so I guess that should be enough...I will quadruple check tomorrow though, it stinks of permissions but I can find anything out of sync.
Gethyn Elliswww.gethynellis.com
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply