Error 6670 after installing Windows Updates Follow

Bob Steele

This article refers to a specific problem that happened in the fall of 2017. We've left this article here for historic reasons, but if you're currently experiencing Message 6670, it's unlikely that this article will help you. You should see this article instead: Error 6670 when using Microsoft Excel.


When printing or viewing Database Connection Setup in BarTender, you get:

  • Error Message #6670 – Failed to connect to database: unexpected error from database driver


  • Microsoft Windows Operating System
  • BarTender Designer (32-bit)
  • Microsoft Excel
  • Microsoft JET OLEDB Provider 

Any of the following October 2017 Windows Updates are installed

Operating System Windows Update Number
Windows 10 build 1703 KB4041676
Windows 10 build 1607, Windows Server 2016 KB4041691
Windows 8.1, Windows Server 2012 KB4041693
Windows 7, Windows Server 2008 R2 KB4041681




We have identified that the problem is in the Microsoft JET OLEDB Provider after installing October 2017 Windows Updates. Microsoft has released a series of updates that resolve the issue.

If you're experiencing this problem, please install the update that corresponds to the version of Windows that you're using.

Operating System Update that resolves issue
Windows 10 build 1709 KB4048955
Windows 10 build 1703 KB4048954
Windows 10 build 1607, Windows Server 2016 KB4048953
Windows 8.1, Windows Server 2012 KB4048958
Windows 7, windows Server 2008 R2 KB4048957



If you're unable to install those Windows updates, you can continue to use the workarounds listed here, but we highly recommend that install the latest Windows updates as soon as possible.

To force BarTender to use ACE you must have ACE installed on your system, and then you must recreate the database connection in BarTender.

To see if you have ACE Installed

  1. Open the Windows Control Panel
  2. Open Programs and Features
  3. Look for "Microsoft Access Database Engine Redistributable"
    1. The presence of this application indicates that you have ACE installed, proceed to " Updating your BarTender Documents"
    2. If you do not have this file, proceed to " Install the ACE Provider"
TIP: Advanced users can check for the presense of the this registry key:

HKEY_CLASSES_ROOT\Microsoft.ACE.OLEDB.12.0. If you have that key, then you have ACE installed.

Install the ACE Provider

Before following these steps, close any open BarTender instances.

If you didn't have ACE installed, then follow these steps to install it.

  1. Go to:
  2. Download the 32-bit version of the ACE Provider (AccessDatabaseEngine.exe)
  3. Run the executable to install Microsoft Access Database Engine Redistributable
  4. Once installed, proceed to "Updating your BarTender Documents"

Updating your BarTender Documents

Once ACE is installed on the machine, follow these steps to update your BarTender Documents.

Please note steps 3 and 4. You will lose those settings during this process.

  1. Open the BarTender Document affected
  2. Click File > Database Connection Setup
  3. Confirm the location of your Excel file
  4. Check the Query or Filter tabs and make note of any queries or filters that are setup
  5. Remove the current database connection by clicking the Remove button (10.1 and earlier) or the red 'X' button (BarTender 2016)
  6. Click Add to reconnect to your Excel document
  7. Recreate any Queries or Filters that were setup
  8. Repeat these steps for other affected BarTender documents

Remove Windows Update

You may also choose to remove the offending update from your computer. However, please be aware that there are several other important fixes included in those updates. You should review the release notes and your environment carefully before choosing to remove or prevent the Microsoft updates. We recommend that you leave the updates installed until Microsoft comments on the problem.

More Information

Microsoft has an official statement on this problem here:

JET is an older technology used to transfer data between Microsoft Office and other applications (e.g. BarTender). ACE is the replacement for JET and was introduced with new Microsoft Office packages.

BarTender attempts to use the ACE provider whenever it is available. BarTender will always use ACE in the following circumstances:

  • You are using a 64-bit version of BarTender (as there is no JET provider for 64-bit)
  • You are using newer Excel files (all newer files require ACE)

If you are using a 32-bit version of BarTender with older Excel files, you could be using JET or ACE, depending on your system configuration. When creating a new Database connection, BarTender will default to ACE if it is available. However, the connection preference is stored on a document specific basis.

Therefore, you must remove the documents JET connection and recreate the database connection with ACE installed on your system. From that point on, BarTender will always attempt to use ACE when using that document.

ACE is fully backwards compatible with all version of Excel documents. So there is no harm in updating to the ACE provider. You will still have JET installed on your computer, so any other applications that might need it can still access it (be aware that other applications trying to open Excel via JET will suffer this problem).


Dave Pere
Comment actions Permalink

We chose to uninstall KB4041676 (issued around Oct.10th 2017) to address this issue until further notice.

Rod Bolt
Comment actions Permalink

I've got clients using the older 9.2 - 10.1 that have had the same issues, I've resolved this issue with a few different clients and they all seem to be working with removing the update and turning off automatic updates. Just have one client who's automatic update just doesn't seem to want to go away. We have Bartender Automation 2016 here in the office and have not had the issue with our 32-bit Windows 7 system. Is this error around versions 10.1 and before or all versions of Bartender? I have a client wanting to upgrade to the latest version to resolve this issue but I don't want to sell it to him just in case it doesn't fix it.

Gene Henson
Comment actions Permalink

Hi Rod,

It certainly can affect BarTender 2016, however it is more likely to affect older versions of BarTender since older versions are all 32-bit. BarTender will always try to use ACE, so the machine that isn't affected may already have ACE installed. If you want to review that setup with us to see if it might be affected, feel free to open a ticket and we'll help you take a look at it.

Ian Wright
Comment actions Permalink

I'm using Bartender 2016 and having this problem, I'm unable to fix it.

Jason Howard
Comment actions Permalink

There is something at play other than the 4 updates listed above. I've disabled all 4 of them via patch management console, and BarTender STILL blows up after updates. This makes for a needle in a haystack scenario, to the point where the only recourse is to disable updates completely, per Rod Bolt's post. In my client's case, the only way to restore functionality was to use a restore to revert back to a point before the update(s) were installed. I don't like chasing ghosts, and a more upfront approach to troubleshooting would have been great. P.S. the conversion from JET to ACE provider did nothing to resolve the issue.

Carl Miller
Comment actions Permalink

We had issues installing and then configuring ACE. Fortunately
the connector was to an excel file, because I could convert it
to a text file and use that.

If you want to try this, open the excel file, type ctrl-a then ctrl-c.
Create a new text file and type ctrl-v. Close and save the file
Rename the file to match the excel file, but keep the .txt extension.

Next open each connector file and add a new connection to the
new file. Open the multi-database option and change each
occurrence of the excel file to the corresponding text file.
Finally, open the template and go into the properties of each
item. Check the data source and update it to use the new
text file.

When finished, open a "Print Preview" to ensure there are
no errors.

Marco Preziosa
Comment actions Permalink

I've installed ACE and smoothly fixed all the database related labels, up and running in a while.

Comment actions Permalink

The ACE fix worked well for me too.

Kevin Cutajar
Comment actions Permalink

Installing Office 32 bit worked for me.
Environment is: BarTender 10.1 SR4, Windows 7 64 bit, Office 2010 64 bit.

ACE install didn't work in this case.

Uninstall Office 64 bit first then install Office 32 bit.

jeremy clark
Comment actions Permalink

Is there a fix for Windows 10 build 1709? The fixes list do not address 1709.

Gene Henson
Comment actions Permalink

Hi Jeremy,

That was an omission on our side. Windows 10 build 1709 is addressed with this patch:

Thanks for pointing that out!

Please sign in to leave a comment.