SAP Knowledge Base Article - Public

2012565 - Crystal Reports for Visual Studio application Crash in Service Pack 9 - this.crystalReportViewer1.CachedPageNumberPerDoc = 10;

Symptom

After creating or updating a Crystal Reports for Visual Studio application with SP 9 and distributing to a runtime only PC you may experience a crash in the application when opening.

Environment

Crystal Reports for Visual Studio Service Pack 9

Cause

Due to a Forward Fit of ADAPT01702641 for CR 2008 FP 6.3 into CR for Vs SP 9 this line of code ( in BOLD below ) is placed into the InitializeComponent() section for the CR Windows Report Viewer:

private void InitializeComponent()
       {

// crystalReportViewer1
       // 
       this.crystalReportViewer1.ActiveViewIndex = -1;
       this.crystalReportViewer1.BorderStyle = System.Windows.Forms.BorderStyle.FixedSingle;
       this.crystalReportViewer1.CachedPageNumberPerDoc = 10;
       this.crystalReportViewer1.Cursor = System.Windows.Forms.Cursors.Default;
       this.crystalReportViewer1.Location = new System.Drawing.Point(8, 333);

Resolution

For now manually comment out the line.

Issue will be resolved in SP 10, the line will stay but it will be commented out.

Keywords

Crystal Reports for Visual Studio, crforvs, Crash, Service Pack 9, this.crystalReportViewer1.CachedPageNumberPerDoc = 10;, CachedPageNumberPerDoc , KBA , BI-DEV-NET-SDK , .NET SDK / COM SDK , Problem

Product

SAP Crystal Reports, developer version for Microsoft Visual Studio