Sage 100

hi there - Anyone have crystal reports connected to excel? Today when trying to run at a customer site or on my local workstation get the attached error message. To test in crystal i just did a new blank report, choose create new connection >> Access/Excel and select any excel sheet (tried new blank sheet, tried existing sheets) and click finish. error pops up immediately. I ~think~ its an excel driver issue but will keep looking.

I had issues like this and it was an issue with a user on an older version of excel opening and saving the file. I would have to open it in the newer version and just save it and then it stated to work again.

My case the file was an xlsm using the database type excel 8.0

I have a client that got the same error message beginning yesterday. They went to Office 365 about a week ago and it appears to have worked after the conversion. I have not found any solution yet.

I heard from my client having the issue. Here is what their IT did to resolve the issue: 1. Office 2016 would not update. Had to do a clean uninstall. https://support.office.com/en-us/article/Uninstall-Office-from-a-PC-9dd49b83-264a-477a-8fcc-2fdf5dbf61d8?ui=en-US&rs=en-US&ad=US 2. Re-installed Office 2016 3. Excluded workstation from updates: KB4041681 & KB4041678 https://social.technet.microsoft.com/Forums/en-US/45ebe780-967e-4748-a146-9ec7a15626dc/unexpected-error-from-external-database-driver-1?forum=itmanager It appears to be the KD's causing the problem.

Hi all - thank you for your comments/help. @ScottFirgens you were right about the updates: KB4041681 & KB4041678. The issue is with MSEXC140.dll. To resolve the issue use a prior version of msexc140.dll (i have a copy from 3/2017 that works if anyone needs it). Place it in a new folder - I put mine at c:\temp\ (the original will be located at C:\Windows\SysWOW64\msexcl40.dll on windows 10) Then edit the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Jet\4.0\Engines\Excel\win32 and replace the contents with the directory location of the new folder where you placed the older version of the MSEXC140.dll file. For mine it was C:\Temp\MSEXC140.dll. Then the connections to the Excel sheets will work again. Found the answer to this at the following link(that @Scott Firgens provided): https://social.technet.microsoft.com/Forums/en-US/45ebe780-967e-4748-a146-9ec7a15626dc/unexpected-error-from-external-database-driver-1?forum=itmanager We'll see if Microsoft releases an update tomorrow for this.

I had IT uninstall the KB4041681 update, reboot and all was good. They are going to look for an older version of the affected .dll before next Tuesday's updates.

I found this, this morning: kenhamady.com/cru/archives/2841

hi - if anyone needs the older dll I posted one on our website to download in zip file format. Its from March 2017. here is the link: http://www.technology-integrators.com/wp-content/uploads/msexcl40.zip