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.
- KB4041681 - Windows 7 SP1 and Windows Server 2008 R2 SP1
- KB4041690 - Windows Server 2012
- KB4041693 - Windows 8.1 and Windows Server 2012 R2
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.
- Open the Object Browser in Integration Manager by navigating to Tools >> Object Browser.
- Select DSNs from the Types browser on the left side of the Object Browser. Then double click on DSN you need to modify.
- 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)
- 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.

Like
Report
*This post is locked for comments