After configuring IIS under 64-bit Windows 2003, run the ASP page. If there is code to connect to the access database, an error warning will appear. Copy the code as follows:
ADODB.Connection error '800a0e7a'
Provider not found. The program may not be installed correctly.
/Connect to website 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 is only 32-bit, not 64-bit, so it cannot be loaded by IIS.
Solution: Let IIS run in 32-bit mode so that the 32-bit jet engine can be called
Solution: Enter in the command line window
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 loaded other 64-bit modules before the change, this module will no longer be loaded after the change. If you want to continue to use the functions of this module, you can only find the 32-bit version of this module and load it.
If you want IIS to run in 64-bit mode again, you can enter
cscript C:/inetpub/adminscripts/adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0