February 7, 2026 at 2:07 am
Hi all,
I'm trying to do classic scenario for loading multiple Excel files into db working in VS2022.
I have reliable template which worked OK for csv files. But now after switching to xlsx I have problem when file name defined on Variable tab let say FileA.xlsx is not present in <FOR EACH> directory. If this happens then SSIS creates this file with sheet = GUD and this breaks my process.
If FileA.xlsx is in place, then everything running smooth and loading right contents for each of the file in Directory. I also used c# scripts to display message to track file names.
What I might missing here ?
Expression for Excel connector set using ExcelFilePath property.
I Played with Delay Validation, no difference.
Am I"m missing some other property ?
Maybe it's my VS setup ? I can't change run64 = false in my project because it's grey out.
February 8, 2026 at 2:10 am
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
February 8, 2026 at 4:59 pm
As you are using a FOREACH container to iterate across a folder, why are you also defining file names? Why not simply let the container pick up *.xlsx within the folder?
Perhaps you can post a screenshot of your FOREACH configuration?
February 10, 2026 at 4:28 pm
Thanks Phil,
That what I exactly doing, picking up all *xlsx, but it doesn't work properly for Excel file Source connector i fI don't have that FileA in my folder, it's very strange. I finished with using zappys.
February 10, 2026 at 4:54 pm
So you solved it? OK.
If it were me, I would be searching across my .DTSX for the text 'FileA' – it must be coming from somewhere!
February 11, 2026 at 3:05 am
The issue you’re seeing with SSIS in VS2022 when working with Excel files is almost always caused by a mismatch between the 32-bit/64-bit ACE OLE DB driver and the execution environment. VS2022 is 64-bit, but many Excel drivers and SSIS Excel connection managers are 32-bit, so if the package runs with the wrong bitness, it may fail to read existing files or even create new empty ones with default sheet names. To fix it, ensure the correct version of the Microsoft Access Database Engine is installed (matching the runtime), configure the package or SQL Agent job to run in the corresponding 32- or 64-bit mode, or alternatively convert Excel files to CSV or use a Script Task to bypass ACE entirely.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply