Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine

Question

I created a windows application developed in .NET 3.5 in a 32 bit Windows 2008 server. When deployed the application in a 64 bit server it shows the error "Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine ".

So as a solution to this issue, i have changed the build property of the project to X86, so that it will build in 32 bit mode, and rebuild the project in the 32bit machine. But, the same project uses other DB drivers (DB2, SQL etc.) to connect to other databases. So when i deployed my app again in the 64 bit OS, it throws the exception " Attempted to load a 64-bit assembly on a 32-bit platform. "

I am using the Microsoft.Jet.OLEDB.4.0 driver to read and write to the Excel (.xls)

Solution 1

I found a solution for this problem. The issue I described in my question occured basically due to the incompatibility of the Microsoft.Jet.OLEDB.4.0 driver in 64 bit OS.

So if we are using Microsoft.Jet.OLEDB.4.0 driver in a 64 bit server, we have to force our application to build in in 32 bit mode (This is the answer I found when I did an extensive search for this known issue) and that causes other part of my code to break.

Fortunately, now Microsoft has released a 64 bit compatible 2010 Office System Driver which can be used as replacement for the traditional Microsoft.Jet.OLEDB.4.0 driver. It works both in 32 bit as well as 64 bit servers. I have used it for Excel file manipulation and it worked fine for me in both the environments. But this driver is in BETA.

You can download this driver from Microsoft Access Database Engine 2010 Redistributable

Solution 2

If the issue persist in ASP.NET,All I had to do was change the "Enable 32-bit Applications" setting to True, in the Advanced Settings for the Application Pool.

Solution 3

I have the same problem

Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine

I applied the answer by neo but it did not work until I change the provider to “Provider=Microsoft.ACE.OLEDB.12.0;” in connection string.

Hope this will help if some one face the same issue.

Solution 4

I know it's quite old questions and many persons has answered. but I am summarizing the things for understanding:

If the file extension is xls and OS is 32 bit then only you can use "Microsoft.Jet.OLEDB.4.0". Microsoft has not released 64 bit version of this driver.

If file extension is xlsx or OS is 64 bit then you must have to use "Microsoft.ACE.OLEDB.12.0". The application compiled in 32/64 bit mode does not impact the selection of driver.

Always install the 64 bit driver of Microsoft.ACE.OLEDB.12.0 on OS 64 bit. If you have already installed Office 32 bit then you need to run driver from cmd with /passive argument. This hack works till Office 2013 only, Microsoft stopped this workaround from Office 2016 for Microsoft.ACE.OLEDB.16.0 drivers.

AccessDatabaseEngine_x64.exe /passive

Download drivers Microsoft.ACE.OLEDB.12.0

private void ProcessFile(string path)
{
    string connString = string.Empty;

    if (Path.GetExtension(path).ToLower().Trim() == ".xls" && Environment.Is64BitOperatingSystem == false)
        connString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" + path + ";Extended Properties=\"Excel 8.0;HDR=Yes;IMEX=2\"";
    else
        connString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=" + path + ";Extended Properties=\"Excel 12.0;HDR=Yes;IMEX=2\"";
}

If Application is compiled with AnyCPU flag, it will look for 64 bit Access drivers on 64 bit OS and 32 bit access drivers on 32 bit OS.

Solution 5

If your application runs on localIIS, You can solve this problem by enabling 32-bit applications in AppPool's Advanced Settings

View more solutions

Comments

[neo]

Anthony, How i can make only some part of a project to run in 32bit mode? All these DB connections, including Excel, will come under one project. Also i got the error in x86, when i try to run it in the 64 bit OS. I think this is because the DB2 driver installed in the 64bit OS is a 64bit version and when it is refferenced from the application, which is configured to run in 32 bit mode, causes the error.

[AnthonyWJones]

If splitting up the project into multipe exes is more hassle than its worth the you are left with only compiling to 32bit. As to the DB2 issue you would to look for some DB2 experts on this perhaps another DB2 specific question. Typically things like SQL Server will install both 32 bit and 64 bit providers on a 64 bit machine.

[neo]

Thanks Anthony for your comments. From doing a lot of search on this issue and from your comments, what i understood is, i have to create the part of the project which process the excel sheet as a separate project and make it compile in 32 bit version.

[David-W-Fenton]

Just so people know, A2010 will have 64-bit Jet.

[neo]

Thanks David, 2010 do have a 64 bit driver

[Mark]

Also pay special attention to the instructions on that link :)

[s.k.paul]

I had the same issue. I changed the application configuration to x86, then it worked!

[Spikolynn]

also i had to change connection string from using Microsoft.Jet.OLEDB.4.0 to Microsoft.ACE.OLEDB.12.0

[Masood Khaari]

Yes, although a 64-bit compatible Access Database Engine is available, it requires that no 32-bit version of MS Office products be already installed on the system (e.g. 32-bit MS Word) which is a big issue. The workaround is that you use 32-bit version of Access Database Engine 2010 and force your .NET application to run in 32-bit mode (e.g. by selecting x86 platform in Configuration Manager). And the proper solution is to replace MS Access with a better alternative.

[Farhan Hafeez]

I was using 64-bit ODBC and this change started to give me database error. I corrected it though. In case someone encounter this too, you will have to install 32-bit ODBC drivers and then create your DSN in that.

[Roman Starkov]

This is it! For a 64-bit server, install the redistributable linked by neo (the 64-bit variant, obviously), and then change the provider as specified in this answer, then it'll work.

[Roman Starkov]

It is quite possible to do this entirely in 64-bit code now. Install the redistributable linked in neo's answer, then use the Provider string suggested in Iqbal's answer. Then upvote both of those answers. That's it!

[Chris Pickford]

This fixed the issue for me on Windows Server 2008 R2 after having installed the 32bit Access DB Engine Redist.

[Iqbal]

You are right romkyns. I already said I applied neo solution, then changes the provider. But thanks your comment makes it more clear. Thanks a lot romkyns

[wtjones]

The downside is that the pool will run in 32-bit mode. We will instead switch to ACE to avoid this.

[AVEbrahimi]

replaced Microsoft.Jet.OLEDB.4.0 with Microsoft.ACE.OLEDB.12.0; in app.config and everything worked.

[philx_x]

noob question: can i distribute this Driver like "within my application" or does every user who wants to use my application have to install it manually?

[philx_x]

worked for me with Windows Forms aswell. no ASP.NET code at all

[Brain2000]

This forces your app to run in 32 bit mode. You need this setting off if you want to be able to avoid the 4GB barrier.

[NoChance]

Thanks for your answer, however, I am using VS2015 on Windows 10 and using X64. When I changed the project configuration from AnyCPU to X86, the problem went away. I did not have to install any additional drivers.

[Romil Kumar Jain]

@NoChance I think you have already installed Office 64 bit on your machine and it already contains Microsoft.ACE.OLEDB.12.0 drivers.

[NoChance]

Thx for your reply, I have office 2007 only.

[David A. Gray]

The answer to that question is provided by the last word in the article title, "Microsoft Access Database Engine 2010 Redistributable". By definition, a redistributable component may be distributed with your application, so long as you add significant value.

[SHEKHAR SHETE]

how to change this configuration? I have created website type project

[simaglei]

x86 made problems in my otherwise 64-bit environment. So I switched to Mixed Platforms, that did the trick. Thanks for the help!

[Terrance Jackson]

How do I include the driver in my application so no installation on user machine is necessary?

[andriy]

I found that this worked, while restricting the app to 32-bit made no difference whatsoever.

[César León]

In my case: "Microsoft.ACE.OLEDB.12.0 not registered", :(

[gamal]

THIS WORKS..... you have to install 64 bit version and change connection string to as this Answer. I tried so many ways, this is the only solution I found. (changing build version did not effect). Thank you...