500.21 Bad module “ManagedPipelineHandler” in its module list

后端 未结 12 1913
遥遥无期
遥遥无期 2021-01-30 02:40

I am getting the error:

HTTP Error 500.21 - Internal Server Error Handler \"CloudConnectHandler\" has a bad module \"ManagedPipelineHandler\" in its module list

相关标签:
12条回答
  • 2021-01-30 03:37

    Try switching to Integrated mode. See the following thread:

    IIS 7, HttpHandler and HTTP Error 500.21

    0 讨论(0)
  • 2021-01-30 03:37

    I discovered that the order of adding roles and features is important. On a fresh system I activate the role "application server" and there check explicitly .net, web server support and finally process activation service Then automatically a dialogue comes up that the role "Web server" needs to be added also.

    0 讨论(0)
  • 2021-01-30 03:40

    To fix the problem, I tried to run

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

    However It didn't work for me. I have to run another command line in CMD window as administrator. Here is the command:

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

    or

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

    Hope it will help.

    0 讨论(0)
  • 2021-01-30 03:42

    Please follow these steps:

    1) Run the command prompt as administrator.

    2) Type either of the two lines below in the command prompt:

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

    or

    %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i
    
    0 讨论(0)
  • 2021-01-30 03:44

    I ran into this error on a fresh build of Windows Server 2012 R2. IIS and .NET 4.5 had been installed, but the ASP.NET Server Role (version 4.5 in my case) had not been added. Make sure that the version of ASP.NET you need has been added/installed like ASP.NET 4.5 is in this screenshot.

    ASP.NET Server Role

    0 讨论(0)
  • 2021-01-30 03:45

    For me, I was getting this error message when using PUT or DELETE to WebAPI. I also tried re-registering .NET Framework as suggested but to no avail.

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

    Disable WebDAV for Individual App Pool:

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

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

    0 讨论(0)
提交回复
热议问题