Excel, Microsoft Technologies, Power BI, SSIS

Installing the Microsoft.ACE.OLEDB.12.0 Provider for Both 64-bit and 32-bit Processing

I recently got a new laptop and had to go through the ritual of reinstalling all my programs and drivers. I sometimes work with SSIS locally to import data from Excel and occasionally do demos with Power BI where I read from an Access database so I needed to install the ACE OLE DB provider.  If you try to do either of those things without the ACE OLE DB provider you will get a message like the one below.

The ‘Microsoft.ACE.OLEDB.12.0’ provider is not registered on the local machine.

I needed both the 32-bit and the 64-bit adapters to cover my various use cases. I started by installing the 64-bit Microsoft Access Database Engine 2010 Redistributable.  If you have ever attempted this, you know there is a secret. You cannot install the 2010 Access database engine with a different processing architecture (bittedness) from your Office install (or install both versions of the 2010 Access database engine) without a workaround.  If you try, you will get an error message.

ACE engine bittedness error

There are two options for getting the other version installed.

Option A: Install the 2007 Office System Driver: Data Connectivity Components

The 2007 Access database engine can read the same format, but didn’t have a 64-bit install. It doesn’t have the check to see what other products are on your machine and can co-exist peacefully with the 64-bit 2010 Access engine.

Option B: Install from the Command Line and Use the Passive Switch

  1. Open the command prompt.
  2. Type the file path and file name for your Access Database Engine install file.
  3. Follow it with a space and then “/passive” and then hit Enter.
  4. Delete or rename the mso.dll registry value in the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Common\FilesPaths

Note: A helpful commenter has informed me that for Access 2016 the switch is /quiet rather than /passive.

ACE install cmd

I wrote up a document for this a while back for a client, but I can never remember where I put it. So I’m posting this on my blog to make this info easier to find for me as well as you.

38 thoughts on “Installing the Microsoft.ACE.OLEDB.12.0 Provider for Both 64-bit and 32-bit Processing”

  1. a trio of questions:
    a. why 2010 and not 2013 or 2016?…just wondering
    dos. where does one get the download of AccessDatabaseEngine_x86.exe (64 bit version)
    III. did you have Office professional such that there was Access 32 bit also…and is this affected?

  2. Hi, Jim. Thanks for your comment. The format didn’t change much from 2010 to 2016 so unless you are looking for a specific features the 2010 driver will often work for a 2016 file. You can substitute the ACE 14 driver and you have the same problem here. I just happened to be dealing with the 12 driver.
    You can get the 64-bit Access engine at https://www.microsoft.com/en-us/download/details.aspx?id=54920. Just choose AccessDatabaseEngine_X64.exe when prompted.
    I have 64-bit office, but occasionally need the 32-bit driver when working on SSMS/SSIS imports. I originally ran into this issue when many of my clients were running 32-bit Office and I had them install 64-bit Power BI, which then required the 64-bit ACE driver. If you have 32-bit Access, you will run into the issue I have documented.

    1. Office 32 bit has long been the recommended install. So as we know the Power BI 64 bit won’t connect and this is the dilemma (although I noticed there is no problem connecting to excel, just Access tables…).

      Once you’ve downloaded the 64 bit driver; it is unclear to me how that is implemented. I assume it is installed into the machine with Office 32. Next, for instance, in PBI (which often is a separate machine) when you select the Data Source you are going to use file explorer to find the Access file and I don’t see at what point one has the opportunity to select the newly installed 64 bit driver. Admittedly I am typing this without yet having tried it and so just recalling my past linking attempts to an Access table.

      1. When using Power BI Desktop, you do not get to select the driver. Power BI searches for the appropriate driver that matches the processing architecture. So if you have 64-bit Power BI, it will look for 64-bit ACE driver in the expected install location. The driver does get installed when you install Access (or a version of Office that includes it), but it’s not installed by default with versions of Office that don’t include Access.
        32-bit Office is the recommended install for most business users, but anyone working with Power Pivot in Excel pretty much needs 64-bit office. So I have 64-bit office for that reason.

      2. I appreciate your patience with me. (I am displaying my lack of understanding of drivers.) So the real world is this: Access has long been installed, 32 bit, for many years. Along comes new-comer Power BI wanting to connect to tables (64 bit). Telling the user they must re-install Office 64 bit will be not generally welcomed. But if I can install a 64 bit driver and PBI will find/use that – it’s a great approach…and the users aren’t involved at all. Can it work this way?

        I’ve got a test environment I’ll try out next……

  3. So as we know the Power BI 64 bit won’t connect and this is the dilemma (although I noticed there is no problem connecting to excel, just Access tables…). […] la version 64 bits et 32 bits en même temps, vous pouvez suivre l’article de  blog de Meagan Longoria pour avoir le […]

  4. […] la version 64 bits et 32 bits en même temps, vous pouvez suivre l’article de  blog de Meagan Longoria pour avoir le […] 12.0 Provider for Both 64-bit and 32-bit Processing (@mmarie) […]

  5. The technic of the /passive switch will not work with the MS Access Engine 2016 at all, stick to MS Access Engine 2010

  6. Hello Meagan
    I’m wondering if you could help me out, I have the same issue that you posted on this forum. I have 64 bit Windows , 32 bit MS office. I was told to the following:

    -Uninstall the 32-bit Database Access Engine
    -Uninstall the 64-bit Database Access Engine
    – Uninstall your 32-bit Office
    – Reboot the computer
    – Reinstall the 32 bit office
    – Reinstall the 32bit Database Access Engine.
    – Reinstall the 64-bit Database Access Engine.

    If this processsed is incorrect, please let me know the correct process. I had also tried the suggested on this page, but still no joy. Anything you can help on this matter, will be greatly appreciated.

    1. I think you will still run into the issue I noted in this post when you get to installing 64-bit Access after installing the 32-bit Access. If you are installing newer versions of Access, try /quiet instead of /passive.

  7. Wowwwww
    Amazing !!
    Thanks !!

    Works using option /quiet
    My Installation is Office 2016 32 Bits

  8. Thank you! Big help! I was able to install both the 32-bit and 64-bit driver in minutes with the /quiet flag on my PC, and SSIS works now.

    1. Great solution .working fine for me.my system is 64 bit with 32 bit office .I tried your option 2 and its working for me

  9. When you have two versions of this driver installed (and using office 365 64 bit) you will need to be careful if you ever need to repair office because it will wipe all your office applications off because it detects the 32 bit driver!

  10. I’m not having luck with option B? I’m getting a “AccessDatabaseEngine_x86.exe is not recognized as an internal or external command, operable program or batch” Any hints??

      1. Hi Meagan — Thanks for the tip and the pointer, but man am i confused now. Are you saying that screen shot image above in this article has incorrect syntax?

        fyi — I’m on a win 7 64 bit machine and my ms office was loaded as 64 bit…

        I can’t fathom that all these others folks had no issues using that screen shot as a guide.

        When I had problems the first time executing from another directory I moved it to my version of his directory to match syntax perfectly. I even realized the x64 references was in fact X64 on the download file I got, but none of that made any difference (it still wouldn’t fire).

        The article you posted requires a pretty interesting move that I wouldn’t have known to do. Did this author and everyone else know to specify executable paths and use a different syntax? Or maybe my machine got a goofy reinstall where the executable dirs are listed properly?

        On a different note, when I got stumped, I decided to try to remove the 32 bit stuff that was conflicting and install. That went okay, but then my use of ACE was still not working (localhost website accessing a msaccess db).

        I tried to load the 2007 32 bit. That went okay, but then I got an error implying the db name was ”.

        I then tried to load the 32 bit for 2010 but ran into a conflict with a one image windows thingy… (seems on reload my IT guys used a bloated all in one windows image that included 32 and 64 bit stuff)… and I was going to have to uninstall all of ms office that had been installed on a reinstall from some magical image that had a bunch of stuff including both 32 and 64 bit stuff.

        Worrying I was now in a Microsoft black hole… I went into IIS and went into the application pool and turned OFF the use of 32 bit applications (luck that I remembered I could do that..)

        And magically, that allowed the 64 bit ACE driver to fire properly when requests came from the localhost.

        And then i reloaded the 32 bit software I had to unload to get the 64 bit ACE driver on the machine…

        Dunno what I’ll do if/when I need to use those 32 objects I had purchased a while back.. .upgrade I guess. or try to uninstall all of office or switch to UNIX as that total time invested may be less?!

        I don’t know how I got this to work years ago when I first set it up. Maybe I had to do the same, but i didn’t have documented. I do now.

        If there is anything you can clarify about why the image above doesnt work that’d be great.. and it may make sense to reference this problem and that link for anyone else who stumbles here hoping for help but gets tossed into a different ms command line grinder.

  11. I’m trying to provide a one-size-fits-all installer for my users. Is there anything they would miss from the 32-bit 2007 version? i.e. Do they need 64-bit? Most have Office 32-bit but a few have 64 or have installed the 64-bit version of 2010 on top of Office 32-bit and then have issues updating Office.

    1. If one is a Power BI user – then the OS (Win 10) should be 64 bit.

      In general – and overwhelmingly – the recommended Office install is 32 bit. This can sit on an OS of 64 bit. The reason for the recommendation is that Word, PowerPoint even Access cannot use the benefit of 64 bit plus there are peripherals out there with drivers that are only 32 bit capable.

      But if one is a Power BI user then one might also be a real power Excel user – and it is the high end of Excel – millions of rows – that needs 64 bit.

      The next part of this is that it means that for Power BI users – for whatever reason it can read/import 32 bit excel data no problem but not 32 bit Access. At least this was true through 2017 and I’m not sure if that has changed or not. My quick & dirty work around was to export the Access table to excel. Otherwise the help of this thread on installing both drivers could be your solution.

      1. In our environment it’s more likely legacy applications that need this connectivity. I’m guessing 32-bit (we almost exclusively install 32-bit Office). Is there any need for the 64-bit database engine?

      2. If all of the applications that must interface with the ACE engine are 32-bit, then you won’t need 64-bit database engine. Power BI is usually 64-bit and therefore requires the 64-bit driver. As mentioned above, hardcore Excel users might be 64-bit. Those who are using 64-bit Office might need the 32-bit ACE for other 32-bit applications (like Visual Studio in my case).

  12. Hi Meagan, I would like to comment on your post made on Feb 27, 2018. I have a very similar situation and need clarification. I developed a program using Visual Studio 2017 that uses an access database. I created the database as an MDB to be more generic. The installer program I created works perfect on my computer which is a a Windows OS 64 bit machine running M.S office 2016 64 bit. But when I run the installer on a users Windows OS 64 bit machine running M.S. Office 2013 32 bit, I get the MS Ace.oledb.12.0 not registered error. My installer program detects the 2013 32 bit office and installes the 32 bit accessdatabase engine.exe. But I still get the same error. It sounds like your saying that If I execute the 2013, 32 bit accessdatabaseengine.exe using the /passive switch I won’t get the error message. Is that correct? Additionally, for my situation, will I need to modify any registry keys? Thank you in advance for your reply.

  13. Thank you for your post, now i have both 32 bit and 64 bit versions of ACE 2016, along with Office 2016 64 bit, SSIS 32 bit from SSMS 17 and VS 64 bit, running like a charm 🙂
    I went on installing with Option B. To install ACE 2016, for me, it worked with /quiet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s