ODBC Excel Driver: Unexpected error from external database driver

Question

Since the Windows update from October 10, the ODBC Excel drivers have stopped working. We get the following error when trying to read a file:

\"Unexpe

Answer 1

On a customers machine I have deinstalled KB4041681 (Windows 7) which came with last Microsoft Patch. On my machine I have deinstalled KB4041676 (Windows 10). After that Microsoft.Jet.OLEDB.4.0 is now working.

I hope that Microsoft will fix this bug soon.

Answer 2

For me, it worked following these steps:

ps.: We have a Windows Server 2008R2

1 – Download and install this: https://www.microsoft.com/en-us/download/details.aspx?id=23734 2 – Open the .dtsx file and change your Excel connection. On the properties dialog, Click on the three dots in the ConnectionString property and change it to Microsoft Excel 2007. This will automatically change your connection string to: Provider=Microsoft.ACE.OLEDB.12.0;Data Source={YOURPATH};Extended Properties=”Excel 12.0 XML;HDR=YES”; 3 – Some of our .dtsx files point to a config file (usually has a .dtsConfig extension). I also changed these guys to point to the right provider (pretty much copied and pasted the connection string I got from visual studio)

After this, I ran the SQL Job again and it worked fine.

Answer 3

I had the same problem with 2 applications developed by me since 3 years (c# and java). Since 10-oct-2017 I couldn't export to excel 2003 but 2007 worked, and couldn't import from excel 2003 but 2007 worked too for import.

In ArcGIS Desktop 10.5.1 By ESRI (a most popular software for Geographic processing) Couldn't open excels 2003 and .mdb files.

Temporally Solution: uninstall KB4041693, KB4041687 in windows 8.1 (maybe for w10).

In microsoft changelog of both path say something about "updates [...] and security updates for microsoft jet". After uninstall and restart all softwares becomes to be normal again.

this problem was introduced in 10-oct-2017. In microsoft forums this problemas was reported (kb4041693 should "fix" it but still doesn't work). Maybe in few weeks they will path (properly) this issue.