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?
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.
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
Software Design Engineer
IIS Core Server
tcontino
2 Posts
Bad module "ManagedPipelineHandler" in its module list
May 20, 2008 11:04 PM|LINK
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
IIS 7.0 500
anilr
2343 Posts
Microsoft
Re: Bad module "ManagedPipelineHandler" in its module list
May 20, 2008 11:15 PM|LINK
What does the handler entry for "WebServiceHandlerFactory-Integrated" look like in configuration?
Software Design Engineer
IIS Core Server
tcontino
2 Posts
Re: Bad module "ManagedPipelineHandler" in its module list
May 20, 2008 11:33 PM|LINK
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?
anilr
2343 Posts
Microsoft
Re: Bad module "ManagedPipelineHandler" in its module list
May 20, 2008 11:50 PM|LINK
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.
Software Design Engineer
IIS Core Server
SM
1 Post
Re: Bad module "ManagedPipelineHandler" in its module list
Aug 29, 2009 02:54 PM|LINK
Hi, on my side, im sure that i installed ASP.NET feature but still have that error:
Handler "PageHandlerFactory-Integrated" has a bad module "ManagedPipelineHandler" in its module list
I tried to had this line:
<section name="system.webServer" type="System.Configuration.IgnoreSectionHandler,
System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
</configSections>
in ../v1.1.4322/CONFIG/machine.confi file but does not work
but i dont know problem could be into applicationhost.config maybe? This is what applicationhost.config looks like:
<location path="" overrideMode="Allow">
<system.webServer>
<handlers accessPolicy="Read, Script">
<add name="PageHandlerFactory-Integrated" path="*.aspx" verb="GET,HEAD,POST,DEBUG" type="System.Web.UI.PageHandlerFactory" preCondition="integratedMode" />
<add name="PageHandlerFactory-ISAPI-2.0" path="*.aspx" verb="GET,HEAD,POST,DEBUG" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" preCondition="classicMode,runtimeVersionv2.0,bitness32" responseBufferLimit="0" />
<add name="ASPClassic" path="*.asp" verb="GET,HEAD,POST" modules="IsapiModule" scriptProcessor="%windir%\system32\inetsrv\asp.dll" resourceType="File" />
<add name="SecurityCertificate" path="*.cer" verb="GET,HEAD,POST" modules="IsapiModule" scriptProcessor="%windir%\system32\inetsrv\asp.dll" resourceType="File" />
<add name="ISAPI-dll" path="*.dll" verb="*" modules="IsapiModule" resourceType="File" requireAccess="Execute" allowPathInfo="true" />
<add name="CGI-exe" path="*.exe" verb="*" modules="CgiModule" resourceType="File" requireAccess="Execute" allowPathInfo="true" />
<add name="TraceHandler-Integrated" path="trace.axd" verb="GET,HEAD,POST,DEBUG" type="System.Web.Handlers.TraceHandler" preCondition="integratedMode" />
<add name="WebAdminHandler-Integrated" path="WebAdmin.axd" verb="GET,DEBUG" type="System.Web.Handlers.WebAdminHandler" preCondition="integratedMode" />
<add name="AssemblyResourceLoader-Integrated" path="WebResource.axd" verb="GET,DEBUG" type="System.Web.Handlers.AssemblyResourceLoader" preCondition="integratedMode" />
<add name="SimpleHandlerFactory-Integrated" path="*.ashx" verb="GET,HEAD,POST,DEBUG" type="System.Web.UI.SimpleHandlerFactory" preCondition="integratedMode" />
<add name="WebServiceHandlerFactory-Integrated" path="*.asmx" verb="GET,HEAD,POST,DEBUG" type="System.Web.Services.Protocols.WebServiceHandlerFactory, System.Web.Services, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" preCondition="integratedMode" />
<add name="HttpRemotingHandlerFactory-rem-Integrated" path="*.rem" verb="GET,HEAD,POST,DEBUG" type="System.Runtime.Remoting.Channels.Http.HttpRemotingHandlerFactory, System.Runtime.Remoting, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" preCondition="integratedMode" />
<add name="HttpRemotingHandlerFactory-soap-Integrated" path="*.soap" verb="GET,HEAD,POST,DEBUG" type="System.Runtime.Remoting.Channels.Http.HttpRemotingHandlerFactory, System.Runtime.Remoting, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" preCondition="integratedMode" />
<add name="AXD-ISAPI-2.0" path="*.axd" verb="GET,HEAD,POST,DEBUG" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" preCondition="classicMode,runtimeVersionv2.0,bitness32" responseBufferLimit="0" />
<add name="SimpleHandlerFactory-ISAPI-2.0" path="*.ashx" verb="GET,HEAD,POST,DEBUG" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" preCondition="classicMode,runtimeVersionv2.0,bitness32" responseBufferLimit="0" />
<add name="WebServiceHandlerFactory-ISAPI-2.0" path="*.asmx" verb="GET,HEAD,POST,DEBUG" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" preCondition="classicMode,runtimeVersionv2.0,bitness32" responseBufferLimit="0" />
<add name="HttpRemotingHandlerFactory-rem-ISAPI-2.0" path="*.rem" verb="GET,HEAD,POST,DEBUG" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" preCondition="classicMode,runtimeVersionv2.0,bitness32" responseBufferLimit="0" />
<add name="HttpRemotingHandlerFactory-soap-ISAPI-2.0" path="*.soap" verb="GET,HEAD,POST,DEBUG" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll" preCondition="classicMode,runtimeVersionv2.0,bitness32" responseBufferLimit="0" />
<add name="TRACEVerbHandler" path="*" verb="TRACE" modules="ProtocolSupportModule" requireAccess="None" />
<add name="OPTIONSVerbHandler" path="*" verb="OPTIONS" modules="ProtocolSupportModule" requireAccess="None" />
<add name="StaticFile" path="*" verb="*" modules="StaticFileModule,DefaultDocumentModule,DirectoryListingModule" resourceType="Either" requireAccess="Read" />
</handlers>
<modules>
<add name="HttpCacheModule" lockItem="true" />
<add name="StaticCompressionModule" lockItem="true" />
<add name="DefaultDocumentModule" lockItem="true" />
<add name="DirectoryListingModule" lockItem="true" />
<add name="IsapiFilterModule" lockItem="true" />
<add name="ProtocolSupportModule" lockItem="true" />
<add name="StaticFileModule" lockItem="true" />
<add name="AnonymousAuthenticationModule" lockItem="true" />
<add name="RequestFilteringModule" lockItem="true" />
<add name="CustomErrorModule" lockItem="true" />
<add name="IsapiModule" lockItem="true" />
<add name="HttpLoggingModule" lockItem="true" />
<add name="ConfigurationValidationModule" lockItem="true" />
<add name="OutputCache" type="System.Web.Caching.OutputCacheModule" preCondition="managedHandler" />
<add name="Session" type="System.Web.SessionState.SessionStateModule" preCondition="managedHandler" />
<add name="WindowsAuthentication" type="System.Web.Security.WindowsAuthenticationModule" preCondition="managedHandler" />
<add name="FormsAuthentication" type="System.Web.Security.FormsAuthenticationModule" preCondition="managedHandler" />
<add name="DefaultAuthentication" type="System.Web.Security.DefaultAuthenticationModule" preCondition="managedHandler" />
<add name="RoleManager" type="System.Web.Security.RoleManagerModule" preCondition="managedHandler" />
<add name="UrlAuthorization" type="System.Web.Security.UrlAuthorizationModule" preCondition="managedHandler" />
<add name="FileAuthorization" type="System.Web.Security.FileAuthorizationModule" preCondition="managedHandler" />
<add name="AnonymousIdentification" type="System.Web.Security.AnonymousIdentificationModule" preCondition="managedHandler" />
<add name="Profile" type="System.Web.Profile.ProfileModule" preCondition="managedHandler" />
<add name="UrlMappingsModule" type="System.Web.UrlMappingsModule" preCondition="managedHandler" />
<add name="CgiModule" lockItem="true" />
<add name="FastCgiModule" lockItem="true" />
</modules>
</system.webServer>
</location>
anilr
2343 Posts
Microsoft
Re: Bad module "ManagedPipelineHandler" in its module list
Oct 23, 2009 12:06 AM|LINK
From your description, it sounds like you have configured your app-pool to run asp.net 1.1 in integrated mode which asp.net 1.1 does not support.
Software Design Engineer
IIS Core Server
doyuga
1 Post
Re: Bad module "ManagedPipelineHandler" in its module list
Nov 16, 2009 10:57 AM|LINK
I think your ASP.net installation was not registered correctly. Try the following steps to register it.
run %windir%\Microsoft.NET\Framework\v4.0.21006\aspnet_regiis.exe -i
this should help you out.
Thanks
Dan
Charana
1 Post
Re: Bad module "ManagedPipelineHandler" in its module list
Nov 18, 2009 02:58 PM|LINK
adefwebserve...
3 Posts
Re: Bad module "ManagedPipelineHandler" in its module list
Nov 19, 2009 12:32 PM|LINK
Yes this works!
I figured everything was set up correctly because I was able to see ASP.NET 4.0 in the IIS. However only after I ran this fix did it work. Whew!
Open Light Group
LightSwitchHelpWebsite.com | ADefWebserver.com
wkpli
13 Posts
Re: Bad module "ManagedPipelineHandler" in its module list
May 03, 2010 05:07 PM|LINK
How come we were talking about ASP .NET v1.1 and all in a sudden we have to register v4.0?
I got the same problem, but I don't have ASP .NET 4.0. Does that mean I have to install ASP .NET 4.0?
Thanks in advance.