Problems and Solutions after installing crystal report 9.2

Directory:

I. Introduction

Ii. Concepts and Principles

Iii. Problems

1. compiler error message: </B> bc30560: "crystalreportviewer" is not clear in the namespace "crystaldecisions. Web.

2. When copying the Crystal Report viewer, "control creation error" is displayed ".

3. When creating the Crystal Report viewer, the "control creation error" is displayed ".

4. analyzer error message: the base class includes the field "crystalreportviewer1", but its type (crystaldecisions. Web. crystalreportviewer) and control (crystaldecisions. Web. crystalreportviewer) are incompatible.

5. analyzer error message: the file named "crystaldecisions. Shared" is found. Program The set list definition does not match the Assembly reference.

6. Problem: Invalid report source

7. If you are using vs. NET 2003 ......

8. problem: in the web. <assemblies> <add Assembly = "crystaldecisions. crystalreports. engine, version = 9.2.3300.0, culture = neutral, publickeytoken = 692fbea5521e1304 "/>

Configuration error after I manually add it !!!

-------------------------------------------------------------------------

I. Introduction

In. net, the DLL hell problem is solved-containing metadata, self-descriptive assembly and Its xcopy deployment!

However, it seems that there are new problems-. Net program upgrade and migration ......

The upgrade is no longer just a simple installation, but you have to do some work ......

-------------------------------------------------------------------------

Ii. Concepts and Principles

1. "assembly version" of various Crystal Reports programs "......

Crystal Reports for Visual Studio. NET 2002

The "assembly version" of the Crystal Reports management component is 9.1.3300.

Crystal Reports for Visual Studio. NET 2003 Program

The "assembly version" of the Crystal Reports management component is 9.1.5000.0.

Crystal Reports 9 program (Visual Studio 2002 only)

The "file version" of the Crystal Reports management component is 9.2.9466.x.

Crystal Reports 9.2 Program (with Visual Studio 2002 and 2003)

The "file version" of the Crystal Reports management component is 9.2.9500.x.

------------------------------------------------

2. Crystal Report Viewer

In vs. net, the Crystal Report viewer version is 9.1.3300.0,

The crystal report viewer version in Crystal Report 9.2 is 9.2.3300.0.

After adding the Crystal Report viewer to the form, the following will be added to the aspx file: Code .

Code (1) <% @ register tagprefix = "cr" namespace = "crystaldecisions. web "assembly =" crystaldecisions. web, version = 9.1.3300.0, culture = neutral, publickeytoken = 692fbea5521e1304 "%>

To introduce the namespace crystaldecisions. Web.

Code (2) <CR: crystalreportviewer id = "crystalreportviewer1" runat = "server" enabledrilldown = "false" displaygrouptree = "false" Height = "50px" width = "350px"> </Cr: crystalreportviewer>

Is the label of the crystalreportviewer control.

-------------------------------------------------------------------------

Iii. Problems

1. compiler error message: </B> bc30560: "crystalreportviewer" is not clear in the namespace "crystaldecisions. Web.

-------------------------

Problem Analysis:

After "design view" deletes the Crystal Report viewer, code (1) still exists. if you add the new version of the Crystal Report viewer again, two different codes will appear (1 ):

<% @ Register tagprefix = "CR1" namespace = "crystaldecisions. Web" assembly = "crystaldecisions. Web, version = 9.2.3300.0, culture = neutral, publickeytoken = Signature" %>

<% @ Page Language = "VB" codebehind = "analysis. aspx. VB" autoeventwireup = "false" inherits = "research_vb.analysis" %>

<% @ Register tagprefix = "cr" namespace = "crystaldecisions. Web" assembly = "crystaldecisions. Web, version = 9.1.3300.0, culture = neutral, publickeytoken = Signature" %>

-------------------------

Solution:

Delete the Crystal Report viewer and all code (1) and add the Crystal Report viewer again.

------------------------------------------------

2. When copying the Crystal Report viewer, "control creation error" is displayed ".

-------------------------

Problem Analysis:

When copying the Crystal Report viewer, code (1) is not copied.

-------------------------

Solution:

Manually copy the code (1 ).

------------------------------------------------

3. When creating the Crystal Report viewer, the "control creation error" is displayed ".

-------------------------

Problem Analysis:

If it is not the Residual code (1), it is incredible ......

-------------------------

Solution:

(1) Delete the Crystal Report viewer control in design view;

(2) Delete the code in "HTML View" (1)

(3) create a crystal report viewer;

If the "control creation error" is displayed, switch to the "html" view, and then switch to the "design" view to automatically restore !!!

------------------------------------------------

4. analyzer error message: the base class includes the field "crystalreportviewer1", but its type (crystaldecisions. Web. crystalreportviewer) and control (crystaldecisions. Web. crystalreportviewer) are incompatible.

-------------------------

Problem Analysis:

Code (1) is not the current version of the Crystal Report Viewer

-------------------------

Solution:

Delete the Crystal Report viewer and all code (1) and add the Crystal Report viewer again.

------------------------------------------------

5. analyzer error message: the Assembly list definition "crystaldecisions. Shared" found does not match the Assembly reference.

Source File: e: \ WEB \ venditionsystem \ WEB. config row: 15

Assembly loading tracking: The following information helps determine why the assembly "crystaldecisions. Shared" cannot be loaded.

-------------------------

Problem Analysis:

The Assembly crystaldecisions. Shared in Web. config defines the Assembly List as Cr for vs. net, and the project references the CR 9.x version ......

-------------------------

Solution 1:

Create a new solution. Add the Crystal Report viewer to the form. The new version of the assembly list definition is automatically generated in Web. config, and then copy the Web. config ......

Solution 2:

Modify the definition of the old assembly list in Web. config:

<Add Assembly = "crystaldecisions. Shared, version = 9.1.3300.0, culture = neutral, publickeytoken = 692fbea5521e1304"/>

Change version = 9.1.3300.0 to version = 9.2.3300.0.

-------------------------

Summary: other conflicts referenced by crystaldecisions Assembly, such as: crystaldecisions. crystalreports. engine. The solution is the same as above.

------------------------------------------------

6. Problem: Invalid report source

-------------------------

Problem Analysis:

The versions of reportdocument, crystalreportviewer, and crystaldecisions are different:

-------------------------

Solution:

(1) Delete All crystaldecisions Assembly references;

(2) Delete All reportdocument and crystalreportviewer components;

(3) Follow 2. Modify the Toolbox settings of Visual Studio. NET;

(4) Add a new component to automatically generate a new reference.

------------------------------------------------

7. If you are using vs. NET 2003 ......

Problem: No. No drag-and-drop controls after upgrade, no code (1 )!!!

Problem Analysis:

If you are using vs. NET 2003, Crystal Reports 9 (version 9.2.0.x) cannot run correctly and must be upgraded to CR 9 (version 9.2.2.x ).

The specific problems are as follows:

-Add a new report to the project, but no corresponding report files are generated.

-Add a new report or report viewer to the project, but do not automatically add required references.

-You cannot create an instance of a strongly-typed report.

Solution:

Upgrade to CR 9 (version 9.2.2.x ).

------------------------------------------------

8. problem: in the web. <assemblies> <add Assembly = "crystaldecisions. crystalreports. engine, version = 9.2.3300.0, culture = neutral, publickeytoken = 692fbea5521e1304 "/>

Configuration error after I manually add it !!!

Solution:

Create a solution, add the crystal report file and the crystal report viewer, and overwrite the original program with its web. config ......