cancel
Showing results for 
Search instead for 
Did you mean: 

blank page after publish Crystal Reports 13 ( Visual Studio 2013 ) to IIS?

Former Member
0 Kudos

Why do I get blank page after publish Crystal Reports 13 ( Visual Studio 2010 ) to IIS? This issue does not occur in local but happens when you host the site on server in IIS.

Below are the steps to resolve the issue Resolution 1:

1. Downloading and installing runtime for Crystal Reports 13 for Visual Studio 2010. (You might want to skip this step if you already did this before and your application is working locally).

2. Once the runtime is installed. Crystal Reports will install the required support files in the location of your local computer:
C:\inetpub\wwwroot\aspnet_client\system_web\4_0_30319\crystalreportviewers13

3. Copy the entire Crystal Report Support folder C:\inetpub\wwwroot\aspnet_client\system_web\4_0_30319\crystalreportviewers13 to your Website's SITE_ROOT\aspnet_client\system_web\4_0_30319 folder.

4) If you do not have a \aspnet_client\system_web\4_0_30319 folders in your website's root. Please create them manually and then copy the crystalreportviewers13 into it. Add below lines in web.config of the web application.
<configSections> <sectionGroup name="businessObjects"> <sectionGroup name="crystalReports"> <section name="rptBuildProvider" type="CrystalDecisions.Shared.RptBuildProviderHandler, CrystalDecisions.Shared, Version=13.0.2000.0, Culture=neutral, PublicKeyToken=692fbea5521e1304, Custom=null" /> <section name="crystalReportViewer" type="System.Configuration.NameValueSectionHandler" /> </sectionGroup> </sectionGroup> </configSections> <businessObjects> <crystalReports> <rptBuildProvider> <add embedRptInResource="true" /> </rptBuildProvider> <crystalReportViewer> <add key="ResourceUri" value="~/crystalreportviewers13" /> </crystalReportViewer> </crystalReports> </businessObjects>

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Run Fiddler and see what it's missing. Or hit the F12 button to see if anything is reported.

Could be your report did not load, check permissions and see KBA 1215387 on how to use Sessions and PostBack methods to keep the report in scope.

Don

Answers (0)