500.21 Bad module “ManagedPipelineHandler” in its module list

后端 未结 12 1912
遥遥无期
遥遥无期 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:18

    I had this problem every time I deployed a new website or updated an existing one using MSDeploy.

    I was able to fix this by unloading the app domain using MSDeploy with the following syntax:

    msdeploy.exe -verb:sync -source:recycleApp -dest:recycleApp="Default Web Site/myAppName",recycleMode=UnloadAppDomain
    

    You can also stop, start, or recycle the application pool - more details here: http://technet.microsoft.com/en-us/library/ee522997%28v=ws.10%29.aspx

    While Armaan's solution helped get me unstuck, it did not make the problem go away permanently.

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

    I had this issue in Windows 10 when I needed IIS instead of IIS Express. New Web Project failed with OP's error. Fix was

    Control Panel > Turn Windows Features on or off > Internet Information Services > World Wide Web Services > Application Development Features

    tick ASP.NET 4.7 (in my case)

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

    Install .NET framework as below, it will work .NET version 4.5 as well.

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

    Some time only give aspnet_regiis.exe -i don't work so give aspnet_regiis.exe -ir in above path.

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

    I got this error on my ASP.Net 4.5 app on Windows Server 2012 R2.

    Go to start menu -> "Turn windows features on or off". A wizard popped up for me.

    Click Next to Server Roles

    I had to check these to get this to work, located under Web Server IIS->Web Server-> Application Development (these are based on Jeremy Cook's answer above):

    Then click next to Features and make sure the following is checked:

    Then click next and Install. At this point, the error went away for me. Good luck!

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

    This is because IIS 7 uses http handlers from both <system.web><httpHandlers> and <system.webServer><handlers>. if you need CloudConnectHandler in your application, you should add <httpHandlers> section with this handler to the <system.web>:

    <httpHandlers>
        <add verb="*" path="CloudConnect.aspx" type="CloudConnectHandler" />
    </httpHandlers>
    

    and also add preCondition attribute to the handler in <system.webServer>:

    <handlers>
      <add name="CloudConnectHandler" verb="*" path="CloudConnect.aspx" type="CloudConnectHandler" preCondition="integratedMode" />
    </handlers>
    

    Hope it helps

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

    if it is IIS 8 go to control panel, turn windows features on/off and enable Bad "Named pipe activation" then restart IIS. Hope the same works with IIS 7

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