Flat File Connection Manager in SSIS package shows "Valid File Name Must be Selected"

Question

                      (Flat File Location)
                    Samba Share | Windows Share
(SSIS)           _______________________________
                |               |
XP 32bit        |  Works        |  Works
                |               |
2003 Serv 32bit |  Works        |  Works
                |               |
Vista 64bit     |  ERROR        |  Works
                |               |
Win 7 64bit     |  ERROR        |  Works 
                |               |
2008 Serv 64bit |  ERROR        |  Works

---

I created an SSIS package in VS 2008 that parses a flat file from a shared folder and puts the records into a SQL Server db.

I recently installed Windows 7 and VS 2008 on a new workstation. When I import the package from TFS and open it, I get the error

Validation error. Parse and Import Catalog Flat File: MySSISPackage: The file name "\\shared\flatfile.txt" specified in the connection was not valid.

When I open the Flat File Connection Manager Editor, there is an error stating:

A valid file name must be selected

I can browse to and select the file from inside the editor, but I cannot change any properties, or move away from the General tab because of this error.

If I go back to my laptop (Windows XP), where the package was first created, there is no error. Both workstations are on the same domain, and I'm logging in using the same credentials.

Any ideas as to why I would receive this error from one workstation and not another?

---

UPDATE: If I take the .dtsx package from the running workstation and load it into SSIS on the server, I get the following errors when it tries to run:

Error: The file name "\\shared\flatfile.txt" specified in the connection was not valid.

and...

Error: Connection "MySSISPackage" failed validation.

and...

Error: The file name property is not valid. The file name is a device or contains invalid characters.

---

UPDATE 2:

a) The Shared folder I'm trying to pull the flat file from is a Samba share on a Unix box.

b) If I access the file using SSIS on any 64-bit platform (Windows 7 64-bit, Vista 64-bit, Windows Server 2008) I get the error "A valid file name must be selected."

c) Accessing the file using SSIS from 32-bit environments (Windows XP 32-bit, Windows Server 2003 32-bit) there is no problem.

d) If I move the file to a shared folder on a Windows server, 64-bit SSIS recognizes the file.

Solution 1

I had a similar problem. What I did was in Solution Explorer I right-clicked on the project name and selected properties. I then clicked Debugging and the set the Run64BitRuntime property = 'False'. The Excel file is 32 bit so running SSIS as a 64 bit application won't work in this scenario.

Solution 2

We had the same kind of problem. After searching a while, we found that the account used had access to the sub-dir, but not to the share. It looks like your account needs to have access inherited from then highest directory.

e.g.: \\server\share\foder\subfold1\subfold2\file.csv <== We need access here acces to "subfold2" is not inherited and the account did not have access to \\server\share\

So we gave acces to \\server\share\ and it fixed the problem.

Solution 3

In BIDS (visual studio SSIS), if you go to the SSIS menu (on the top bar), and uncheck "work offline".

A right pain in the bum, I got the hint to the fix in http://www.sqldev.org/sql-server-integration-services/flat-file-connection-manager-problem-32774.shtml

Solution 4

I found a solution by just changing the file path to one it could digest better - named drive worked. Example: Text file was on \server\filepath\filename.txt ERROR I copied the file over to c:\filepath\filename.txt and it worked fine.

Solution 5

There is one other possibility here, and the solution that worked for me on the same problem was to right click the connection manager, and choose DelayValidation = True instead of the default of false. My pain point was using SSIS Configurations to tell where the file was at and BIDS did not like the network share file path.

View more solutions