When I create my connection manager to connect to a .xlsx file, I get the error message that says:
"Test connection failed because of an error in initializing provider. External table is not in the expected format."
The provider selected was the ole db "Microsoft office 12.0 Access Database Engine...", and in the All tab I entered "Excel 12.0" at the top where it says Extended properties.
Here is the stumper:
My import package(s) has (have) been running manually for the last 2-3 weeks, but now i've finished an automated system that downloads the files from the ftp site, unzips them, validates all the expected files are there, renames and relocates the files to the names/locations expected by my ETL, and then runs the ETL.
I found out today that the people who manually did this process were each time opening the file and then saving it to the correct location in Excel 2007.
When I try to run my ETL on the files in the automated process, it fails with the above error. If, however, I just open the file and save it (also in 2007), it runs fine. I have been trying to figure out what saving the file is doing to change it to be in the expected format.
I have tried to use an excel 2003 connection to connect to a copy of the file with a modified extension of .xls and that didn't work. (in case it was in another version of excel and someone just changed the ext)
I then tried to access the file with the OLE DB provider, as above, but instead of entering 12.0 on the Extended properties line, entering 9.0 or 14.0 in turn (creating new sources/connections each time), and when I do that, both times I get an error that says:
“Test connection failed because of an error in initializing provider. Could not find installable ISAM.”
Am I missing something? Is there something else that simply opening and saving the file might be doing to make it paletable to ssis?
If we install excel on the db server I realize i could probably open it up and save it as excel 2007 and that would do the trick, but the dba is resistant to this idea, so I thought I'd see if anyone has any other ideas?
If we do have to install excel on that server, does the version have to be excel 2007 in order to programmatically save it as type 2007?
thanks in advance for your thoughts on the issue...