web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :

Integration Manager "ODBC Excel Driver Login Failed - Unexpected error from external database driver (1)."

Karl Hendrickson Profile Picture Karl Hendrickson 111

Recently there was a Microsoft update that was release on October 10th, 2017 (list below), that are affecting Integration Manager when using the ODBC Excel Driver.

Once the update is applied to the server/workstation, user may experience the error message below when attempting to run an integration utilizing an older version of the ODBC Excel Driver for the DSNs.

ODBC Excel Driver Login Failed

    Unexpected error from external database driver (1).

Below is the verbiage from the Known Issues for the updates:

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 .xls files. The error message is, “Unexpected error from external database driver (1). (Microsoft JET Database Engine)".

To fix the issue, it may require that the workstation has Microsoft Access Database Engine 2010 Redistributable, Report Viewer Redistributable and 2007 Office System Driver: Data Connectivity Component installed, which will provided a newer version of the ODBC Excel driver. Then follow the steps below to update the DSN settings.

  1. Open the Object Browser in Integration Manager by navigating to Tools >> Object Browser.
  2. Select DSNs from the Types browser on the left side of the Object Browser. Then double click on DSN you need to modify.
  3. If the Driver for the DSN are Microsoft Excel (*.xls) or Driver do Microsoft Excel (*.xls) - or similar driver with single XLS type in the name, it will need to be changed to the driver named Microsoft Excel (*.xls, *.xlsx, *.xlsm, *.xlsb). (If you do not see the multiple driver types option, install the Office System Driver link above)
  4. Update the connection string - example below:

    DBQ=C:\someexcelfile.xls;DefaultDir=C:\;Driver={Microsoft Excel Driver (*.xls)};DriverId=790;FIL=excel 8.0;MaxBufferSize=2048;MaxScanRows=8;PageTimeout=5;ReadOnly=1;SafeTransactions=0;Threads=3;UID=admin;UserCommitSync=Yes;

     

    DBQ=C:\someexcelfile.xls;DefaultDir=C:\;Driver={MICROSOFT EXCEL DRIVER (*.XLS, *.XLSX, *.XLSM, *.XLSB)};DriverId=1046;FIL=excel 12.0;MaxBufferSize=2048;MaxScanRows=8;PageTimeout=5;ReadOnly=1;SafeTransactions=0;Threads=3;UID=admin;UserCommitSync=Yes;

Once this is complete, Integration Manager should be utilizing the correct ODBC Excel driver.

Comments

*This post is locked for comments

  • Community Member Profile Picture Community Member
    Posted at

    A million thanks for posting this. I have taken the trouble of signing up to Dynamics GP for the sole purpose of thanking you.

    I happened to be experimenting with some relatively advanced (for me - I'm no expert) code in Access VBA of Office XP at the time this update was installed. Therefore I just assumed I had broken a reference somewhere. Hours spent - including complete uninstall/reinstall/update of Office XP to no avail. Amazement followed when I found the problem had mysteriously migrated first to a second Win 7 machine where I backed up data and then to Win 10 as the dual boot on the original machine. Took a few search attempts but then found your post.

    My simple solution is to risk not having the security updates of KB4041681 and just uninstall it while waiting for the promised MS fix.  Main problem solved. Subsidiary problem was that a false reference had been created to Web Components and this had to be deselected. (Was showing as missing and creating an error message on load of database file.)

  • callen Profile Picture callen 4,595
    Posted at

    This article is unbelievably timely. Just today I had a client ask me about this issue. Thank you for putting out the article.