How to fix Microsoft.ACE.OLEDB.12.0 provider is not registered on the local machine

Rhys Mckinnon 31

After trying to follow several solutions online none seem to be working. I'm using 64bit Microsoft access and 2019 visual studio and have already installed the engine from https://www.microsoft.com/en-au/download/details.aspx?id=13255. I've tried running visual studio on x86 and any cpu. Stumped on where to go next

Castorix31 81,741 Reputation points

2021-03-03T07:32:57.253+00:00

...several solutions

Which solutions ?

(BTW, the 2016 version is Microsoft Access Database Engine 2016 Redistributable )
(accessdatabaseengine_X64.exe)
Daniel Zhang-MSFT 9,616 Reputation points

2021-03-12T08:16:48.093+00:00

Hi @Rhys Mckinnon ,
I suggest you can try to use 32bit Microsoft access to check.
Regarding this problem, there are some solutions and suggestions have been provided in this thread.
Best Regards,
Daniel Zhang
Oli sicard 1 Reputation point

2022-08-26T13:13:10.773+00:00

Has this been resolved?

I am having the same problem, I have Office 2016, 64 version. I've downloaded the redistributables, and still getting not registered problem.

I have went into settings ticked off prefer 32-bit, tried anyCPU, 64, x86. Nothing works.!
Ashkan Khalili 1 Reputation point

2023-01-05T10:32:36.35+00:00

To solve this error try to install Access Database Engine 12, and you will be find :)
incase this didnt solve the problem, Install access Database engine 14.
Randall Edick 25 Reputation points

2023-04-03T14:50:26.0533333+00:00

I'm using the Community Edition of VS2022, built a winforms app on .NET.framework 4.7.2, I've installed the AccessDatabaseEngine_x64. I see it installed in the registry, but I'm still getting the error.
Raymond Larkin 1 Reputation point

2023-10-17T20:21:21.08+00:00

I have same scenario for 64 bit version. The 32 bit version of the engine will not install because Access 64 bit is installed. However, the 32 bit version will install from an Inno setup app and run fine. I have to find a solution for exposing C# methods to unmanaged code for 64 bit before I can compile the libraries for x64.
Jones, Ron@CSD 0 Reputation points

2023-10-19T16:17:44.08+00:00

I'm using the Community Edition of VS2022, updating a winforms app on .NET.framework 4.5, I installed the AccessDatabaseEngine_x64. I still got the error and then changed my target build to 64 bit and error was gone..

8 answers

Abdelmalek Aitouche 176 Reputation points

2021-03-03T11:56:14.95+00:00

Hi gents,

I have gone through the same issue after installing several Access, ADODB runtime redistributables but still had the same problem.
The solution is:
Go to project properties
Compile Tab
Scroll down to Advanced Compile Options
Target CPU: change between x86 , x64 and AnyCPU validate your selection and run debug to test.
I hope this will solve your issue.
Best regards,
A. Aitouche
Please sign in to rate this answer.

8 people found this answer helpful.
Dave Patrick 426.1K Reputation points MVP

2021-07-20T16:09:38.847+00:00

This was helpful as it got me to the right place to look. For me it seemed to be unchecking the box for Prefer 32 bit that did the trick.

Rout, Deepak Kumar 1 Reputation point

2021-09-24T12:08:55.83+00:00

What about the Exe file?

I have developed the code in one server where the application is running fine. But while I move the Exe to a different server and tried to run that exe after install the MS Access Database Engine software, it's not working there

Leonard Salazar 1 Reputation point

2022-01-29T22:18:35.543+00:00

thank you so much :)

Бойко Максим 1 Reputation point

2022-06-22T14:49:52.087+00:00

fixing the parameters in connecting to the database helped, changed it to this Provider=Microsoft.Jet.OLEDB.4.0;Data Source=DataBase.mdb

madhur surve 1 Reputation point

2022-09-03T05:05:14.827+00:00

thank you for the solution, it worked.

Mark Finn 6 Reputation points

2022-09-06T14:44:00.76+00:00

Just a quick correction. Not sure if it's because of Visual Studio updates over the past year since this answer, but the instructions cannot be followed as-is. There is no Compile tab in the project properties. Instead, go to the Build tab. Under General is where you will find the Platform target drop-down. That's where you can select your proper target. See my other post on this question for more information about strange behavior to keep in mind when tackling this issue.

Ashwini Kumar Vijayvargia 5 Reputation points

2023-04-19T03:27:04.9066667+00:00

I was facing the similar problem, in one project, while in other project running on the same machine working fine with the same connection string. Changing Target CPU, didn't work, But I removed the check 'Prefer 32 Bit' just below this option, and it worked. Thanks.
Sign in to comment
Thomas 31 Reputation points

2021-09-06T07:35:33.153+00:00
After some updates of Windows 10 and migration to Office 365 I did this:

Installing AccessDatabaseEngine_X64.exe (which did not directly solve the issue)

Visual Studio 2019: Project > <Project_Name> Properties > Target CPU > 'x64'

Thank you A. Aitouche!
Please sign in to rate this answer.

6 people found this answer helpful.
DB 1 Reputation point

2022-06-29T00:45:02.55+00:00

Thanks much for sharing your solution!

I had this issue today after continuing a project at home and running into this error.. switching my target cpu to x64 took care of it.. it was set to 'Any Cpu'

ismael polanco 1 Reputation point

2022-08-01T01:27:46.127+00:00

Excellent. Thanks a lot! Your answer it was the only one solution I found, and yes, if you have Office for x86, you need also need to run your application for x86 plattforms. Thanks bro!

Ashcannon 0 Reputation points

2023-04-17T03:56:17.86+00:00

Thank you. It helps a lot.
Sign in to comment
Max Santeramo 21 Reputation points

2022-06-02T15:16:55.177+00:00

I run into the same problem but nothing seems to work. I run windows 10 and Visual Studio 2022. All is 32bits including office but no matter what I always get hte bloody OLED12 service provider not registered issue. I also tried the previous solution but there's no way, it doesn't work. Also if I try to install the 64 bit version of AccessDatabaseEngine is raises an error due to the different bitness. What can I do? Thanks for your support.
Please sign in to rate this answer.
Amir Baymuratov 1 Reputation point

2022-06-04T10:15:28.393+00:00

I have the same problem and can't solve it

Pascal Muders 1 Reputation point

2022-07-01T13:51:40.317+00:00

I had some similar problems with acedao (class nor reg).

I found a way that worked for me. No access runtime needed.

// died not work
/* m_hr = CoCreateInstance(
__uuidof(DAO::DBEngine),
NULL,
CLSCTX_ALL,
IID_IDispatch,
(LPVOID*)&theApp.m_pEngine);
/
// worked
m_hr = CoCreateInstance(
__uuidof(DAO::DBEngine),
` nullptr,
CLSCTX_ALL,
__uuidof(DAO::_DBEngine),
reinterpret_cast<LPVOID>(&theApp.m_pEngine));

Mich 0 Reputation points

2024-04-19T17:46:53.06+00:00

I installed AccessRuntime_x86_en-us.exe and got it to work.
Sign in to comment
Mark Finn 6 Reputation points

2022-08-31T16:57:10.353+00:00

I have this problem every time I get a new laptop.

As has been said, you have to install the Microsoft library here and set the platform target appropriately, but setting that target is not as simple as you would expect. It is NOT sufficient to change the solution target (in the drop-down at the top of the Visual Studio window) because, for some reason, that does not always set the targets of the underlying projects to the same value. In particular, when the solution target is AnyCPU, the project target default is correct (AnyCPU), but when the solution target is x86, the project target inexplicably defaults to x64. You need to go into the properties of all projects which use the Microsoft library and make sure the project target is set to what you want.

Is there a reason for this strange behavior, or is it a bug? Who knows? Hopefully, though, this will help some of you out there. It is a very annoying problem that rarely comes up, so it's hard to remember the fix.
Please sign in to rate this answer.

1 person found this answer helpful.
Barns Le Tourneur 0 Reputation points

2023-07-10T15:33:48.4133333+00:00

I went into the Project properties and turned off the 'prefer 32 bit' under Build -> Platform Target.

It then worked - go figure?! @Mark Finn thanks for putting me on this trail.
Sign in to comment
REGIE CLARIN 6 Reputation points

2022-10-26T16:33:55.833+00:00

the microsotf.ACE.OCLEDB 12.0 provider is not register on the local machine
Please sign in to rate this answer.

1 person found this answer helpful.
pe 0 Reputation points

2023-02-25T08:01:51.23+00:00

Install " AccessDatabaseEngine 2007 "

link: https://1drv.ms/u/s!AtFBlKEguYWKsH7yVVAbIOt1rebV?e=cedma5
Sign in to comment