Gsx analyzer: http 500

On IIS 7, I"m trying to lớn use custom HttpHandler for my ASP.NET web application. I use pipeline mode "classic", .NET version is 4.0.30319, my web.config configuration for the handler is:

When I invoke this handler, I get this error:

HTTP Error 500.21 - Internal hệ thống ErrorHandler "MyHandler" has a bad module "ManagedPipelineHandler" in its module listI did a google search, the most of people fix this issue by re-registering ASP.NET by aspnet_regiis.exe /i command, but this is not working for me (the command finishes, I restart the IIS, but same error). I tried it on two different servers, but got the same result.

What else should I try? Thank you


Highest score (default) Trending (recent votes count more) Date modified (newest first) Date created (oldest first)
It"s not possible lớn configure an IIS managed handler to run in classic mode. You should be running IIS in integrated mode if you want to do that.

Bạn đang xem: Gsx analyzer: http 500

You can learn more about modules, handlers and IIS modes in the following blog post:

IIS 7.0, ASP.NET, pipelines, modules, handlers, & preconditions

For handlers, if you mix preCondition="integratedMode" in the mapping, the handler will only run in integrated mode. On the other hand, if you mix preCondition="classicMode" the handler will only run in classic mode. And if you omit both of these, the handler can run in both modes, although this is not possible for a managed handler.


Luckily, it’s very easy lớn resolve. Run the follow command from an elevated command prompt:

%windir%Microsoft.NETFramework64v4.0.30319aspnet_regiis.exe -iIf you’re on a 32-bit machine, you may have to use the following:

%windir%Microsoft.NETFrameworkv4.0.30319aspnet_regiis.exe -i



I had the same problem and was solved by running the following in run

%windir%Microsoft.NETFramework64v4.0.30319aspnet_regiis.exe -i


I had the same problem & just solved it. I had posted my own question on

Can't PUT to my IHttpHandler, GET works fine

The solution was to lớn set runManagedModulesForWebDavRequests to true in the modules element. My guess is that once you install WebDAV then all PUT requests are associated with it. If you need the PUT khổng lồ go to your handler, you need khổng lồ remove the WebDAV module & set this attribute khổng lồ true.

...So if you"re running into the problem when you use the PUT verb and you have installed WebDAV then hopefully this solution will fix your problem.

On windows server năm 2016 i have used:

dism /online /enable-feature /featurename:IIS-ASPNET45 /all

Also can be done via Powershell:

Install-WindowsFeature .NET-Framework-45-Features

This situation happens because you haven"t installed/start service of

Xem thêm: Sinh Ngày 28/12 Là Cung Gì ? Tìm Hiểu Đặc Điểm Ma Kết 28/12

Use below command in windows 7,8,10.

%windir%Microsoft.NETFrameworkv4.0.30319aspnet_regiis.exe -i
One solution that I"ve found is that you should have lớn change the .Net Framework back lớn v2.0 by Right Clicking on the site that you have manager under the Application Pools from the Advance Settings.

Thanks for contributing an answer to lớn Stack Overflow!

Please be sure khổng lồ answer the question. Provide details và share your research!

But avoid

Asking for help, clarification, or responding to lớn other answers.Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

Post Your Answer Discard

By clicking “Post Your Answer”, you agree to lớn our terms of service, privacy policy & cookie policy

How khổng lồ fix: Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module danh sách
Site design / logo © 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA. Rev2023.1.14.43159

Your privacy

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device & disclose information in accordance with our Cookie Policy.

hotlive |