There are times when the coexistence of 64 and 32 bit code on the same machine can cause all sorts of seemingly strange issues. One of them just occurred to me while trying to run the ASPx demos from Developer Express, my main provider of .Net components (the best supplier I’ve ever been able to find). I was getting the following error:

The ‘Microsoft.Jet.OLEDB.4.0’ provider is not registered on the local machine:

It may look otherwise, but this error is generally due to either of two thing:

you don’t have Office 2007/2010 Jet drivers installed

or you are running a 32 bit application in a default x64 environment.

The first issue is easy to solve, just download the Access 2010 Database Engine from Microsoft (works with Access 2007 databases as well).

Hi dude, you understand this stuff more than microsoft bill gate, they have no idea of user’s problems to support them. You certainly know what you are talking about, well done, keep the open source knowledge going!!!

I will definitely be posting a link to your solution on my site. This was driving me nuts. I use Access all the time, but had never had to run it on my own server. When I got the error message you refer to, I started browsing around expecting it to be obvious. Lots of false leads and dead ends. Your steps for Windows Server 2008 were the answer. Thank you!!

well, any day now, my application will be up and running thanks to your help

35. Krunal Rathod | January 28th, 2013 at 7:38 pm

Hi, Reading .xls and .xlsx file was working my local system fine. But same code was showing error on Testing server which is 64 bit. Error: (The ‘Microsoft.Jet.OLEDB.4.0’ provider is not registered on the local machine.)

about

This is a simple technical weblog where I dump thoughts and experiences from my computer-related world. It is mostly focused on software development but I also have wider interests and dabble in architecture, business and system administration.More About me…