Today, we changed the system to a Windows 64-bit system. Previously, 32-bit normal-running websites were deployed in 64-Bit mode and cannot be accessed. The system always reports a 404.17 or 404.3 error.
According to the error message, the mime ing is not configured. The solution in the help manual on the Microsoft official website is (the original HTTP Error 404.17 ):
Add an application to the Web. config fileProgramConfiguration processed:
<System. webserver>
<Handlers>
<! -- Configure mime ing -->
<Add name = "urlre" Path = "*" verb = "*" modules = "isapimodule" scriptprocessor ="C: \ windows \ Microsoft. NET \ framework64 \ v4.0.30319 \ aspnet_isapi.dll"
Resourcetype = "unspecified" requireaccess = "NONE"
Precondition ="Classicmode, runtimeversionv4.0, bitness64"/>
</Handlers>
</System. webserver>
Select the corresponding configuration based on different operating systems (My. NET Framework version is 4.0 ).
ASP. NET 2.0 Classic Mode 32-bit handler (Windows 32-bit operating system configuration)
<Add name = "PageHandlerFactory-ISAPI-2.0" Path = "*. aspx "verb =" Get, Head, post, debug "modules =" isapimodule "scriptprocessor =" % WinDir % \ Microsoft. net \ framework \ v4.0.30319 \ aspnet_isapi.dll "precondition =" classicmode, runtimeversionv4.0, bitness32 "responsebufferlimit =" 0 "/>
ASP. NET 2.0 Classic mode 64-bit Handler(Windows 64-bit operating system configuration)
<Add name = "PageHandlerFactory-ISAPI-2.0-64" Path = "*. aspx "verb =" Get, Head, post, debug "modules =" isapimodule "scriptprocessor =" % WinDir % \ Microsoft. net \ framework64 \V4.0.30319\ Aspnet_isapi.dll "precondition =" classicmode,Runtimeversionv4.0,Bitness64"Responsebufferlimit =" 0 "/>
In this way, add the ing configuration and the program runs normally.