You may encounter the following two errors when configuring the IIS server for ASP or ASP. NET. Configuration of IIS7.0 is more complex than that of IIS5.1 on Windows 7. It is more challenging to configure an IIS server environment where ASP and ASP. NET coexist. The following are my two summaries:
1. error message: ADODB. Connection error '800a0e7a '. No provider is found. Solution: the original website was generated in a 32-bit windows environment, causing an error in win764 bits (the IIS7 application pool does not enable the 32-bit program by default, that is to say, if you are using a 64-bit operating system without a 64-bit Jet 4.0 driver, you need to enable the 32-bit program in IIS7 ). Click "application pool" on the left of IIS manager, and select "True" on "enable 32-bit application ".
2. Error message: the absolute physical path "C: \ inetpub \ custerr" is not allowed in the system. webServer/httpErrors section of the HTTP Error 500.19-Internal Server Error web. config file ". Use a relative path. Solution: In the process of configuring ASP, the 500. html parameter in the error page is configured. asp. to delete a cofig file, open the folder where your ASP Website is located and delete it. If no, it will be C: \ inetpub \ wwwroot \ web. delete the code from httperrors to/httperrors in cofig, including % SystemDrive % \ inetpub \ custerr "path =" 500. asp "responseMode =" File "/>.