Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to fix: Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list

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

%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i 

If I had been on a 32 bit system, it would have looked like the following:

%windir%\Microsoft.NET\Framework\v4.0.21006\aspnet_regiis.exe -i 

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?

like image 732
hspain Avatar asked Jul 27 '11 14:07

hspain


People also ask

Which module has a bad module “managedpipelinehandler” in it?

145 replies on “IIS 7.5 error: Handler “PageHandlerFactory-Integrated” has a bad module “ManagedPipelineHandler” in its module list” yoshelynsays: September 9, 2010 at 9:16 am

What is wrong with pagehandlerfactory-integrated?

Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list [Detailed Error Information] Module IIS Web Core

How to fix typographical error in the handler module list?

•There is a typographical error in the configuration for the handler module list. [Things you can try:] •Install ASP.NET if you are using managed handler. •Ensure that the handler module's name is specified correctly.

Is there a managed handler in ASP NET?

•Managed handler is used; however, ASP.NET is not installed or is not installed completely. •There is a typographical error in the configuration for the handler module list. [Things you can try:]


1 Answers

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

%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i 

If I had been on a 32 bit system, it would have looked like the following:

%windir%\Microsoft.NET\Framework\v4.0.21006\aspnet_regiis.exe -i 

Remeber to run the command prompt as administrator (CTRL+SHIFT+ENTER)

like image 134
hspain Avatar answered Sep 17 '22 18:09

hspain