IIS 7 HttpHandler and HTTP Error 500 21

Question

On IIS 7  I m trying to 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     lt system webServer gt   lt handlers gt       lt add name  MyHandler  path    myExtension  verb     type  Company App UI Controls MyHandler  Company App UI  resourceType  Unspecified    gt   lt  handlers gt   lt  system webServer gt     When I invoke this handler  I get this error   HTTP Error 500 21 - Internal Server Error Handler  MyHandler  has a bad module  ManagedPipelineHandler  in its module list   I 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

User · Answer

I had the same problem and just solved it. I had posted my own question on stackoverflow:

Can't PUT to my IHttpHandler, GET works fine

The solution was to 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 to go to your handler, you need to remove the WebDAV module and set this attribute to true.

<modules runManagedModulesForWebDavRequests="true">
...
</modules>

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.

User · Answer

Luckily  it   s very easy to resolve  Run the follow command from an elevated command prompt    windir  Microsoft NET Framework64 v4 0 30319 aspnet regiis exe -i   If you   re on a 32-bit machine  you may have to use the following    windir  Microsoft NET Framework v4 0 30319 aspnet regiis exe -i

User · Answer

One solution that I ve found is that you should have to change the  Net Framework back to v2 0 by Right Clicking on the site that you have manager under the Application Pools from the Advance Settings

User · Answer

On windows server 2016 i have used   dism  online  enable-feature  featurename IIS-ASPNET45  all  Also can be done via Powershell   Install-WindowsFeature  NET-Framework-45-Features

User · Answer

I had the same problem and was solved by running the following in run   windir  Microsoft NET Framework64 v4 0 30319 aspnet regiis exe -i

User · Answer

This situation happens because you haven t installed start service of ASP net   Use below command in windows 7 8 10    windir  Microsoft NET Framework v4 0 30319 aspnet regiis exe -i

User · Answer

It s not possible to configure an IIS managed handler to run in classic mode  You should be running IIS in integrated mode if you want to do that   You can learn more about modules  handlers and IIS modes in the following blog post   IIS 7 0  ASP NET  pipelines  modules  handlers  and preconditions     For handlers  if you set preCondition  integratedMode  in the    mapping  the handler will only run in integrated mode   On   the other hand  if you set 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

[asp.net] IIS 7, HttpHandler and HTTP Error 500.21

Examples related to asp.net

Examples related to iis

Examples related to iis-7

Examples related to httphandler

Examples related to ihttphandler