Handler "ExtensionlessUrlHandler-Integrated-4.0" has a bad module "ManagedPipelineHandler" in its module list

Question

To be honest, I've tried to turn a dirty trick on IIS and just when I thought that I was going to get away with it, I realized my workaround doesn't work. Here's what I've tried to do:

1) I have ASP.NET application which has Preloader class that inherits IProcessHostPreloadClient and does all the heavy initialization in Preload method implementation (application is complex and it's a part of an enormous system, so it requires approximately 2 minutes to establish connections to all necessary services and pre-instantiate some Unity registrations).

2) I have a lot of work that needs to be done on application shutdown (unsubscribing, disconnecting, disposing,...), and I guess the best place to do it is in *Application_End* method located in Global.asax.

3) Everything works just fine when I have user activity (first request after the Application Pool that contains aforementioned web application is started will cause *Application_Start* to be called and afterwards *Application_End* is called on Application Pool stop or recycle), but problems occur when there is no user activity and application tries to restart itself after being active for 48 hours (configured requirement). Since there was no requests, application officially didn't get started. Ergo, it can't be gracefully stopped since *Application_End* won't be called.

4) Now comes the messy part... I've tried to make a GET request from code at the end of the Preload method, and it worked. But this solution seemed bad to me, even though it worked. So, I've tried a lot of things, and the last thing I tried was this:

SimpleWorkerRequest swr = new SimpleWorkerRequest(string.Empty, string.Empty, tw);
HttpRuntime.ProcessRequest(swr);

... and that has done it's purpose. *Application_Start* was called, (I've checked response, it was containing login page that was supposed to be displayed in initial request) and on Application Pool shutdown application ended gracefully by doing necessary work in *Application_End*.

BUT

After the application was started (preloaded and initiated) in this manner, this is what happened when I wanted to reach application via Web browser:

HTTP Error 500.21 - Internal Server Error Handler "ExtensionlessUrlHandler-Integrated-4.0" has a bad module "ManagedPipelineHandler" in its module list

I am unable to figure this out. Can anybody tell me why this happens and how to fix it?

If I don't figure this out, I will go back to first solution (sending GET request from code) but this problem will bug me since I don't even have an idea what's wrong.

Not a direct answer to your question, but for other users with similar problem and asuming you have an internet facing application: you could just use an external service like http://uptimerobot.com/ to touch your application every X amount of time. You keep your app in running state + you have the added benefits of the service (uptime, alerts, etc). — qbantek, Feb 18 '14 at 13:56
@qbantek Even though application I am working on is not internet facing, you gave me a good idea. I could use load balancer to do periodic touch by setting health status checking type to Simple HTTP GET. Thanks — Ivan Peric, Feb 24 '14 at 18:18

score 652 · Answer 1 · edited Apr 24 '13 at 19:29

652

Try to re-register ASP.NET with aspnet_regiis -i. It worked for me.

A likely path for .NET 4 (from elevated command prompt):

c:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i

http://forums.iis.net/p/1190643/2026401.aspx

edited Apr 24 '13 at 19:29

Michael Haren

97,268
39
159
200

answered Nov 07 '12 at 09:29

danijelk

6,721
2
13
11

Thank you for your answer. I have already tried that and it didn't work. :( – – Osama khodrog Dec 03 '13 at 12:54
8

Doesn't work for Windows Server 2012. Read Zach's post on this page. – Ivan Akcheurov Dec 23 '13 at 10:49
Thanks. Worked for me doing this on a virtual machine in Azure. What I would like to know though is why would I have to do this on a new install. Surely ASPNET registers itself when it installs right? My guess is it has something to do with the order of installation. – David Bridge Jan 05 '15 at 15:45
4

If you are using .NET 4.5.x or 4.6.x, don't be fooled by the answer mentioning 4.0 and thinking it doesn't apply to you. This problem can be related to the order of installation of .NET before IIS, as it was for me. Running the command (in my case the 64 bit version) fixed it even though my application is using .NET 4.5.2. – Coxy May 17 '16 at 02:51
windows 2008, fresh install AWS microserver required me to run this command..Just for those of us who thinks its not relevant to their system. – terary Apr 17 '19 at 23:10

score 177 · Answer 2 · edited Mar 05 '14 at 20:20

177

If you're running into this error with Windows 8/Windows Server 2012 and .Net 4.5 follow these instructions here: http://www.britishdeveloper.co.uk/2013/01/handler-extensionlessurlhandler.html

Go to "turn Windows features on or off" Then Internet Information Services Then World Wide Web Services Then Application Development Features And then enable ASP.NET 4.5

This worked for me (although the wizard and wording is a little different in Windows Server 2012, but you'll figure it out). With this being said, why this is necessary after installing everything through the Web Platform Installer including all of the dependencies is completely beyond me...

edited Mar 05 '14 at 20:20

Chris Pietschmann

28,196
35
116
161

answered Feb 26 '13 at 22:54

Zach

1,771
1
10
2

3

Configuring Windows Server is a PITA. Why isn't there a central package management system? – Kugel Mar 10 '14 at 02:00
if you installed iis with web platform, check for Virgo139's comment, it solved my problem easily – castors33 Mar 20 '14 at 19:21
This was the fix for me on Windows 10 Pro build 1607, cheers! – Apogee Dec 13 '17 at 13:47
This fixed it for me on WIndows 10 as well. Worth noting that the common command-line fix (aspnet_regiis.exe -i) is not allowed on Windows 10. – Nat Webb Jan 12 '18 at 19:57
1

Confirmed solution for windows 10 Pro. – Zoomzoom Oct 18 '19 at 13:18
This worked for me. I had to turn on 4.8. I'm guessing just needed to turn on whatever framework you're using. FYI - Other checkboxes were automatically checked when I checked my box. – athomas Dec 23 '20 at 14:16

Jonathan · Answer 3 · 2019-12-03T17:20:30.710

65

Despite following most of the advice on this page, I was still getting problems on Windows Server 2012. Installing .NET Extensibility 4.5 solved it for me:

Add Roles and Features > Server Roles > Web Server (IIS) > Web Server > Application Development > .NET Extensibility 4.5

edited Dec 03 '19 at 17:20

answered Jul 31 '13 at 11:43

Jonathan

10,693
16
74
110

2

Thanks for spelling it out, I was staring at Web Server -> Web Server -> Web Server pipe for far too long... :) – Gleno Jan 28 '14 at 21:26
2

Don't forget to check Roles and Features > Server Roles > Web Server (IIS) > Web Server > Application Development > ASP.NET 4.6 (or 4.5 depending on your setup) – Lionet Chen Nov 01 '18 at 03:09
1

Yep, then reboot IIS Service. Worked for me! Thanks. +1 – Rusty Nail Dec 07 '18 at 02:34

Bart Verkoeijen · Answer 4 · 2018-03-01T08:20:04.233

52

For Windows 10 / Windows Server 2016 use the following command:

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

The suggested answers with aspnet_regiis doesn't work on Windows 10 (Creators Update and later) or Windows Server 2016:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i
Microsoft (R) ASP.NET RegIIS version 4.0.30319.0
Administration utility to install and uninstall ASP.NET on the local machine.
Copyright (C) Microsoft Corporation. All rights reserved.
Start installing ASP.NET (4.0.30319.0).
This option is not supported on this version of the operating system. Administrators should instead install/uninstall ASP.NET 4.5 with IIS8 using the "Turn Windows Features On/Off" dialog, the Server Manager management tool, or the dism.exe command line tool. For more details please see http://go.microsoft.com/fwlink/?LinkID=216771.
Finished installing ASP.NET (4.0.30319.0).

Interestingly, the "Turn Windows Features On/Off" dialog didn't allow me to untick .NET nor ASP.NET 4.6, and only the above DISM command worked. Not sure whether the featurename is correct, but it worked for me.

edited Mar 01 '18 at 08:20

answered Jan 05 '17 at 05:57

Bart Verkoeijen

12,647
6
48
56

This fixed it for me, I was running Windows 10 pro with the creator update. Thanks! – Samuel Poirier May 05 '17 at 13:08
Legendary answer! I had to rebuild my web server, and hadn't updated the scripts in a few years, I've added this DISM command to my VM provisioning scripts, works like a charm. – Chris Schaller Aug 12 '18 at 23:52
dism /online /enable-feature /featurename:IIS-ASPNET45 /all Worked for me on Windows Server 2016 – Syed Nasir Abbas Jul 10 '19 at 19:23
Thanks to you, I still have a job! :) Worked. – Scott Oct 03 '19 at 12:17

score 42 · Answer 5 · edited Jan 31 '16 at 12:02

42

Run one of these commands :

For 32 Bit Windows OS:

c:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i

For 64 Bit Windows OS:

c:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -I

edited Jan 31 '16 at 12:02

Rahul

1,845
2
28
68

answered Jul 31 '14 at 15:40

user3896335

441
4
2

I noticed when doing this, the folder, "aspnet_client" gets added to the website under the Sites directory of IIS Connections – eaglei22 Jul 06 '17 at 21:25

score 26 · Answer 6 · edited May 23 '17 at 11:54

26

This https://stackoverflow.com/a/13266763/1277458 works perfectly. But if you have 64-bit operation system use Framework64 instead of Framework in path:

c:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i

edited May 23 '17 at 11:54

Community

1
1

answered Jun 23 '14 at 11:05

Neshta

2,277
2
24
37

1

FWIW, Server 2012 R2 says this option is not supported, and suggests using the Feature dialog to enable ASP.NET 4.5 – bvj Mar 26 '15 at 05:21
Yes, Zach's answer covers this. – Neshta Mar 26 '15 at 12:17

chue x · Accepted Answer · 2014-01-14T16:38:27.103

The problem

You are using SimpleWorkerRequest in a scenario that it wasn't designed for. You are using it inside of IIS. If you look at the prior MSDN link (emphasis is mine):

Provides a simple implementation of the HttpWorkerRequest abstract class that can be used to host ASP.NET applications outside an Internet Information Services (IIS) application. You can employ SimpleWorkerRequest directly or extend it.

Also, if you look at the MSDN documentation for the System.Web.Hosting namespace (SimpleWorkerRequest is in this namespace), you will also see something similar to the above (again, emphasis is mine):

The System.Web.Hosting namespace provides the functionality for hosting ASP.NET applications from managed applications outside Microsoft Internet Information Services (IIS).

The solution

I would recommend removing the call to SimpleWorkerRequest. Instead, you can use a Microsoft solution to make sure your web site automatically starts up after it recycles. What you need is the Microsoft Application Initialization Module for IIS 7.5. It is not complicated to configure, but you need to understand the exact options. This is why I would also recommend the Application Initialization UI for IIS 7.5. The UI is written by an MSDN blogger.

So what exactly does the Microsoft solution do? It does what you are trying to do - IIS sends a "get" request to your website after the application pool is started.

I was hopping to find a solution that can be implemented in code, but this is as close to a "good enough" as it gets so I'm awarding the bounty to it. But I guess the solution that @danijelk provided will be most useful for most people who come across this question for reason other than I specified. So this is a note for them to take a look at it. — Ivan Peric, Nov 30 '13 at 21:08

score 13 · Answer 8 · answered Jan 09 '16 at 21:35

13

In my case (Windows 10 + IIS 10) i had to open "Turn Windows Features On or Off" and then go to Internet Information Services > World Wide Web Services > Application Development Features > and check ASP.NET 4.6

answered Jan 09 '16 at 21:35

Xaris Fytrakis

477
6
16

1

Mine was IIS on Windows 2012 R2. Added the compatible ASP.NET in Server Manager > Manage > Add Roles and Features > Role-based or feature-based installation > (select your server) > Web Server (IIS) > Web Server > Application Development > ASP.NET 4.5. As @ArsmanAhmad said a good sanity check is to verify if your App Pool .NET CLR Version is set to v4.0. – GBU Dec 13 '16 at 11:13

score 6 · Answer 9 · answered Mar 10 '17 at 15:17

Making this its own post because this had me going for hours.

I saw maybe a dozen of similar posts here and elsewhere about this problema and the aspnet_regiis fix. They weren't working for me, and aspnet_regiis was acting odd, just listing options etc.

As user ryan-anderson above indicated, you cannot enter .exe

For those less comfy with things outside IIS on the server, here's what you do in simple steps.

Find aspnet_regiis in a folder similar to this path. c:\Windows\Microsoft.NET\Framework\v4.0.30319\
Right-click command prompt in the start menu or wherever and tell it to run as administrator. Using the windows "Run" feature just won't work, or didn't for me.
Go back to the aspnet_regiis executable. Click-drag it right into the command prompt or copy-paste the address into the command prompt.
Remove, if it's there, the .exe at the end. This is key. Add the -i (space minus eye) at the end. Enter.

If you did this correctly, you will see that it starts to install asp.net, and then tells you it succeeded.

Worked perfectly for me. Thank you. – Mike Jun 23 '17 at 18:18 — Mike, Jun 23 '17 at 18:18

score 6 · Answer 10 · edited Jul 24 '19 at 00:31

6

I solved this problem, adding in "Turn Windows features on or off" The option ASP.NET 4.7

edited Jul 24 '19 at 00:31

kamalpreet

2,384
1
23
47

answered Feb 22 '18 at 01:09

Edgar Chivichon

61
1
3

score 5 · Answer 11 · answered Oct 31 '16 at 12:25

Make sure that you have set your application-site version from v2.0 to v4.0 in IIS Manager:

Application Pools > Your Application > Advanced Settings > .NET Framework Version

After that, install your ASP.NET.

For 32-Bit OS (Windows):

C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i

For 64-Bit OS (Windows):

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i

Restart your application-site in IIS Manager and enjoy.

Yeah, I tried my best to make answer simplest. ;-) @yuyangJian — Arsman Ahmad, Nov 05 '18 at 09:47

score 4 · Answer 12 · answered Aug 19 '13 at 09:43

I know this is an oldie, but thought I might add some value. For those of us running Server Core outside of a domain (domain members can just run Server Manager remotely to add/remove features/roles), you have to resort to command lines.

Powershell users can type "Install-WindowsFeature Web-Asp-Net45"

That should be equivalent to using server manager.

score 4 · Answer 13 · edited Jun 20 '20 at 09:12

4

I was challenged by the same error message, with .net 4.7 installed.

The solution was to follow one earlier mentioned post to go with the "Turn Windows feature on or off", where the ".NET Framework 4.7 Advanced Services" --> "ASP.NET 4.7" already was checked.

Further down the list, there is the "Internet Information Services" and subnote "Application Development Features" --> "ASP.NET 4.7", that also needs to be checked.

When enabling this, allot of other features are enabled... I simply pressed the Ok button, and the issue was resolved. Screendump of the windows features dialog

edited Jun 20 '20 at 09:12

Community

1
1

answered Dec 14 '17 at 15:10

theodor.johannesen

176
1
4

I should add that this was a **windows 10 pro** edition – theodor.johannesen Dec 14 '17 at 15:11

score 2 · Answer 14 · answered Nov 20 '15 at 09:42

I'm working on Windows Server 2012. .NET Extensibility 4.5 feature is on. WebDAVModule removed. I was still getting 500.21 error on ASP.NET route '/docs'.

Changing 'skipManagedModules' to false fixed the problem.

<applicationInitialization doAppInitAfterRestart="true" skipManagedModules="false">
        <add initializationPage="/docs" />    
</applicationInitialization>

Thanks to https://groups.google.com/forum/#!topic/bonobo-git-server/GbdMXdDO4tI

score 1 · Answer 15 · answered Feb 15 '13 at 12:13

1

I had this problem and found that removing the following folder helped, even with the non-Express edition.Express:

C:\Users\<user>\Documents\IISExpress

answered Feb 15 '13 at 12:13

Thomas Bratt

40,822
34
113
133

score 1 · Answer 16 · answered Mar 30 '15 at 20:33

This error started happening to me out of nowhere last week, affecting the existing web sites on my machine. I had no luck with it trying any of the suggestions here. Eventually I removed WebDAV from IIS completely (Windows Features -> Internet Information Services -> World Wide Web Services -> Common HTTP Features -> WebDAV Publishing). I did an IIS reset after this for good measure, and my error was finally resolved.

I can only guess that a Windows update started the issue, but I can't be sure.

Just had the same issue. Installed some windows updates that switched around my IIS settings. Turning off WebDAV Publishing fixed it again. — ElliotSchmelliot, Apr 09 '15 at 00:20

score 1 · Answer 17 · answered Feb 19 '20 at 19:37

1

Installing .NET 4.7 worked for me. I only had 3.5 installed prior.

answered Feb 19 '20 at 19:37

Eric S.

21
1

score 0 · Answer 18 · answered May 21 '14 at 15:53

0

You could fix it by change the "ExtensionlessUrlHandler-Integrated-4.0" type in iis to System.Web.DefaultHttpHandler

answered May 21 '14 at 15:53

user3661608

1

score 0 · Answer 19 · answered Feb 18 '15 at 10:39

For me, removing WebDAV from my server caused the application to return a 503 Service Unavailable Error message when using PUT or DELETE, so I re-installed it back again. I also tried completely removing .NET Framework 4.5 and reinstalling it and also tried re-registering as suggested but to no avail.

I was able to fix this by disabling WebDAV for the individual application pool, this stopped the 'bad module' error when using PUT or DELETE.

Disable WebDAV for Individual App Pool:

Click the affected application pool
Find WebDAV Authoring Tools in the list
Click to open it
Click Disable WebDAV in the top right.

Ta daaaa!

I still left the remove items in my web.config file.

 <system.webServer>
    <modules>
      <remove name="WebDAVModule"/>
    </modules>
    <handlers>
      <remove name="WebDAV" />
    </handlers>
 <system.webServer>

This link is where I found the instructions but it's not very clear.

score 0 · Answer 20 · answered May 26 '15 at 14:54

This maybe not a usefull solution for OP but it concerns the same "error" message.

We are hosting PHP pages on IIS8.5 with .NET 4.5 installed correctly.

We make use of the preload functionality to make sure our application is always responsive across the board.

After a while we started getting this error at random.

In the web.config : I put skipManagedModules to true, -> don't do this!

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <system.webServer>
<applicationInitialization skipManagedModules="false" doAppInitAfterRestart="true">
  <add initializationPage="/" />
</applicationInitialization>
...

Although website is php, the routing to the paging is managed by the modules!!!

score 0 · Answer 21 · answered Jan 07 '16 at 12:00

I also ran into that problem. My MVC4 App is running on a Windows Server 2012 R2 with IIS 8.5. None of these posted solutions worked for me...installing the missing frameworks through IIS Features could have solved it but the installation always failed.

I had to use the Web Platform Installer and installed the following packages:

score 0 · Answer 22 · answered Mar 05 '17 at 14:19

I was facing this issue in a web application hosted on a shared hosting server. So obviously did not have direct access to IIS, so could not apply many solution proposed here.

On the hosting provider's control panel I enabled error logging for IIS and ASP.Net. And then got to know that error actually lied in a missing cshtml.

Handler "ExtensionlessUrlHandler-Integrated-4.0" has a bad module "ManagedPipelineHandler" in its module list

22 Answers22

Disable WebDAV for Individual App Pool:

Linked