views:

2835

answers:

2

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.

+5  A: 

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:

Scott Ivey
Sounds like we're definitely on the right track, but this is IIS 6.0. Is that something I can edit directly in the metabase?
Chris B. Behrens
+1 for SO helping solve my obscure problem once again. Thanks!
Mercurybullet
+3  A: 

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

rookie