Package Validation Error

Question

I'm trying to use a foreach loop container to import several excel files into a table, I specified the folder and the files I'm going to use (*.xls), after that I created a path variable then I went to the excel source connection and in the "Expression" property I selected the variable. I created the foreach container but, the excel source's connectionString only shows Provider=Microsoft.Jet.OLEDB.4.0;, so it means it's not taking the variable value. What can I do to solve that?

Note: I'm using SQL Server 2012

ADDITIONAL INFORMATION:

Error at Data Flow Task [Excel Source [20]]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.

Error at Data Flow Task [SSIS.Pipeline]: Excel Source failed validation and returned error code 0xC020801C.

Error at Data Flow Task [SSIS.Pipeline]: One or more component failed validation.

Error at Data Flow Task: There were errors during task validation.

Error at Package [Connection manager "Excel Connection Manager"]: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80040E4D.

(Microsoft.DataTransformationServices.VsIntegration)

Solution

Check the link below where I answer mainly focus on RUN64BITS TO FALSE instead of TRUE.

Execel Source ERROR

Comments

[Libin M]

Again this may not be the case always but for me the excel was corrupted. I followed these steps after wasting 3 hours: tried to open the source excel file, it didn't open and prompted the file is corrupted. recreated the excel file from the source, saved as excel (.xlsx) file recreated the connection manager and edited excel source and everything works fine.

[Jeremy Thompson]

Downvoter, care to explain? It might not be a solution but it's the root cause.

[Kazem]

After I read this comment, i double checked my excel file, surprisingly although i had created the file myself, it was showing a message saying this file is locked for editing for a different user, so recreated it with a different name and updated my Excel connection manager and it worked for me too.