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

user_525780 0
Viewed 320310

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?

asp.net-4.0 iis-7 asp.net-mvc configuration
19 Answers

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.

user_652440

I had a similar issue with Windows server 2012, installing the feature "Application Server" in the server manager fixed the issue.

user_12551620

  1. run cmd

  2. drag and drop Aspnet_regiis.exe into the command prompt from:

    C:\Windows\Microsoft.NET\Framework64\v2.0.50727\

  3. type -i (for example Aspnet_regiis.exe -i)

  4. hit enter

  5. wait until the process completes

Good luck!

user_117161160
Related