export to another format, such as xlsx, csv use proc export, etc.). We plan to contact Microsoft regarding this issue.įor now, there are some workarounds in EG (ex. Also, EG users can't make use of the Microsoft suggested workaround (above), since the EG application would have to be changed to implement the workaround. Microsoft has not provided a resolution at this time.

(If you wish to confirm this is the issue, turn on EG logging (in Tools->Options->Application Logging), reproduce the problem, then search your EG log for the error message, 'Unexpected error from external database driver'.) Microsoft is working on a resolution and will provide an update in an upcoming release. Example: Change Provider=.4.0 to Provider=.12.0. Yet this morning I have systems either not booting because they've been broken by applying both, or systems that are still working because they are still pending reboot from having both of these updates installed. (Microsoft JET Database Engine)'.ĭownload and install the Microsoft Access Database Engine 2010 Redistributable, and then modify the DB connection strings in Microsoft Excel to use ACE as a provider. I have approved Cumulative Update for KB4041691 in WSUS, but I have not approved the Delta Update for KB4041691.

The error message is, “Unexpected error from external database driver (1). Installing this update may cause applications based on the Microsoft JET Database Engine (Microsoft Access 2007 and older or non-Microsoft applications) to fail when creating or opening Microsoft Excel. It sounds like you may be encountering an issue that was introduced with this recent () Microsoft update:

Kb4041691 failed to install