December 16, 2016 at 7:45 am
I have created the Integration Services package , one of the task I use is script task.
This Task checks if the file exists on the network drive.
package works when I am running through visual studio, it is able to find file and process it.
but when I load the package into the catalog and execute it then though the file exists on that network drive. task is not able to find it
December 16, 2016 at 7:51 am
did you already configure a credential and proxy operator in SQL Agent?
Did you configure that step to use that proxy operator?
the account that runs the SSIS jobs \is often a service account that has no access to network shares.
it is very common that you need to create a domain account(ie [myDomain\SQLServiceAccount] with a password that does not expire, and then grant that account permissions to the right file shares that this kind of process will be touching(network backup shares, shares for files to be copied/to/from etc)
Lowell
December 16, 2016 at 8:12 am
mandavli (12/16/2016)
I have created the Integration Services package , one of the task I use is script task.This Task checks if the file exists on the network drive.
package works when I am running through visual studio, it is able to find file and process it.
but when I load the package into the catalog and execute it then though the file exists on that network drive. task is not able to find it
Are you using a UNC path (and not a mapped drive)?
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
December 16, 2016 at 8:52 am
Thank you. Created the proxy and it worked on the native server (where the catalog exists)
But when I create a job on a different sql server. it fails, I have created same proxy. the credential account is same and has same permissions on sqlserver
December 16, 2016 at 8:54 am
mandavli (12/16/2016)
Thank you. Created the proxy and it worked on the native server (where the catalog exists)But when I create a job on a different sql server. it fails, I have created same proxy. the credential account is same and has same permissions on sqlserver
it might fail on the other server, but with what specificf error?
it might be related to file/path assumptions, or permissions, or may other things. (doe sit assume there is a c:\Data directory or something?)
Lowell
December 16, 2016 at 8:59 am
it is UNC path that I am using in the package,
with fail as I mean it's not able to find file, even if I have same proxy accounts on both servers and they have exact same rights.
December 16, 2016 at 9:12 am
mandavli (12/16/2016)
it is UNC path that I am using in the package,with fail as I mean it's not able to find file, even if I have same proxy accounts on both servers and they have exact same rights.
Are both servers on the same network? Is one in a firewalled DMZ for example?
From that other server, can YOU navigate to the UNC path in question?
Lowell
December 16, 2016 at 9:18 am
yes I can navigate to that path from the other server and it's on the same network
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply