HTTP Error 500.23 – Internal Server Error
ASP.NET Settings not applicable in integrated managed pipe mode were detected.
The most likely reason:
- This application defines the configuration in the System.web /httpHandlers section.
\
Possible operations:
- Will configure the migration to the system. The webServer/handlers section. You can also do this manually, or by using AppCmd on the command line. For example, run AppCmd Migrate config “Default Web Site/” from the IIS Express installation directory. Migrating the application using AppCmd will enable it to work in integrated mode and continue to work in classic mode and on previous versions of IIS.
- If you are sure that you can ignore this error, you can through the system. The webServer/validation @ validateIntegratedModeConfiguration set to false to disable it.
- You can also switch your application to the Classical-mode application pool. For example, run appcmd set app “Default Web Site/” /applicationPool:”Clr4ClassicAppPool” from the IIS Express installation directory. Do this only if the application cannot be migrated.
\
Detailed Error Information:
| Module | ConfigurationValidationModule |
|---|---|
| Notification | BeginRequest |
| Handler | StaticFile |
| Error Code | 0x80070032 |
| Requested URL | http://localhost:57758/ |
|---|---|
| Physical Path | |
| Logon Method | Has not yet been determined |
| Logon User | Has not yet been determined |
| Request tracing directory | D:\Documents\IISExpress\TraceLogFiles\HN3D.NET |
\
\
\
\
\
\
\
More Information:
Integrated mode is the preferred mode for running ASP.NET applications on IIS 7.0 and later.
View more information »
\
The error is shown below:
\
VS solutions:
This error is due to a problem with the managed pipe pattern used by the WEB project; just change the integration to classic. \
Select the WEB project and press F4 to enter the project properties, as shown below :\
\
IIS solution:
Httphandler = httphandler = httphandler = httphandler = httphandler = httphandler But it appears when browsing:
HTTP Error 500.23 – Internal Server Error
ASP.NET Settings not applicable in integrated managed pipe mode were detected.
Many modification methods on the Internet are to modify the integrated hosting mode to the classic mode.
In fact, another way to do this is to add a new handler map to IIS
Perform a “migration” of the site.
May refer to the incorrect source:
Use commands directly: in CMD.
%SystemRoot%\system32\inetsrv\appcmd migrate config “Default Web Site/”
Note: Default Web Site represents the name of your current Web Site named in IIS.
As shown in the figure:
After entering the above command in CMD. Refreshing the page usually eliminates this error. You can also use inherited Httphandler normally.
———————————-
Then if I don’t want to use configuration for this site use my custom processing mapping.
Or I want to transfer processing back to the ASP.NET processing module in IIS.
You can open IIS 7.0 in the administrative tools —–>
Then click on your site display name — to find the handler map on the right. (Click where to register there)
When I click in,
You can view the mapping you just added and delete or modify its properties.
IIS7 reported 500.23 error resolution
Pizibaidu.blog.51cto.com/1361909/179…
\
www.jb51.net/article/877…
\
\