HTTP Error 500.21 - Internal Server Error Handler "CXML... RSS

• 

  Boxout6

  0 Points

  5 Posts

  • Reply
  •  

  HTTP Error 500.21 - Internal Server Error Handler "CXML" has a bad module "ManagedPipelineHandler...

  Jul 04, 2010 10:40 PM | LINK

  Hi, 

   I am trying to deploy the dynamic example onto IIS7 and I can't figure out how to get around the following error:

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

   The code works fine on my local machine with VS2010 but I would like to deploy this to my web server.  Has anyone had any luck doing this?  Could you share the IIS7 settings that are required to make this work?

   Below is my web.config:

  <?xml version="1.0" encoding="UTF-8"?>
  <configuration>
   
  <!-- If your network requires a proxy server to access external web resources, set it here -->
  <!--
  <system.net>
      <defaultProxy>
          <proxy bypassonlocal="True" proxyaddress="http://<your-proxy-server-url>"/>
      </defaultProxy>
  </system.net>
  -->
  
  <system.web>
      <!--
          Set compilation debug="true" to insert debugging
          symbols into the compiled page. Because this
          affects performance, set this value to true only
          during development.
      -->
      
      <!--
          The <authentication> section enables configuration
          of the security authentication mode used by
          ASP.NET to identify an incoming user.
  
          Note, the Pivot CTP1 desktop application does not support the Windows authentication
          mode, so the authentication mode is set to None here.
          The Silverlight PivotViewer control is able to use any type of authentication.
          If your collection application is only using the Silverlight PivotViewer and requires
          access to resources (files, databases, web services) using the Windows credentials of
          the person using the application, set the authentication mode to Windows.
      -->
  
      <authentication mode="Windows" />
  
      
      <!--
          The <customErrors> section enables configuration
          of what to do if/when an unhandled error occurs
          during the execution of a request. Specifically,
          it enables developers to configure html error pages
          to be displayed in place of a error stack trace.
  
          <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
              <error statusCode="403" redirect="NoAccess.htm" />
              <error statusCode="404" redirect="FileNotFound.htm" />
          </customErrors>
      -->
      <customErrors mode="RemoteOnly" />
  
     
  </system.web>
   
  <system.webServer>
      <!-- IIS uses these handler configuration values -->
      <handlers>
              <remove name="PageHandlerFactory-ISAPI-2.0-64" />
          <!--
              A generic handler that responds to requests for any CXML.
              You may leave this section as is, and place your collection factory assemblies into the
              bin folder of this ASP.NET Application for them to be used.
              Alternatively, you may add classes that implement the IHttpHandler (or HttpAsyncHandler)
              interface yourself and replace the generic handler below with the handlers specific to
              your CXML path.
              See the HttpHandler.cs source file for the generic implementation.
          -->
          <add name="CXML" path="*.cxml" verb="GET" type="PivotServer.CxmlHandler" />
  
          <!-- Deep Zoom Collection and Deep Zoom Image XML and image handlers -->
          <add name="DZC" path="*.dzc" verb="GET" type="PivotServer.DzcHandler" />
          <add name="DZI" path="*.dzi" verb="GET" type="PivotServer.DziHandler" />
          <add name="DeepZoomImage" path="*/dzi/*_files/*/*_*.jpg" verb="GET" type="PivotServer.DeepZoomImageHandler" />
          <add name="ImageTile" path="*_files/*/*_*.jpg" verb="GET" type="PivotServer.ImageTileHandler" />
      </handlers>
  
  <!--
      <staticContent>
          <mimeMap fileExtension=".cxml" mimeType="text/cxml" />
          <mimeMap fileExtension=".dzc" mimeType="text/xml" />
          <mimeMap fileExtension=".dzi" mimeType="text/xml" />
      </staticContent>
  -->
  </system.webServer>
  </configuration>
  
  

  IIS7 ManagedPipeHandler

• 

  mark.bramley

  Member

  42 Points

  6 Posts

  Microsoft

  • Reply
  •  

  Re: HTTP Error 500.21 - Internal Server Error Handler "CXML" has a bad module "ManagedPipelineHan...

  Jul 06, 2010 07:58 PM | LINK

  This typically means that an earlier version of .NET is being used by IIS. Ensure that .NET v4.0 is registered with IIS by running:

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

  (note, the folder name "v4.0.30319" may be different if your PC has a different sub-version of .NET 4.0 installed)

• 

  cjaskoll

  Member

  5 Points

  18 Posts

  • Reply
  •  

  Re: HTTP Error 500.21 - Internal Server Error Handler "CXML" has a bad module "ManagedPipelineHan...

  Jul 20, 2010 05:39 PM | LINK

  hi

  i just wanted to mention i am having the same issue:

  1) IIS7 - same error as above. working on the fix

  2) IIS6 - get a 404 error on the CXML page (httphandler)

  3) VS2010 Built In Server - works OK
  

  pivot IIS6 vs2010 pivotcontrol 404

• 

  e3burnh

  Member

  2 Points

  1 Post

  • Reply
  •  

  Re: HTTP Error 500.21 - Internal Server Error Handler "CXML" has a bad module "ManagedPipelineHan...

  Aug 12, 2010 07:53 PM | LINK

  Did anyone ever receive an answer to this issue?