Previous Next

• 05-20-2008, 7:04 PM

  tcontino Joined on 05-20-2008, 10:56 PM Posts 2 tcontino

  Bad module "ManagedPipelineHandler" in its module list Reply Contact I am in the process of deploying an existing web service developed in .Net 1.1 and WSE 2.0 to IIS 7.0. When I attempt to go to the URL associated with the service I receive the following error: HTTP Error 500.21 - Internal Server Error Handler "WebServiceHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list. Does anyone have information on how to resolve this problem? Tom

  Tags: IIS 7.0500

• 05-20-2008, 7:15 PM

  In reply to

  anilr Joined on 05-23-2006, 10:13 PM Redmond, WA Posts 988 anilr	Re: Bad module "ManagedPipelineHandler" in its module list Reply Contact What does the handler entry for "WebServiceHandlerFactory-Integrated" look like in configuration? Anil Ruia Senior Software Design Engineer IIS Core Server

• 05-20-2008, 7:33 PM

  In reply to

  tcontino Joined on 05-20-2008, 10:56 PM Posts 2 tcontino

  Re: Bad module "ManagedPipelineHandler" in its module list Reply Contact There are to line items as follows:  ASPNET-ISAPI-1.1-WebServiceHandlerFactory which points to C:\Windows\Microsoft.Net\Framework\v1.1.4322\aspnet_isapi.dll and  WebServiceHandlerFactory-Integrated which points to System.Web.Services.Protocols.WebServiceHandlerFactory, System.Web.Services, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a if change the application pool to be Classic vs. Integrated for this service I then receive the following error: The page you are requesting cannot be served because of the ISAPI and CGI Restriction list settings on the Web server. When looking at the handler section it indicates this is "enabled" at the server and the web site level.  What else could be the missing?

• 05-20-2008, 7:50 PM

  In reply to

  anilr Joined on 05-23-2006, 10:13 PM Redmond, WA Posts 988 anilr	Re: Bad module "ManagedPipelineHandler" in its module list Reply Contact Looks like you have not installed the asp.net feature from within IIS in "Add/Remove windows component" so that all the regstration needed to run asp.net is not present in your configuration. Anil Ruia Senior Software Design Engineer IIS Core Server