topic RE: The 'Microsoft.ACE.OLEDB.16.0' provider is not registered on the local machine in Digital Exchange

The 'Microsoft.ACE.OLEDB.16.0' provider is not registered on the local machine

astrid.stollberger — Fri, 20 May 2022 13:23:00 GMT

Hi,

I'm trying to use OLEDB to connect to an Excel file.
This worked fine as long as the Robot was running on MS2016.
After migration to (Click-to-Run) M365 I'm getting this error: "The 'Microsoft.ACE.OLEDB.16.0' provider is not registered on the local machine."

I can see OLDEB drivers are registered in the registry, but I have the feeling Blue Prism can't find them for some reason....

------------------------------
Cheers Astrid
------------------------------

RE: The 'Microsoft.ACE.OLEDB.16.0' provider is not registered on the local machine

PabloSarabia — Fri, 20 May 2022 13:55:00 GMT

Hi @astrid.stollberger

Did you try reinstalling this one: https://www.microsoft.com/en-us/download/details.aspx?id=54920? Maybe is an internal problem and repairing the installation it fix.

Hope this helps you!!

See you in the Community, bye 🙂

------------------------------
Pablo Sarabia
Solution Manager & Architect
Altamira Assets Management
Madrid
------------------------------

RE: The 'Microsoft.ACE.OLEDB.16.0' provider is not registered on the local machine

devneetmohanty07 — Fri, 20 May 2022 14:09:00 GMT

Hi Astrid,

This error usually comes when the correct drivers are not installed on the machine or any version conflict occurs. You can try with Access Database Engine 2010 installation file from here: Microsoft Access Database Engine

I am also using M365 and was able to resolve this issue when I was getting the same error. The version Access Database Engine 2010 seems to work for me but not 2016 for some reason:

------------------------------
----------------------------------
Hope it helps you out and if my solution resolves your query, then please mark it as the 'Best Answer' so that the others members in the community having similar problem statement can track the answer easily in future

Regards,
Devneet Mohanty
Intelligent Process Automation Consultant | Sr. Consultant - Automation Developer,
Wonderbotz India Pvt. Ltd.
Blue Prism Community MVP | Blue Prism 7x Certified Professional
Website: https://devneet.github.io/
Email: devneetmohanty07@gmail.com

----------------------------------
------------------------------

RE: The 'Microsoft.ACE.OLEDB.16.0' provider is not registered on the local machine

astrid.stollberger — Fri, 20 May 2022 14:14:00 GMT

Thanks, Pablo, but I can't re-install this as the OLEDB drivers come with M365 build on our VMs, so that's not an option...

------------------------------
Cheers Astrid
------------------------------

RE: The 'Microsoft.ACE.OLEDB.16.0' provider is not registered on the local machine

astrid.stollberger — Fri, 20 May 2022 14:18:00 GMT

Hi Devneet,

we used MS Access 2010 DB Engine (x32) on MS2016 but with M365 we would like to get away from 32-bit components as Microsoft will no longer support them:
Can't use the Access ODBC driver or OLEDB provider outside Office Click-to-Run - Office | Microsoft Docs
"

The Microsoft Access Database Engine 2010 Redistributableis no longer suggested as a recommended solution because Office 2010 has reached the end of the Microsoft Support Lifecycle.

"

I already found out that although the Blue Prism installer is 64-bit, the core processes such as automate.exe etc. still run in 32-bit which probably causes the issue.
However, I also read that Blue Prism is certified to work with 64-bit applications like Word, Excel etc., so I thought I give it a try.
Still, Blue Prism doesn't seem to find the ACEOLEDB.dll and I don't know how I could point it to the correct location...

------------------------------
Cheers Astrid
------------------------------

RE: The 'Microsoft.ACE.OLEDB.16.0' provider is not registered on the local machine

ewilson — Fri, 20 May 2022 22:48:00 GMT

Hi @astrid.stollberger,

Have you tried placing the DLL in the Blue Prism Automate folder?

Cheers,

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------

RE: The 'Microsoft.ACE.OLEDB.16.0' provider is not registered on the local machine

AtyantSrivastav — Mon, 23 May 2022 10:21:00 GMT

Hi Astrid,

I have gone through the similar problem and here is the solution for it:

Can you try the 32-bit ODBC software which has been proven to be more reliable for working with Blue Prism software, even on a 64-bit operating system.

You will need the 32-bit drivers. https://www.microsoft.com/en-us/download/details.aspx?id=54920 and install it with these instructions:

If Office 365 is already installed, side by side detection will prevent the installation from proceeding. Instead perform a /quiet install of these components from command line. To do so, download the desired AccessDatabaseEngine.exe or AccessDatabaeEngine_x64.exe to your PC, open an administrative command prompt, and provide the installation path and switch Ex: C:\Files\AccessDatabaseEngine.exe /quiet

------------------------------
Atyant Srivastava
Team lead
Personal
Asia/Kolkata
------------------------------

RE: The 'Microsoft.ACE.OLEDB.16.0' provider is not registered on the local machine

astrid.stollberger — Tue, 24 May 2022 12:05:00 GMT

Hi @ewilson,

I just tried that but unfortunately still getting the same error...

------------------------------
Cheers Astrid
------------------------------

RE: The 'Microsoft.ACE.OLEDB.16.0' provider is not registered on the local machine

astrid.stollberger — Tue, 24 May 2022 12:07:00 GMT

Hi @Atyant Srivastava,

as I mentioned above, we used MS Access 2010 DB Engine (x32) on MS2016 but with M365 we would like to get away from 32-bit components as Microsoft will no longer support them:
Can't use the Access ODBC driver or OLEDB provider outside Office Click-to-Run - Office | Microsoft Docs
"

The Microsoft Access Database Engine 2010 Redistributableis no longer suggested as a recommended solution because Office 2010 has reached the end of the Microsoft Support Lifecycle.

"

------------------------------
Cheers Astrid
------------------------------

RE: The 'Microsoft.ACE.OLEDB.16.0' provider is not registered on the local machine

Sheela — Mon, 01 Aug 2022 15:14:00 GMT

@astrid.stollberger

Could you please let me know whether you managed to resolve this issue.

------------------------------
Sheela Parthasarathy
Assistant Vice President
Deutsche Bank Group
Pacific/Apia
------------------------------

RE: The 'Microsoft.ACE.OLEDB.16.0' provider is not registered on the local machine

theBelovedKing — Tue, 20 Feb 2024 10:59:00 GMT

@astrid.stollberger and @Sheela Parthasarathy,

I know this is an old post. However, I was able to resolve a similar challenge I had experienced with this error, after about a year and a couple of months.

1. I uninstalled all instances of Microsoft Access Database Engine (2010, 2016) from Control Panel.

2. I downloaded the Microsoft Access Database Engine 2016 file from this Microsoft. Ensure you download the 32-bit version, as the 64-bit version still threw the same error after installing.

3. Open cmd, navigate to your downloads folder and execute this command: [file_path]/filename.exe /quiet. You can follow this guide.

Let me know how it goes.

Best regards,

------------------------------
Kingsley David
------------------------------

RE: The 'Microsoft.ACE.OLEDB.16.0' provider is not registered on the local machine

astrid.stollberger — Wed, 21 Feb 2024 12:09:00 GMT

Hi David,

as I mentioned above, we used MS Access 2010 DB Engine (x32) but we had to get away from 32-bit components as Microsoft will no longer support them.

We solved it now by down-grading the Office 365 installation to 32-bit so that Blue Prism can use the OLEDB drivers which come with the M365 installation. So at least we don't have a dependency now on the EOL MS Access 2010 DB Engine.

Cheers

Astrid

------------------------------
Cheers Astrid
------------------------------

RE: The 'Microsoft.ACE.OLEDB.16.0' provider is not registered on the local machine

ewilson — Wed, 21 Feb 2024 14:53:00 GMT

For everyone's reference, there are a couple VBOs that use OLEDB, in some fashion, including Data - OLEDB and Utility - File Management. I'm pretty sure every BP VBO that uses OLE DB has been updated to use the ACE provider in the default connection string as JET only supports 32-bit. With ACE, you have 32 and 64-bit options. However, you have to match the ACE driver to the BP architecture as well as the Office installation type.

What that means is a 32-bit installation of Blue Prism can only use a 32-bit installation of the ACE driver and a true 64-bit installation of Blue Prism (v7.3 or later) can only use the 64-bit version of the ACE. Please note, prior to BP v7.3, the 64-bit installer for Blue Prism didn't actually install a 64-bit version of the Automate.exe program. It is 32-bit. Yes, a little confusing, but that's the way it is.

You also must account for the Office version. If you have a 64-bit version of Office installed, it won't let you install the 32-bit version of ACE, as far as I know.

------------------------------
Eric Wilson
Director, Integrations and Enablement
Blue Prism Digital Exchange
------------------------------