in the third error I see a connection which is not found, did you copy or move this data flow task or components inside data flow task from somewhere? if yes, did you checked again every transformation /source/destination and map the connection manager with a correct existing connection manager again?http://www.rad.pasfu.com

Hi Reza, Thanks very much for your response. I do no have msexcl40.dll file on my machine. What wonders me is when I use an excel spreadsheet as a source using an excel connection manager I seem to have no issue even with msexcl40.dll file missing. Could you please help me understand ? The other question I have is when dealing with excel files as source how do I make them dynamic in the excel connection manager ? SSIS Error: The connection string format is not valid. It must consist of one or more components of the form X=Y, separated by semicolons. This error occurs when a connection string with zero components is set on database connection manager. The result of the expression "@[User::ExcelFilePath]" on property "ConnectionString" cannot be written to the property. The expression was evaluated, but cannot be set on the property. SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft JET Database Engine" Hresult: 0x80004005 Description: "Could not find installable ISAM.". Thanks..............

how did you set the connection string? did you set the expression property of excel connection manager to a package variable? if yes, did you set a default valid value for the variable? and let us know is it compile time error or runtime?http://www.rad.pasfu.com

Two options as this point in time I can think of , Data connectivity components for 64 bit office installed ? Run64BitRuntime set to false(albiet this is design time)? Also to traverse multiple excel files , the excel connection string has to be dynamically changed using script task or expressions. Basically try getting the file path in for each enumerator and assign the connection string of execl connection with file path as a variable appended. This file path is already picked up by for each loop as a variable. Hope it helps.Happy to help! Thanks. Regards and good Wishes, Deepak. http://deepaksqlmsbusinessintelligence.blogspot.com/

how did you set the connection string? Using a variable did you set the expression property of excel connection manager to a package variable? Yes if yes, did you set a default valid value for the variable? Yes and let us know is it compile time error or runtime? Runtime error

could you set a break point at OnPreExecute of data flow task and check the value of excel connection string ? maybe there are some bad data therehttp://www.rad.pasfu.com

Hi Reza, Its not even getting that far I get this error right away. Please find screenshot for the same.

SSIS error: "Could not find installable ISAM." This is the error I get when I am trying to deal with multiple excel files using Foreach Loop container. When I pick just one excel file it seems to work fine, In the enumerator configuration I am using traverse folder option as I have multiple folders within which I have to look for excel files. I am using ssis 2008 on a 64 bit windows os, I have this package enabled to run in 32-bit mode. Please help me fix this error......... Thanks...................

in the third error I see a connection which is not found, did you copy or move this data flow task or components inside data flow task from somewhere? if yes, did you checked again every transformation /source/destination and map the connection manager with a correct existing connection manager again?http://www.rad.pasfu.com

did you tried this?: I guess this is problem with Microsoft Jet Excel Isam, which is required to access Excel sheets/workbooks. Please try to find msexcl40.dll at %SystemRoot%\System32 location in your machine. If it is available then please run the following command. regsvr32 %SystemRoot%\System32\msexcl40.dll. The above command will register the dll correctly. If msexcl40.dll is not available at %SystemRoot%\System32, then please install latest version of MDAC (Microsoft Data Access Component). reference: http://www.codeproject.com/KB/reporting-services/ImportDataUsingTSQLScript.aspx?msg=2580383http://www.rad.pasfu.com