This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 70%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEC%3C/text%3E%3C/svg%3E)
Connection to ACCESS database fails with exception:
The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 59%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
Thanks for reaching here! Could you please elaborate your issue in detail and Azure services you are using.
How to fix The microsoft.ACE.OLEDB.12.0 provider
You fix it by installing the ACE = "Access Database Runtime" dataprovider, select the right version from below:
https://www.microsoft.com/en-us/download/details.aspx?id=10910
https://www.microsoft.com/en-us/download/details.aspx?id=39358
https://www.microsoft.com/en-us/download/details.aspx?id=54920
After developing an ASP.NET VB web application using ACCESS database on Visual Studio 2022, successfully deployed to an Azure App Service. The app was functioning, but failed with exception when connecting to the ACCESS database.
Exception:
The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine
Since the application is hosted at azure app service, unable to download the required modules and register. Using different options of deploying from Visual Studio 2022 were of no help either.
As to Olaf Helper's advice, I downloaded AccessRuntim.exe (32 bit) and installed on my PC, rebuilt my app on Visual Studio 2022 and deployed to Azure web service, but it still fails the connection to ACCESS database at Azure.
After reading some articles posted, I found that ACCESS database run-time DLLS such as Microsoft.ACE.Oledb.12.0.dll and ACEOLEDB.DLL were not deployed (from Visual Studio 2022) to the application folder at Azure. I was wondering if this may be the cause of ACCESS database connection failure...
Found oledb32.dll in the following azure active directories:
d:\Program Files\Common Files\System\Ole DB\oledb32.dll
d:\Program Files\Common Files\System\Ole DB\oledb32r.dll
d:\Program Files\Common Files (x86)\System\Ole DB\oledb32.dll
d:\Program Files\Common Files (x86)\System\Ole DB\oledb32r.dll
But command "regsvr32 oledb32.dll" fails with "Access is denied" even the option for "user can register application" is turned on.
Besides, there are no ACEOLEDB.DLL and Microsoft.ACE.Oledb.12.0.dll found on the Azure directories.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 47%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVM%3C/text%3E%3C/svg%3E)
For anyone developing in Visual Studio the answer is to uncheck Prefer 32-bit in the project properties compile page.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 51%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDG%3C/text%3E%3C/svg%3E)
Thank you, out of all those long complicated solutions your very simple fix worked.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 12%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECC%3C/text%3E%3C/svg%3E)
Thank you. I knew the issue was because I built my project on a machine with 32 bit and I was trying to run the compiled exe on a machine with 64 bit. However, I did not know there was such a simple fix for this issue.
Problem
ACCESS database connection failure on an app in Azure Web Service:
The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine
The 'Microsoft.Jet.Ole8db.4.0' provider is not registered on the local machine.
Background
Microsoft recognizes that the error is by design as we do not install the Microsoft.Ace.we.12.0' driver. The Microsoft.Ace drivers are not supported in server side environments and as of now there is no plans to add these to the Azure Web Sites.
My working solution
The solution is complex, but it is working at least.
Step 1) Separate connection strings for the 64-bit source (on PC) and 32-bit target (Azure)
Connection String for 64-bit environment:
"Provider=Microsoft.ACE.OLEDB.12.0;" & "Data Source=" & sMdb & ";" & "Jet OLEDB:Database Password=" & sPass & ";" & "Persist Security Info=True;"
Connection String for 32-bit target environment:
"Provider=Microsoft.Jet.Ole8db.4.0;" & "Data Source=" & sMdb & ";" & "Jet OLEDB:Database Password=" & sPass & ";" & "Persist Security Info=True;"
Step 2) Adjust Registry Editor
In the search box on the taskbar, type “regedit” to open Registry Editor and adjust
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Fusion
Add:
DWORD ForceLog set value to 1
DWORD LogFailures set value to 1
DWORD LogResourceBinds set value to 1
DWORD EnableLog set value to 1
String LogPath set value to folder for logs (e.g. C:\FusionLog)
(reference: https://stackoverflow.com/questions/255669/how-to-enable-assembly-bind-failure-logging-fusion-in-net)
Step 3) Switch settings when deploying to Azure
Change Project / Property / Compile / Target CPU to “x86”
Change Platform to "x86"
Change Enable 320Bit Applications to “True”
Step 4) Switch settings back to 64-bit development PC environment
Change Project / Property / Compile / Target CPU to “Any CPU”
Change Platform to "Any CPU"
Change Enable 320Bit Applications to “False”
My working solution failed again after reinstalling Office 365 and Azure Virtual Machine.
I am not sure if ACCESS would be a reliable data source in the Azure environment.
@Ed Choi Could you please reach out to us by sending an email with subject line “Attn:Sneha |thread title” to AzCommunity[at]microsoft[dot]com referencing this thread, would be working closely on this.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 54%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPC%3C/text%3E%3C/svg%3E)
I had all sorts of difficulty trying to connect local (not Azure) MS Access databases to a DataGridView with the above error until i read Step 4) above and reconfigured my compiler to x64 - then it worked.
Apologies for facing issue on this! If you are receiving the following error on your Azure Web Site
'Microsoft.Ace.OLEDB.12.0' provider is not registered on the local machine
The error is by design as we do not install the Microsoft.Ace.we.12.0' driver.
The Microsoft.Ace drivers are not supported in server side environments and as of now there is no plans to add these to the Azure Web Sites.
Workaround-
This leaves the option of using the Jet Drivers which are installed, however these are only available in 32 bit versions so you will have to configure your site to run in 32 bit versions. The Microsoft OLE DB Provider for Jet and the Microsoft Access ODBC driver are available in 32-bit versions only: http://support.microsoft.com/kb/957570/en-us
This is also discussed here: Data Access Technologies Road Map http://msdn.microsoft.com/en-us/library/ms810810.aspx#bkmk_DepMDAC_WDACComps
Also, you could use Windows Containers to install these drivers.
Quickstart: Run a custom container on App Service - Azure App Service | Microsoft Learn
Further if you wish you may share your feedback on Azure Web App Uservoice -
All of the feedback, you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure. Additionally, users with a similar request can up-vote you post and add their comments.
Please let us know, if you have further query or issue remains.
As you indicated, I ran “accessdatabaseengine.exe” (from 2016)
https://www.microsoft.com/en-us/download/details.aspx?id=54920.
But it failed with error (attached)32-bit install error.jpg:
As the error message indicated, I removed 64-bit Office products and re-ran “accessdatabaseengine.exe”. But I got the same error message.
2)
I installed “accessRuntime.exe” (from 2010)
https://www.microsoft.com/en-us/download/details.aspx?id=10910, adjusted the connection string, rebuilt, and re-published.
But it failed as below:
ConnectionString:
"Provider=Microsoft.Jet.Ole8db.4.0;" & "Data Source=" & sMdb & ";" & "Jet OLEDB:Database Password=" & sPass & ";" & "Persist Security Info=True;"
=> exception
The 'Microsoft.Jet.Ole8db.4.0' provider is not registered on the local machine
3)
I even tried with the connection string for ODBC, but it still fails with the exception:
An OLE DB Provider was not specified in the ConnectionString. An example would be, 'Provider=SQLOLEDB;'.
Your help is much appreciated.
As per some articles posted, “AccessDatabaseEngine.exe” from Microsoft Access Database Engine 2010 Redistributable https://www.microsoft.com/en-ca/download/details.aspx?id=13255 was successfully installed, but the ACCESS database connection still fails with the same error:
ConnectionString = "Provider=Microsoft.Jet.Ole8db.4.0;" & "Data Source=" & sMdb & ";" & "Jet OLEDB:Database Password=" & sPass & ";" & "Persist Security Info=True;"
=> exception
The 'Microsoft.Jet.Ole8db.4.0' provider is not registered on the local machine
Note: Target CPU was set to 86x when deploying (screenshot attached)
Found that DLLs of Microsoft Jet OLE DB 4.0 reside on C:\Windows\System32. Tried to register the DLLs by executing command such as “regsvr32 Msjetoledb40.dll”, but failed with error “Access was denied” even I was using the admin account with the right permissions. (screen-print attached)
The Wayback Machine and Internet Archive FOR THE WIN!
This was sourced from chocolatey, but is available for direct download from the following links:
Chocolately package for reference: https://community.chocolatey.org/packages/made2010#files
Cheers!