none
Error in Windows update KB4041681 - Unexpected error from external database driver (1) RRS feed

  • Question

  • Hi,

    After Windows update KB4041681 OLEDB connection stop working.

    THIS CODE stop working:

    using (OleDbConnection conObj = new OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\\a.XLS;Extended Properties=Excel 8.0;"))
                {
                    conObj.Open();

    RISE ERROR:

    EN: Unexpected error from external database driver (1). (Microsoft JET Database Engine)
    PL: Nieoczekiwany błąd (1) w sterowniku zewnętrznej bazy danych.

    After unistall update KB4041681 all is OK.

    ANY other workaround then removing update KB4041681?

    Pawel Pelc

    www.LoMag.eu


    Pawel


    Thursday, October 12, 2017 12:25 PM

All replies

  • After installing this update the ODBC Data Source Administrator does not allow editing configured. In SQL Server 2000 data exports imports into Excel (xls) stop working.

    After unistall update KB4041681 all is OK
    • Edited by GustavoMORE Thursday, October 12, 2017 2:31 PM
    Thursday, October 12, 2017 2:20 PM
  • Hi we have the same problem with Access and Export a Table to Excel.

    Very disapointed

    Thursday, October 12, 2017 2:49 PM
  • Same issue here.

    Using an external desktop aaplication to export data through ODBC into an Excel file.

    Thursday, October 12, 2017 3:42 PM
  • We are having the same problem.  Does anyone know when this will be addressed?

    Thursday, October 12, 2017 5:44 PM
  • Hello,

    I have the same issue.

    If somebody have a solution other than uninstalling update KB4041681, please let us know.

    Regards

    Thursday, October 12, 2017 6:16 PM
  • I ran into this and have a good half-dozen custom .NET programs that rely on Excel automation. What I did to both address the issue (and upgrade the underlying dependencies) was to migrate things from a Microsoft.Jet.OLEDB.4.0 to a Microsoft.ACE.OLEDB.12.0 provider. I installed the AccessDatabaseEngine executable, which is an Office 2010-level support library. This created the ACE provider I needed. After doing this we are back in business.

    Of course this required working with XLSX instead of XLS files, but then again this isn't the year 2002.

    Confirmed that any Excel automation I had that inserted records via the old JET provider was broken after this Windows Update. Haven't run into one of those situation in a loooooong time!

     
    Thursday, October 12, 2017 6:48 PM
  • I'm having exactly the same problem from ODBC:

    "[Microsoft][ODBC Excel Driver] Reserved error (-5016)"

    Thursday, October 12, 2017 8:14 PM
  • I got the same problem too. Hope MS can fix this issue as soon as possible. I turn off the auto update to avoid it happen now.

    • Edited by CoreyNg Friday, October 13, 2017 5:48 AM
    Friday, October 13, 2017 5:47 AM
  • I got the same problem too
    Friday, October 13, 2017 9:17 AM
  • Hello

    The gregarican's answer is partially the right one. ACE do the trick but you are not force to change to xlsx files

    Installing the AccessDatabaseEngine and using Miscrosoft.ACE.OLEDB.12.0 provider will work out and if you keep Excel 8.0 in the connexion string, you can still use .xls files.

    After installing the AccessDataBaseEngine Try changing :

    using (OleDbConnection conObj = new OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Data Source=C:\\a.XLS;Extended Properties=Excel 8.0;"))
                {
                    conObj.Open();

    to

    using (OleDbConnection conObj = new OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\\a.XLS;Extended Properties=Excel 8.0;"))
                {
                    conObj.Open();



    • Edited by bascoure Friday, October 13, 2017 9:44 AM
    • Proposed as answer by HopkinFar Thursday, October 19, 2017 7:00 PM
    Friday, October 13, 2017 9:37 AM
  • Good call. I found that out when refining some routines that required still working with XLS files. Just change the connect string from Jet to ACE and it works just fine. I am also reading some tab-delimited text files and changed from Jet to ACE for those methods. 

    If you Google this October round of Microsoft Update roll-ups you will see a variety of fubars, from BSOD's to broken application dependencies to you name it. At least it's not as damaging as Windows NT 4.0 Service Pack 6. Which basically broke TCP/IP for a lot of servers back in the day. Hence the rush release of NT SP6a :)

    Friday, October 13, 2017 12:56 PM
  • We have this problem also.  Unable to export to .xls from our database software without the -5016 error.  Uninstalling KB4041681 and KB 4041678 resolves it for us.  Hiding those updates for now, hope Microsoft is reading this forum!  ;-)

    • Edited by Mike442 Friday, October 13, 2017 7:29 PM
    Friday, October 13, 2017 7:28 PM
  • I was getting from MS Access 2000 error 3275 in VBA transferspreadsheet unexpected error from external driver (1), uninstalling Windows update KB4041681 fixed my issue.

    Joe

    Friday, October 13, 2017 10:33 PM
  • Same problem, after KB4041681 the connection fails:

    ''''''''''''''''''''''

    Dim cn As ADODB.Connection
    Set cn = New ADODB.Connection
    With cn

    .Provider = "Microsoft.Jet.OLEDB.4.0"
    .ConnectionString = "Data Source=C:\TEST\test.xls;" & _
    "Extended Properties=Excel 8.0;"
    .Open

    End With

    '''''''''''''''''''''''''''''''''''''''''


    Roberto Patuelli SEM2000



    Sunday, October 15, 2017 6:11 PM
  • Thanks bascoure,

    it work for me too.

    Monday, October 16, 2017 12:46 AM
  • Hello there,

    Same behaviour with my Windows 7. I have a Brother P-touch that I link with an external Excel file as database.

    I must uninstall this KB4041681 if I want to print my stickers. Boring Microsoft..

     

     Bruno

    Monday, October 16, 2017 5:48 AM
  • As mentioned in forums.embarcadero.com/thread.jspa?messageID=902557&tstart=0 and forum.kanors-emr.org/showthread.php?tid=571&pid=2652#pid2652, the KB4041681 installs version 4.0.9801.1 of msexcl40.dll.

    1. Find prior version (4.0.9801.0) of msexcl40.dll

    2. Place in another directory. They suggest the application directory, but since in the next step you will modify registry to point to this older version, it can probably go anywhere.

    3. Update registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Jet\4.0\Engines\Excel\win32 to point to the location from step 2.

    We have tested with Primavera 8.3.3 export to Excel function, and this solved the issue. As this is a third-party app we could not fix the app itself and needed this workaround.

    • Proposed as answer by arash_1910 Monday, October 16, 2017 7:26 AM
    Monday, October 16, 2017 5:55 AM
  • Dear fred.schulz

    Thank you very much for your solution.

    We have same problem in P6 8.2 , and also other third-party application which generate run time error.

    Now, P6 excel export works fine, and other application run successfully.

    Monday, October 16, 2017 7:25 AM
  • I confirm this solution as well.

    Monday, October 16, 2017 7:36 AM
  • Confirmed fix for us too. thanks.


    Monday, October 16, 2017 8:40 AM
  • We are experiencing the same issue.

    We have had issues the last two months with the rollup updates. This is just unacceptable from Microsoft, removing the granularity of updates and then hosing them.

    Sincerely,
    Hunter

    Monday, October 16, 2017 3:27 PM
  • it works perfectly ..thank you so much
    Monday, October 16, 2017 4:48 PM
  • read fred.schulz  commenst...his solution works
    Monday, October 16, 2017 4:49 PM
  • We've found that if you are trying to export a query from Access 2003 into Excel the following works.

    Instead of exporting to Excel, choose tools, Office Links, Analyze it with Microsoft Office Excel, it will create the spreadsheet without error. I believe it defaults to the documents folder.

    • Proposed as answer by Rowdyreda Tuesday, October 17, 2017 2:06 PM
    Tuesday, October 17, 2017 2:06 PM
  • We had issues exporting to .xls from one our programs and issues using .xls as a datasource in a Crystal Report (don't ask).  Exporting as .csv was a work-around for the first, removing both 4041687 and 1678 was a solution for the second.   The correct response would be to update our datasources.  That fix is going to take more time and this was holding up production.  

    Thank you everyone for your efforts and posts. 

    tech notes:

    I used WSUS to decline the updates and PDQ deploy to run the removal command.

    wusa.exe /uninstall /kb:4041678 /quiet /norestart 

    -B

    Tuesday, October 17, 2017 3:47 PM
  • Yeah, the Brother P-Touch issue is hosing a half-dozen of my machines around here.  Connecting to a .xlsx does no good, because those aren't editable from within the P-Touch software. 

    Going to try installing the older .dll fix.

    Awesome.


    • Edited by AJRaven Tuesday, October 17, 2017 6:21 PM
    Tuesday, October 17, 2017 6:19 PM
  • Same problem creating and reading Excel with ODBC.
    Furthermore SQLGetInstalledDrivers crash (I compile for XP),
    FIRSTROWHASNAMES and CREATE_DB are not 
    recognized in connection string.
    Tuesday, October 17, 2017 8:30 PM
  • Thank bascoure, It work well for me.
    Wednesday, October 18, 2017 4:31 AM
  • I had the same problem and was able to fix it thanks to what was proposed by bascoure, oh and I didn't have to switch from xls to xlsx.

    Thank you bascoure.

    Thursday, October 19, 2017 7:02 PM
  • I found a solution but temporary. No need remove patchs. 

    Open .XLS Excel File and 1 click CELL and after try import excel file in your program (dont close excel file)

    ALSO

    You have patchs and Install 32 bit accessDtabaseEngine and xlsx (Ace 12.0) work. But If you have 64 bit Office and u can not install AccessDatabaseEngine (32 bit) and you can install 64 bit AccessDatabaseEngine and you can not import excel (not work for me) 

    But that solution "Open .XLS Excel File and 1 click CELL and after try import excel file in your program (dont close excel file)" ITS WORK.



    • Edited by HsyN07x Monday, October 23, 2017 11:06 AM
    • Proposed as answer by HsyN07x Friday, October 27, 2017 10:59 AM
    • Unproposed as answer by HsyN07x Friday, October 27, 2017 10:59 AM
    Monday, October 23, 2017 11:04 AM
  •  use AccessDatabaseEngine.exe /passive

    Monday, October 23, 2017 12:01 PM
  • The easiest way to repair it without having to hack the registry, etc
    Depending on what Windows Version listed here:

    KB4041676 -- Windows 10 Version 1703
    KB4041691 -- Windows 10 Version 1607 and Windows Server 2016
    KB4041693 -- Windows 8.1 and Windows Server 2012
    KB4041681 -- Windows 7 and Windows Server 2008 R2

    Just Open a Administrator CMD window and remove the following updates
    by pasting this into the command line:

    wusa /uninstall /kb:4041676
    wusa /uninstall /kb:4041691
    wusa /uninstall /kb:4041676
    wusa /uninstall /kb:4041693
    wusa /uninstall /kb:4041681

    It will take a few minutes to search the system, If the update is found, click Yes
    to uninstall, then reboot the machine, do this for as many updates
    as needed until it's back to normal. Then disable Automatic updates from
    Windows Update in the Control Panel, and you should be back to normal. Until,
    Microsoft fixes this, it's going to continue to cause problems for people.
    • Proposed as answer by Datamagnet Thursday, October 26, 2017 6:56 PM
    Monday, October 23, 2017 4:38 PM
  • Hello,

    sorry for the amateur question...but where exactly do you change to this?

    using (OleDbConnection conObj = new OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\\a.XLS;Extended Properties=Excel 8.0;"))
                {
                    conObj.Open();

    Thank you!

    Wednesday, October 25, 2017 9:31 AM
  • The easiest way to repair it without having to hack the registry, etc
    Depending on what Windows Version listed here:

    KB4041676 -- Windows 10 Version 1703
    KB4041691 -- Windows 10 Version 1607 and Windows Server 2016
    KB4041693 -- Windows 8.1 and Windows Server 2012
    KB4041681 -- Windows 7 and Windows Server 2008 R2

    Just Open a Administrator CMD window and remove the following updates
    by pasting this into the command line:

    wusa /uninstall /kb:4041676
    wusa /uninstall /kb:4041691
    wusa /uninstall /kb:4041676
    wusa /uninstall /kb:4041693
    wusa /uninstall /kb:4041681

    It will take a few minutes to search the system, If the update is found, click Yes
    to uninstall, then reboot the machine, do this for as many updates
    as needed until it's back to normal. Then disable Automatic updates from
    Windows Update in the Control Panel, and you should be back to normal. Until,
    Microsoft fixes this, it's going to continue to cause problems for people.
    Do you know the KB number for Win10 1710 ? Those KBs are not installed here and i still have the bug
    Wednesday, October 25, 2017 1:32 PM
  • This worked for me, I would only add that my location was in:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel\win32

    Thanks for the great fix!
    Wednesday, October 25, 2017 5:14 PM
  • As mentioned in forums.embarcadero.com/thread.jspa?messageID=902557&tstart=0 and forum.kanors-emr.org/showthread.php?tid=571&pid=2652#pid2652, the KB4041681 installs version 4.0.9801.1 of msexcl40.dll.

    1. Find prior version (4.0.9801.0) of msexcl40.dll

    2. Place in another directory. They suggest the application directory, but since in the next step you will modify registry to point to this older version, it can probably go anywhere.

    3. Update registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Jet\4.0\Engines\Excel\win32 to point to the location from step 2.

    We have tested with Primavera 8.3.3 export to Excel function, and this solved the issue. As this is a third-party app we could not fix the app itself and needed this workaround.

    This fix is ok for a dev machine but we can't do that on every customer machine :/

    Thursday, October 26, 2017 7:20 AM
  • I found a solution but temporary. No need remove patchs. 

    Open .XLS Excel File and 1 click CELL and after try import excel file in your program (dont close excel file)

    ALSO

    You have patchs and Install 32 bit accessDtabaseEngine and xlsx (Ace 12.0) work. But If you have 64 bit Office and u can not install AccessDatabaseEngine (32 bit) and you can install 64 bit AccessDatabaseEngine and you can not import excel (not work for me) 

    But that solution "Open .XLS Excel File and 1 click CELL and after try import excel file in your program (dont close excel file)" ITS WORK.



    One question. Does it work for exporting from Access to Excel too?
    Thursday, October 26, 2017 8:39 AM
  • In our VB program we programatically export from an Access DB and into Excel. This solution of removing the offending update worked for us.


    DataMagnet

    • Proposed as answer by AntoNaz Monday, October 30, 2017 11:55 AM
    • Unproposed as answer by AntoNaz Monday, October 30, 2017 11:55 AM
    Thursday, October 26, 2017 6:56 PM
  • Thanks Fred Schulz

    1. Find prior version (4.0.9801.0) of msexcl40.dll from a pc where update has not taken place C:\Windows\System32

    2. Place in another directory e.g. C:\ProgramData\JET_FIX

    3. Update registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel\win32old to point to the location from step 2. e.g. C:\ProgramData\JET_FIX\msexcl40.dll







    • Proposed as answer by AntoNaz Monday, October 30, 2017 12:00 PM
    • Edited by AntoNaz Monday, October 30, 2017 4:29 PM
    Monday, October 30, 2017 11:59 AM
  • Thanks a lot.

    I could not find 4.0.9801.0 version.

    But I downloaded 4.0.9756.0 version from here

    https://www.opendll.com/index.php?file-download=msexcl40.dll&arch=32bit&version=4.0.9756.0#

    and change the registry settings as you mentioned in step 3. Now my application is working proper. 


    VB6.0 bilgisi ile WP7.1 uygulaması yazmaya çalışan Türk..

    Saturday, November 4, 2017 10:08 PM
  • Any news on this?

    I still have the problem.

    I don't want to change registry, or install old DLL version, or nothing. I can't do that on custummer PCs. I need a fix from the same who introduce it (Microsoft).

    MS silently broke my system, MS should "silently" fix it.

    Thanks.

    Tuesday, November 7, 2017 2:07 AM
  • Opening the excel file I want to import into Access, clicking on any cell in the worksheet and leaving it open whilst I imported file worked for me. Thanks.
    Tuesday, November 7, 2017 7:27 PM
  • Hello at all,

    after i have uninstalled the update KB4041681 and and try to export contacts from MS Outlook to Excel,

    i receive the following message:

    A file error has occurred in the translator while trying to save a field map.

    The file "C:\Users\admin\AppData\Roaming\Microsoft Excel.ADR"
    was not found by the translator. Check the spelling of the file name and path.

    We are using Windows 7 Professional x64 with MS Office 2003.

    I have already tried to reinstall Office but it doesn't solve the issue.

    I don't have a user called "admin" on the clients. 

    I would be thankful about some tips to resolve it.

    Thanks in advance and best regards,

    Niklas

    Wednesday, November 15, 2017 10:12 AM
  • Has anybody an idea?
    Friday, November 17, 2017 10:57 AM
  • A different forum? I can't see any relation to SQL Server.

    Although Office 2003 does not look like a good start. No matter how much I could love for it being the last version without the ribbon, I suspect it is out of support.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Friday, November 17, 2017 4:34 PM
  • Hello Erland,

    i dont know why the issue should be related to SQL Server.

    I know that MS Office 2003 is out of support, but i have the same

    issue with MS Office 2016. 

    Currently we are upgrading all clients from Office 2003 to 2016.

    There must be a converter installed on the system, which is linked to

    the path in the error message. I have searched in the whole registry 

    to find any path like I mentioned above.

    I assume that there is maybe no Office issue. It must be a converter which

    is registered in Windows 7. It could be a converter from ODBC.

    Thanks in advance and best regards,

    Niklas

    Sunday, November 19, 2017 1:27 PM
  • i dont know why the issue should be related to SQL Server.

    You are however asking for help in a forum for SQL Server Data Access. Which may explain why you are not getting much help here.

    What forum you should ask in, I don't really know. But probably something related to Office.


    Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

    Sunday, November 19, 2017 3:56 PM
  • Okay thank you Erland.

    I will switch to a Microsoft Office Forum.

    Monday, November 20, 2017 8:14 AM