Home/ Questions/Q 519047
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T08:00:01+00:00

I created a windows application developed in .NET 3.5 in a 32 bit Windows

  • 0

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)

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    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.

    As the 2010 link is no longer available, you can currently download this driver from Microsoft Access Database Engine 2016 Redistributable

    • 0