RE: The connection was not valid" "Flat File Source"

#1

Hello Shawn,

Quick thought. This would suggest that the execution account of the package
cannot see a D:\ drive.

Regards

Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com

Quote:

It appears to work fine when the physical path to the file is replaced
with a file share path (i.e. "\\machine\files\xxx.txt")

"Shawn" wrote:

When executing a SSIS package I get the following error The file name
"D:\xxx.TXT" specified in the connection was not valid.

I am executing my package from a .NET Assembly using
"Microsoft.SqlServer.Dts.Runtime"

C# excerpt
Application a = new Application();
Package p = a.LoadPackage("e:\xxx.dtsx", null);
DTSExecResult result = p.Execute();
My package does the following:
1) Executes a TSQL Statement to delete all the data from the table
2) Reads in records from a flat file on the disk (flat file source)
3) Uses Derived columns to add some information to the result set
4) Uses a OLE DB Destination to load that data into a table into SQL
Server
The package is created on one computer and executed on another.

It uses integrated authentication to access the SQL Server, the nt
account the application is running under has SA permissions in the
sql server and is an admin on the windows server. The nt account that
the SSIS service is running under is an admin on the windows server.
Everyone has full control of the file. (I understand this is not the
best thing from a security perspective, but I was trying to eliminate
security as a cause of the package not being able to see the flat
file on the disk.)

#2

We gave the execution account of the package admin privileges on the entire
box (i.e. it could see all drives, etc.). Additionally we gave everyone “full
control” permissions on the file. My initial thought was security, but I
don’t know what more to give it. . .

Thanks for your ideas, keep them coming

"Allan Mitchell" wrote:

Quote:

Hello Shawn,

Quick thought. This would suggest that the execution account of the package
cannot see a D:\ drive.

Regards

Allan Mitchell
Konesans Ltd
T +44 7966 476 572
F +44 2071 008 479
http://www.konesans.com

It appears to work fine when the physical path to the file is replaced
with a file share path (i.e. "\\machine\files\xxx.txt")

"Shawn" wrote:

When executing a SSIS package I get the following error The file name
"D:\xxx.TXT" specified in the connection was not valid.

I am executing my package from a .NET Assembly using
"Microsoft.SqlServer.Dts.Runtime"

C# excerpt
Application a = new Application();
Package p = a.LoadPackage("e:\xxx.dtsx", null);
DTSExecResult result = p.Execute();
My package does the following:
1) Executes a TSQL Statement to delete all the data from the table
2) Reads in records from a flat file on the disk (flat file source)
3) Uses Derived columns to add some information to the result set
4) Uses a OLE DB Destination to load that data into a table into SQL
Server
The package is created on one computer and executed on another.

It uses integrated authentication to access the SQL Server, the nt
account the application is running under has SA permissions in the
sql server and is an admin on the windows server. The nt account that
the SSIS service is running under is an admin on the windows server.
Everyone has full control of the file. (I understand this is not the
best thing from a security perspective, but I was trying to eliminate
security as a cause of the package not being able to see the flat
file on the disk.)

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

RE: The connection was not valid" "Flat File Source"

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts

RE: The connection was not valid" "Flat File Source" - 12-11-2006 , 02:51 PM

RE: The connection was not valid" "Flat File Source" - 12-12-2006 , 06:37 AM