Home All Groups Group Topic Archive Search About
Author
11 Feb 2009 7:29 PM
j0hnj0hn
I think this is due to my lack of understanding, but I need help.  I have
created an SSIS package that will export the rows from a view to a text file
across the network.  When I execute the package in the Execute Package
Utility the package runs as expected exporting the file to the network file. 
However, when I run this package under the SQL Server agent (the step
executes the SSIS package saved on the local file system) I get the error
cannot write to DestinationConnectionFlatFile [file name].  I set my account
to the Server Agent service and restarted it with the same luck.  Am I
missing something the SQL Server Agent needs to execute this package?

Author
13 Feb 2009 3:19 AM
Marcelo Vollbrecht
Show quote Hide quote
"j0hnj0hn" wrote:

> I think this is due to my lack of understanding, but I need help.  I have
> created an SSIS package that will export the rows from a view to a text file
> across the network.  When I execute the package in the Execute Package
> Utility the package runs as expected exporting the file to the network file. 
> However, when I run this package under the SQL Server agent (the step
> executes the SSIS package saved on the local file system) I get the error
> cannot write to DestinationConnectionFlatFile [file name].  I set my account
> to the Server Agent service and restarted it with the same luck.  Am I
> missing something the SQL Server Agent needs to execute this package?
Are all your drivers up to date? click for free checkup

Author
13 Feb 2009 3:22 AM
Marcelo Vollbrecht
Hi There.

Just check if you are trying to save this file in a location that your
server can actually see.

if your file destination is :  c:\ExportFiles\File002003.txt for example,
this folder c:\exportfiles needs to be there.

if so, please let us know.
Author
16 Feb 2009 5:23 PM
John
On Feb 12, 8:22 pm, Marcelo Vollbrecht
<MarceloVollbre***@discussions.microsoft.com> wrote:
> Hi There.
>
> Just check if you are trying to save this file in a location that your
> server can actually see.
>
> if your file destination is :  c:\ExportFiles\File002003.txt for example,
> this folder c:\exportfiles needs to be there.
>
> if so, please let us know.

The file exists and SSIS will export if I run it from the Execution
Package Utility without a problem.  It is not an error that it can't
find the file, it can't open the file to write to it, so the file is
there.

John
Author
25 Feb 2009 12:25 AM
Pat M - City of Reno
I had the same problem except doing backups to a different server. You have
to run the SQL Server Agent under a Domain Admin account so you have access
to the drives under the service. If SQL Agent is running under Local Account
it won't work. Hope this helps.
Pat


Show quoteHide quote
"j0hnj0hn" wrote:

> I think this is due to my lack of understanding, but I need help.  I have
> created an SSIS package that will export the rows from a view to a text file
> across the network.  When I execute the package in the Execute Package
> Utility the package runs as expected exporting the file to the network file. 
> However, when I run this package under the SQL Server agent (the step
> executes the SSIS package saved on the local file system) I get the error
> cannot write to DestinationConnectionFlatFile [file name].  I set my account
> to the Server Agent service and restarted it with the same luck.  Am I
> missing something the SQL Server Agent needs to execute this package?

Bookmark and Share