- Windows NT 4.0
- Windows 2000
- Windows XP (x86)
- Windows Server 2003 (x86)
- Windows Server 2008 (x86)
- Windows 7 (x86)
- Windows Server 2003 (x64)
- Windows Vista (x64)
- Windows 7 (x64)
- Windows Server 2008 (x64)
- Windows Server 2008 R2 (x64)
- Windows Server 2012 (x64)
When you attempt to connect to a Microsoft Access database using the ODBC provider Microsoft.Jet.OLEDB.4.0 you receive the error message:
For x64 Systems:
The Microsoft.Jet.OLEDB.4.0 is only available as a 32-bit (x86) module. In order to use it via IIS you must change the web site to run in a 32-bit application pool.
Under IIS 7.0, 7.5 or 8.0:
- Assuming that you will not want to use ASP .net, in the IIS console in the Application Pools section, create a no managed code, integrated application pool. If you do want to maintain access to ASP .net, select the framework version you require.
- Once created, in its advanced settings set “Enable 32-bit Applications” to true
- In the Basic Settings… for the web site entry you are experiencing the error on, change the Application Pool to the newly created 32-bit pool.
- Restart the web site
In most cases where the system is running under an x64 architecture, this should fix the problem.
For x86 and x64 Systems:
We had a server down for an entire day because of this one. It was either an attempt to fix a security database fault, or an update from Microsoft Update delivered in the April 2008 patch cycle, but after the reboot for the patches, none of the JET (Access) databases on the particular server, in any IIS web would operate.
I will simply cut to the fix for you in the beginning, to expedite your likely finding of a resolution to this problem. Something had caused the service provider for the Microsoft.Jet.OLEDB.4.0 provider to become unregistered. To fix the problem issue the following command from a Command Prompt or Run:
You shouldn’t need to reboot to solve the problem, it didn’t in my case. However, if nothing happens do restart before progressing to the next step.
Additional Steps: Step 1
Reregister the components from MDAC, JET and ADO in their entirety. Simply copy the below into a BAT file and run it.
Additional Steps: Step 2
Reinstall MDAC 2.8 SP1 (Windows XP SP1 or below only). You will need to perform some registry modifications before you can reinstall MDAC as it is a protected system module.
- Open Regedit
- Navigate to:
- Look through each class ID for the following friendly name values. Delete the Class ID containing the matching friendly names:
Microsoft MDAC Response Files
Microsoft MDAC Setup Files
Microsoft SQL Server ODBC Drivers
Microsoft SQL Server Net Libs
Microsoft SQL Server OLEDB Provider
WebData Setup Exception Package
Mdac 2.8 Exception Package
- Download and reinstall MDAC 2.8 SP1 from Microsoft which should reinstall in full.