asp.net-mvc - staticfile - managedpipelinehandler execute_request_handler
How to fix: Handler “PageHandlerFactory-Integrated” has a bad module “ManagedPipelineHandler” in its module list (12)
-Using application initalization feature -requesting wrong pages (.asp) because of config inheritance
500.21 will occur on the first user connection only. Subsequent connections work.
Resolved by correcting the applicationInitialization url collection on the .NET website.
I am configuring an MVC 3 project to work on a local install of IIS and came across the following 500 error:
Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list.
It turns out that this is because ASP.Net was not completely installed with IIS even though I checked that box in the "Add Feature" dialog. To fix this, I simply ran the following command at the command prompt
If I had been on a 32 bit system, it would have looked like the following:
My question is, is there a way to install IIS on a windows 7 box to use .NET 4.0 (MVC 3) without taking this extra step?
Error: Handler “PageHandlerFactory-Integrated” has a bad module “ManagedPipelineHandler” in its module list
I found the articles to fix this issue by simply run the following commands at the command prompt.
If the system is 32 bit, it would have looked like this:
But, when I tried to execute these commands using cmd prompt, I got the following error/warning message:
C:\Windows\Microsoft.NET\Framework64\v4.0.30319>aspnet_regiis.exe -i Microsoft (R) ASP.NET RegIIS version 4.0.30319.33440 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.33440). This option is not supported on this version of the operating system. Administr ators should instead install/uninstall ASP.NET 4.5 with IIS8 using the "Turn Win dows Features On/Off" dialog, the Server Manager management tool, or the dism.e xe command line tool. For more details please see http://go.microsoft.com/fwlin k/?LinkID=216771. Finished installing ASP.NET (4.0.30319.33440).
To fix this on a Windows 8.1 I would suggest to do the following thing.
Go to - Turn Windows features on or off > Internet Information Services > World Wide Web Services > Application Development Features >Enable ASP.NET 4.5
This should resolve the issue.
I had a similar issue with Windows server 2012, installing the feature "Application Server" in the server manager fixed the issue.
I had the same problem and my solution was:
Go to "Turn Windows features on or off" > Internet Information Services > World Wide Web Services > Application Development Features >Enable ASP.NET 4.5
I had this problem and found that removing the following folder helped, even with the non-Express edition.Express:
I have tried to do aspnet_regiis in command prompt but I got answer that I don't have admin rights. Then, after some more googling and looking for a solution I tried to right click cmd and run it as an admin. Confirmed yes when dialog appeared, ran aspnet_iis again ant worked like a charm. In short: 1. check .NET framework in app_pool 2. run cmd as an admin 3. run aspnet_regiis -i
I would also check the obvious first: that the application pool is set to the correct framework and that your IIS application actually points to the folder where you put your files
If you want to deploy an MVC application without installing MVC, you can deploy the MVC DLL's with your application. This gets around installing MVC 3. You can use features in some .Net 4.0 namespaces without installing .Net using a similar approach.
None of these worked for me. So as I compared various app pools with one that worked vs one that didn't, I had to go into Advanced Settings for the App Pool, and set
Enable 32-Bit Applications = true
Then it worked fine!
The accepted answer is correct, however sometimes you would get the "Aspnet_regiis.exe is not recognized as an internal or external command, operable program or batch file." error message.
To resolve it try the following:
Make sure that your .NET 4.0 installation is not corrupted (run the installer and 'Repair' it). There's also a chance it is not installed on your machine at all.
If you're sure you don't have .NET 4.0 installed and want to run it as .NET 2.0, try this:
If you see the message "Aspnet_regiis.exe is not recognized as an internal or external command, operable program or batch file.", switch to the C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Aspnet_regiis.exe -i at the command prompt.
To solve the issue try to
repair the .net framework 4 and then run the command
To solve the issue try to repair the .net framework 4 and then run the command