ADODB. Connection error ' 800a0e7a '
Provider not found. The program may not be installed correctly.
/Connect to the site Content management database. ASP, line 2
Reason: IIS runs in 64-bit mode, it can only load 64-bit modules and cannot load 32-bit modules. The jet engine that accesses the Access database has only 32 bits and no 64 bits, so it cannot be loaded by IIS.
Workaround: Let IIS run in 32-bit mode so that it can invoke a 32-bit jet engine
Workaround: Enter in command line window
Copy Code code as follows:
cscript C:\inetpub\adminscripts\adsutil.vbs SET W3svc/apppools/enable32bitapponwin64 1
The negative effect of the above method: Because IIS is changed to run in 32-bit mode, it can only load 32-bit modules. If IIS loads the other 64-bit modules before it is changed, the module cannot be loaded after the change. If you want to continue using the functionality of this module, you can only look for the 32-bit version of this module and load it.
If you want IIS to run again in 64-bit mode, you can enter
Copy Code code as follows:
cscript C:\inetpub\adminscripts\adsutil.vbs SET W3svc/apppools/enable32bitapponwin64 0
Yesterday to help customers configure the Web site, the client server is the use of Windows 2003 64bit system, I have configured the IIS site after the test found that the program has been prompted to run overtime, because this program on the 32bit machine run no problem, suspect the problem out in the loop, so that the program in the cycle began The test works correctly, output record status Rs.bof display blank, suspected jet engine problem, the program error control statement removed after the program run error description is not found provider, open "data source (ODBC)", go to the "Driver" tab to see, found no jet engine. So from the Microsoft website downloaded mdac2.7 installation, after the installation found that the problem remains!
Search from the web found that 64-bit IIS could not be compatible with the 32 jet engine, and that IIS would have to be run as 32, just enter the command at the command line
cscript C:\inetpub\adminscripts\adsutil.vbs SET W3svc/apppools/enable32bitapponwin64 1
IIS then runs in 32-bit ways.
After running the command, the site will work properly.
In addition: The Internet also mentions that if the ASP.net module is run when IIS is running in 32 and must also load 32 asp.net extensions, IIS will not function properly because 64-bit IIS cannot load 32-bit asp.net modules, and 32-bit IIS will not be able to load 64-bit asp.net modules.
