“The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine”…DNN

6
votes

I'm trying to get a new DotNetNuke site up and running on our 64-bit server, and I'm encountering the following error message:

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

I know from experience that you run into this when you target a 64-bit assembly on a 64-bit machine (there is no 64 bit OLE-DB provider currently). In that case, I simply target the x86 in Visual Studio and everything works fine.

But in this case, the site uses dynamic compilation, so there's no simple place to specify that I need to target x86. Any thoughts?

TIA.

3
asp.net64-bitoledbdotnetnuke
I know this is probably a dumb question, but is the correct version of MDAC installed on the server? – David
Yeah, not a dumb question. I've got a bunch of other sites running here, but they don't use dynamic compilation, and I don't think they use Jet either. In any case, the DLL's are actually present on the box, and of the version consistent with 2003 SP2. – Chris B. Behrens
Why is it trying to use Jet/OLEDB at all? It should be going to SQL Server directly. What are you using for your connection string? – EfficionDave

3 Answers

8
votes

You could change your app pool that you're running that site under to run as a 32 bit application. In the IIS7 manager, its under "Advanced Settings" of your app pool, and then set "Enable 32-bit Applications" to true.

You could also do this with AppCmd from a console with the following:

appcmd apppool set /apppool.name:MyNukeSite /enable32BitAppOnWin64:true

In IIS6 - you could try something like this (2 lines here, run aspnet_regiis when finished changing the metabase value)...

cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1
aspnet_regiis.exe -i

See the following for more info:

3
votes

HI, Now the Microsoft has released the 2010 Office System Driver Beta: Data Connectivity Components which is supported both in 32 bit as well as 64 bit OS. So using this driver instead of the traditional Microsoft.Jet.OLEDB.4.0 driver will give us a 64 bit application running on a 64 bit server (that is what we really need).

Though this is in beta, it worked fine for me.

You can download this driver from 2010 Office System Driver Beta: Data Connectivity Components

Thnks

1
votes

You shouldn't try to target your application to 32-bit in which case you are losing the advantages of using 64-bit system. As aaa has pointed out, you can use the latest Access Database Engine 2010 to address this issue. Please refer to my blog post for complete solution.

Hope it helps.