April 24, 2014 at 6:55 pm
Hello - I am trying to find out what is the best way to have my ssis package export data to flat file on a mapped network share. This will run hourly with a agent job running under the service account. I know im probably going to run into issues with a network share. Any help suggestions would be greatly appreciated.
Thanks !! 🙂
April 25, 2014 at 12:25 am
elee1969 (4/24/2014)
Hello - I am trying to find out what is the best way to have my ssis package export data to flat file on a mapped network share. This will run hourly with a agent job running under the service account. I know im probably going to run into issues with a network share. Any help suggestions would be greatly appreciated.Thanks !! 🙂
My suggestion would be to use a UNC path rather than a mapped drive.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
April 28, 2014 at 10:46 am
Phil Parkin (4/25/2014)
elee1969 (4/24/2014)
Hello - I am trying to find out what is the best way to have my ssis package export data to flat file on a mapped network share. This will run hourly with a agent job running under the service account. I know im probably going to run into issues with a network share. Any help suggestions would be greatly appreciated.Thanks !! 🙂
My suggestion would be to use a UNC path rather than a mapped drive.
So i would put the UNC path in the connection manager in the File Name section? When the package runs under the service account will it have issues writing to that location?
April 28, 2014 at 11:02 am
elee1969 (4/28/2014)
Phil Parkin (4/25/2014)
elee1969 (4/24/2014)
Hello - I am trying to find out what is the best way to have my ssis package export data to flat file on a mapped network share. This will run hourly with a agent job running under the service account. I know im probably going to run into issues with a network share. Any help suggestions would be greatly appreciated.Thanks !! 🙂
My suggestion would be to use a UNC path rather than a mapped drive.
So i would put the UNC path in the connection manager in the File Name section? When the package runs under the service account will it have issues writing to that location?
Yes and maybe. Whether you use a mapped drive or a UNC path does not affect the permissions which the service account needs to modify files there.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
April 29, 2014 at 10:47 am
Can't get this to work. I used UNC path \\Server\E$\filepath
I get error can not find path.
April 29, 2014 at 12:07 pm
If you log in as that service account, are you able to navigate to that path in Windows Explorer? Is that definitely a local drive on the server?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
April 29, 2014 at 12:11 pm
its not a local drive.
What i am trying to do is ssis package creates 3 files on Server A. Then have the 3 files places on Server B because server B can get to the outside world to send files to vendor. We thought if we create a mapped network drive that it would work but so far no go.
April 29, 2014 at 12:16 pm
UNC paths need to use local disks, as far as I know. But if you can map a drive to another server, you should also be able to point a UNC path at another server. I don't really understand the problem.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply