November 17, 2010 at 8:28 am
I've run into an interesting problem. I've got an SSIS package that connects to a group of files on a remote directory (UNC path) and imports each of those files into a SQL Server database. The test files are located on a Windows file share, but the production files are located on a UNIX file share. Working with the Windows file share works fine, and all files are processed successfully. When I update the remote UNC directory to the UNIX file share, my For Each Loop container can "see" each of the files (specifically, it loops through the directory once for each file), but spits out an error indicating an invalid file path when I try to import each file.
I've tried using the Bulk Insert task as well as a data flow task, both of which failed. I've ruled out permissions issues, and confirmed that the file is in the correct format. My colleagues here are certain that they've accessed files from this same UNIX share within SSIS. Any suggestions?
TIA,
Tim
Tim Mitchell, Microsoft Data Platform MVP
Data Warehouse and ETL Consultant
TimMitchell.net | @Tim_Mitchell | Tyleris.com
ETL Best Practices
November 18, 2010 at 1:24 pm
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply