Knowledge Base

Connection to Excel .XLS data sources fails when using Microsoft Jet 4.0 OLE DB Provider


When you use NiceLabel to connect to Excel .XLS type of data files, NiceLabel will use database driver "Microsoft Jet 4.0 OLE DB Provider" by default. After October 10, 2017, you might not be able to connect to such data sources anymore.

NOTE: Connection to .XLSX type of Excel file is unaffected.

The following would happen in NiceLabel software:

  • NiceLabel V2017. You would see the system error message "Unexpected error from external database driver (1)."
  • NiceLabel V6. You would see the "Database Login" dialog box, prompting you for the user name and password.

Windows updates from October 10, 2017 were the culprit for this problem.



Microsoft has published known issues for the October 10th Windows update. Read this document.

The problem is solved with .NET Framework November 2017 Security and Quality Rollup released on November 14 with the following updates. We recommend that you update your Windows system with the latest updates.

  • Windows 10 Version 1709: KB4048955
  • Windows 10 Version 1703: KB4048954
  • Windows 10 Version 1607 and Windows Server 2016: KB4048953
  • Windows 10 Version 1511: KB4048952 (for Windows 10 Enterprise and Windows 10 Education editions only), KB4052232
  • Windows 10 Version (initial version released July 2015): KB4048956
  • Windows 8.1 and Windows Server 2012 R2: KB4048958 (Monthly Rollup), KB4048961 (Security-only update)
  • Windows Server 2012: KB4048962
  • Windows 7 and Windows Server 2008 R2: KB4048957 (Monthly Rollup), KB4048960 (Security-only update)

If you cannot update the system with the November 14 updates just yet, the following workarounds are available.


This workaround is applicable in NiceLabel V2017 and NiceLabel V6.

Remove the Windows update that causes the problem. Find the update id for your Windows system in the list below and remove it.

  • Windows 10 1703: KB4041676
  • Windows 10 1607 and Windows Server 2016: KB4041691
  • Windows 10 1507: KB4042895
  • Windows 8.1 and Windows Server 2012 R2: KB4041693
  • Windows Server 2012: KB4041690
  • Windows 7 and Windows Server 2008 R2: KB4041681, KB4041678 and KB4041686.

To remove the update, do the following:

  1. Open Control Panel.
  2. Navigate to Programs and Features>Installed Updates.
  3. Find the update with the KB number in its description.
  4. Click Uninstall.

Then make sure to temporary disable automatic updates, or Windows will install the update again at next update check. If you do now know how to change the update mode, read this article for details.


This workaround is applicable only in NiceLabel V2017.

NiceLabel 2017.3 has been released on October 27, 2017. NiceLabel 2017.3 will use ACE provider to connect to .XLS Excel data sources, even if you have initially configured JET provider on the labels. The switch happens automatically in the background, when you open a label. ACE provider is backwards compatible with JET provider, so there will be no issues making the switch.

NiceLabel 2017.3 will use ACE provider also for each new .XLS Excel file that you will use on the label. If ACE provider is not available, NiceLabel 2017.3 will downgrade to JET provider.

The ACE provider is installed with Microsoft Office products, but can also be installed separately, if needed (you can download it from Microsoft). You can install either 32-bit or 64-bit ACE provider, NiceLabel 2017 will use the one you have installed.

To upgrade your NiceLabel 2017 to 2017.3 release, download the trial installer here and install new version on top of the existing one, overwriting it, but keeping all settings and preferences.

If you cannot upgrade to NiceLabel 2017.3 (from one reason or another), you can change the data provider yourself. Change the provider from "Microsoft Jet 4.0 OLE DB Provider" (JET) to "Microsoft Office XX.0 Access Database engine OLE DB Provider" (ACE) (XX represents a version number of your database provider). You will have to do it for each label separately.

Print document   Email document


Did this article help you? *