ReCrystallize Pro Support Frequently Asked Questions

HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.

Not yet using ReCrystallize Pro to enable viewing your Crystal Reports on the web?

Try it - click here to view sample Crystal Reports in your browser now.

Click here for more information and a free trial download.

Synopsis:

When attempting to view a Crystal Report on the web using ReCrystallize Pro's ASP.NET option, the following message is displayed:

HTTP Error 500.19 - Internal Server Error

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

Detailed Error Information

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

Error

More Information:

This error can occur when the web.config file that ReCrystallize Pro creates is duplicated in a lower level folder. 

The web.config file should ideally be included only in the highest level directory of an application and should not be duplicated in subdirectories.  Any duplicated copies of the web.config file in the lower level folders should be deleted.

About the web.config file created for ASP.NET

ReCrystallize Pro creates a web.config file along with each set of ASP.NET web pages.  The web.config file includes the minimal configuration settings necessary for the web application to display your reports. The web.config file is not unique for each report; it is common to all report web pages that use the same Crystal Reports version.

The recommended best practice is to place one copy of the web.config file at the root of the web site or at the top of the folder structure within the web site that houses the ReCrystallize Pro web pages and reports.  It is permissible to include  copies of the web.config file in multiple folders that are at the same level within the web site.  However, the web.config file must not be included at different levels within nested folders or an error will result.

Example of recommended best practice placement of the web.config file:

  • c:\inetpub\wwwroot\reports
    • web.config
    • c:\inetpub\wwwroot\reports\financials
      • financialreport-parameters.aspx
      • financialreport.aspx
      • financialreport.aspx.vb
      • financialreport.rpt
    • c:\inetpub\wwwroot\reports\sales
      • salesreport-parameters.aspx
      • salesreport.aspx
      • salesreport.aspx.vb
      • salesreport.rpt
      • c:\inetpub\wwwroot\reports\salesbyregion
        • salesreportbyregion-parameters.aspx
        • salesreportbyregion.aspx
        • salesreportbyregion.aspx.vb
        • salesreportbyregion.rpt
    • c:\inetpub\wwwroot\reports\hr
      • hrreport-parameters.aspx
      • hrreport.aspx
      • hrreport.aspx.vb
      • hrreport.rpt