locked
HTTP Error 500.19 - Internal Server Error: RRS feed

  • Question

  • User1604693657 posted

    Hi,

       I have crystal report version 12.0.0.683. I have published a WCF service project using VS 2008 in which some crystal reports were built using 12.0.2000.0.

    More Information: Vista Ultimate, VS 2008, Framework 3.5 sp1.

       I got a error when accessed published project as :

    <FIELDSET style="PADDING-BOTTOM: 10px; PADDING-LEFT: 15px; PADDING-RIGHT: 15px; PADDING-TOP: 0px"><LEGEND style="BORDER-BOTTOM: rgb(150,150,150) 1px solid; BORDER-LEFT: rgb(237,237,237) 1px solid; PADDING-BOTTOM: 4px; BACKGROUND-COLOR: rgb(231,236,240); MARGIN: 4px 0px 8px -12px; PADDING-LEFT: 10px; PADDING-RIGHT: 15px; COLOR: rgb(51,51,51); FONT-SIZE: 1em; BORDER-TOP: rgb(237,237,237) 1px solid; FONT-WEIGHT: bold; BORDER-RIGHT: rgb(150,150,150) 1px solid; PADDING-TOP: 4px; -webkit-background-clip: initial; -webkit-background-origin: initial">Error Summary</LEGEND>

    HTTP Error 500.19 - Internal Server Error

    The requested page cannot be accessed because the related configuration data for the page is invalid.

    </FIELDSET>
    <FIELDSET style="PADDING-BOTTOM: 10px; PADDING-LEFT: 15px; WIDTH: 662px; PADDING-RIGHT: 15px; HEIGHT: 438px; PADDING-TOP: 0px"><LEGEND style="BORDER-BOTTOM: rgb(150,150,150) 1px solid; BORDER-LEFT: rgb(237,237,237) 1px solid; PADDING-BOTTOM: 4px; BACKGROUND-COLOR: rgb(231,236,240); MARGIN: 4px 0px 8px -12px; PADDING-LEFT: 10px; PADDING-RIGHT: 15px; COLOR: rgb(51,51,51); FONT-SIZE: 1em; BORDER-TOP: rgb(237,237,237) 1px solid; FONT-WEIGHT: bold; BORDER-RIGHT: rgb(150,150,150) 1px solid; PADDING-TOP: 4px; -webkit-background-clip: initial; -webkit-background-origin: initial">Detailed Error Information</LEGEND>
    Module IIS Web Core
    Notification BeginRequest
    Handler Not yet determined
    Error Code 0x800700b7
    Config Error Cannot add duplicate collection entry of type 'add' with unique key attribute 'name' set to 'CrystalImageHandler.aspx_GET'
    Config File \\?\C:\inetpub\wwwroot\AdverantProject\web.config
    Requested URL http://localhost:80/AdverantProject/
    Physical Path C:\inetpub\wwwroot\AdverantProject\
    Logon Method Not yet determined
    Logon User Not yet determined
    Failed Request Tracing Log Directory C:\inetpub\logs\FailedReqLogFiles
    </FIELDSET>
    <FIELDSET style="PADDING-BOTTOM: 10px; PADDING-LEFT: 15px; PADDING-RIGHT: 15px; PADDING-TOP: 0px"><LEGEND style="BORDER-BOTTOM: rgb(150,150,150) 1px solid; BORDER-LEFT: rgb(237,237,237) 1px solid; PADDING-BOTTOM: 4px; BACKGROUND-COLOR: rgb(231,236,240); MARGIN: 4px 0px 8px -12px; PADDING-LEFT: 10px; PADDING-RIGHT: 15px; COLOR: rgb(51,51,51); FONT-SIZE: 1em; BORDER-TOP: rgb(237,237,237) 1px solid; FONT-WEIGHT: bold; BORDER-RIGHT: rgb(150,150,150) 1px solid; PADDING-TOP: 4px; -webkit-background-clip: initial; -webkit-background-origin: initial">Config Source</LEGEND>
      129:       <add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
      130:       <add name="CrystalImageHandler.aspx_GET" verb="GET" path="CrystalImageHandler.aspx" type="CrystalDecisions.Web.CrystalImageHandler, CrystalDecisions.Web, Version=12.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304" preCondition="integratedMode"/>
      131:     </handlers>
    </FIELDSET>



          Anyone look into it, which will be helpful to me.

    Thanks.

    Tuesday, May 26, 2009 9:50 AM

Answers

  • User372121194 posted

    Hi,

    The error message means that there are two types 'add' with unique key attribute 'name' set to 'CrystalImageHandler.aspx_GET' in web.config.

    Please make sure there is not same type with 'name' set to 'CrystalImageHandler.aspx_GET' in your web.config.

    When ASP.NET is starting, the web.config file will be integrated with inherited web.config. So please make sure there is not type 'add' with unique key attribute 'name' set to 'CrystalImageHandler.aspx_GET' in parent web.config file.

     

    I look forward to receiving your test results.

     

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Thursday, May 28, 2009 5:35 AM
  • User854688209 posted
    500.19. You receive this error when the XML metabase contains invalid configuration information for the content type that you are trying to access. To resolve this issue, remove or correct the invalid configuration. This problem typically indicates a problem in the ScriptMap metabase key.

    Reference: http://support.microsoft.com/kb/318380

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Thursday, May 28, 2009 6:03 AM

All replies

  • User372121194 posted

    Hi,

    The error message means that there are two types 'add' with unique key attribute 'name' set to 'CrystalImageHandler.aspx_GET' in web.config.

    Please make sure there is not same type with 'name' set to 'CrystalImageHandler.aspx_GET' in your web.config.

    When ASP.NET is starting, the web.config file will be integrated with inherited web.config. So please make sure there is not type 'add' with unique key attribute 'name' set to 'CrystalImageHandler.aspx_GET' in parent web.config file.

     

    I look forward to receiving your test results.

     

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Thursday, May 28, 2009 5:35 AM
  • User854688209 posted
    500.19. You receive this error when the XML metabase contains invalid configuration information for the content type that you are trying to access. To resolve this issue, remove or correct the invalid configuration. This problem typically indicates a problem in the ScriptMap metabase key.

    Reference: http://support.microsoft.com/kb/318380

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Thursday, May 28, 2009 6:03 AM
  • User-1540559508 posted

    This might not help, but I wanted to comment that I spent hours on this same error and found the solution to my problem. It turned out to be something that nobody else ever documented, so I'm trying to spread the word for Google.

    It turned out that my root web was working fine, but my subwebs were not working fine and I got this error for the subweb. The subweb was an individually configured ASP.NET application. I figured that this wasn't important because the root web was just a flat HTML file, but it mattered.

    What happened in my case was that a few days ago I had relocated the root web, then updated IIS to point to the new directory. All of the subweb applications, however, were treated by IIS as virtual directories, each with its own physical directory mapping. So each had the stale path.

    More specifically, I moved "C:\web\www.mysite.com" to "C:\web\mysite.com", updated IIS for MySite to point to \web\mysite.com, and left it as such. The applications under mysite.com were each pointing to C:\web\www.mysite.com\[application].

    I had to update each subweb application's Basic Settings to point to the revised path, and the 500.19 error went away.

    Hope this helps others like it would've helped me.

    Jon

     

    Sunday, June 21, 2009 5:20 PM