FAQs during deployment of Crystal Reports
From csdn
------------------------------------------------
Directory:
1. Report loading error
2. An error occurred while deploying to Windows 98/me: "load report failed"
3. Run the prompt "this field name is unknown" on the Win98 client"
4. "query engine error" when distributed to the client"
5. Load crpe32.dll failed
6. An error occurred while loading the report in ASP. NET: "load report failed"
7. When the. NET 9.1 program is deployed to Windows 98, an error occurs: "load report failed"
------------------------------------------------
1. Report loading error
The problem lies in report Publishing.
A project that publishes a crystal report must contain three components: Report (*. rpt), Module (*. MSM), and Runtime Library (*. MSM ).
C:/program files/common files/merge modules/directory.
(1) Report (*. rpt)
The crystal report file created by the user during programming.
(2) module (*. MSM)
Managed. MSM this module contains the management module of CR for vs. net, such
Crystaldecisions, crystalreports. Engine. dll, crystaldecisions. Web. dll,
And crystaldecisions. Windows. Forms. dll ......
Managed_chs.msm is the Chinese version of this module
Language support.
Database_access.msm this module contains the database driver, the connection with different databases, and the documents and chart components that export reports in the RTF and HTML formats.
Database_access_chs.msm is supported in the Chinese language of this module.
Regwiz. MSM registration information module is very important. You must enter the registration serial number of the crystal report in this module.
(3) running database (*. MSM)
If the report file uses the dataset DataSet object of ADO. net, the vc_crt.msm and vc_stl.msm modules must also be included in the installation project. The "module retargetable folder" item of the File Installation attribute of the two modules must be modified to the system directory.
In the Vs. net installation project, only dotnetfxredist_x86_chs.msm and managed. MSM modules are detected by the system. We need to manually add other modules.
(1) In Solution Explorer, right-click the installation project and choose "add"-> "Merge Module (m )"
(2) In the "add module" dialog form, select managed_chs.msm, database_access,
Database_access_chs, regwiz, vc_crt.msm, and vc_stl.msm modules
(3) re-build the installation project. No problem, but the generated installation program is 7 or 8 Mb in size.
-------------------------
2. An error occurred while deploying to Windows 98/me: "load report failed"
It is because the query engine DLL (crqe. dll) is not correctly registered on the customer's computer.
To solve this problem, manually register crqe. dll on the client's computer and run the following command:
Regsvr32 "C:/program files/common files/crystal decisions/1.0/bin/crqe. dll"
If crqe. dll is not successfully registered and the problem persists, check the ATL. dll version on the customer's computer. The correct ATL. DLL for Windows 98/Me version is 3.0.8449.
By using any of the following three methods, you can find and register the correct version of ATL. dll.
(1) install ie6.0 on the client computer.
(2) manually copy and register ATL. dll on the customer's computer, and then run the installation package for Crystal Reports distribution.
(2) Add the ATL. MSM merge module to the installation project. ATL. MSM is part of Visual Studio installer 1.1. You can go to the Microsoft website http://msdn.microsoft.com/vstudio/downloads/tools/vsi11/download.aspxdownload.
-------------------------
3. Run the prompt "this field name is unknown" on the Win98 client"
The report works normally on the Win2000 client. when running the Report on the Win98 client, the message "this field name is unknown "?
The reason is that the field name in the SQL Server database used by the report is Chinese, and the field name is changed to English field name.
-------------------------
4. "query engine error" when distributed to the client"
A: That's because the VC runtime libraries are not installed: vc_crt.msm and vc_stl.msm.
-------------------------
5. Load crpe32.dll failed
The following describes how to deploy crystal report 9 in cr9net_deployment.pdf:
Open the windows application.
In Solution Explorer, right-click windows application solution, point to "add", and then click "Create Project ".
In the Add new project dialog box, select "Install and deploy Project" in the "project type" pane, and select "Install Project" in the "template" pane ". Click OK.
In solution resource management, right-click the installation project, point to "add", and then click "project output ".
In "add project output group", select "primary output" and click "OK ".
All dependencies are automatically added, such as dotnetfxredist_x86_enu.msm and dotnetcrystalreports. MSM.
To exclude dotnetcrystalreports. MSM from the project, right-click the module in Solution Explorer and choose exclude ".
In Solution Explorer, right-click the installation project, point to "add", and then click "Merge Module ".
In the "add module" dialog box, select the following modules to be added to the installation project, and click "open ":
Reportengine. MSM, crnetruntime. MSM, license. MSM
Mapping. MSM (optional. When geographic maps are used in the report)
Vc_crt.msm and vc_stl.msm (if the windows application you deploy uses the ADO. Net dataset, the vc_crt and vc_stl merging modules must also be included)
In Solution Explorer, right-click the license. MSM file and select "properties ".
In the Properties window, expand mergemoduleproperties and enter a valid license key in the license key attribute box.
Note that the license key must be provided whenever the Crystal Reports application is deployed.
From the "generate" menu, select "generate solution" to generate the application.
-------------------------
6. An error occurred while loading the report in ASP. NET: "load report failed"
Make sure that the local user of ASPnet has "Full Control" permission on the report folder.
-------------------------
7. When the. NET 9.1 program is deployed to Windows 98, an error occurs: "load report failed"
It is because the query engine DLL (crqe. dll) is not correctly registered on the customer's computer.
To solve this problem, copy dbghelp. dll from the development computer to the "C: Windows/system32" folder on the client computer.
How to deploy programs using Crystal Reports and vs. Net? (Translation: Haibo. Net)
Outline
How to deploy programs using Crystal Reports and vs. Net?
================================
Note:
Before deploying programs using Crystal Reports and Visual Studio. NET, you must confirm the following information:
The Crystal Reports version used with Visual Studio. NET. Possible versions:
-Crystal Reports for Visual Studio. NET 2002
-Crystal Reports for Visual Studio. NET 2003
-Crystal Reports 9
-Crystal Reports 9.2
The "assembly version" of the Crystal Reports management component ".
Check the "assembly version" of the Crystal Reports management component and view the "project"> "Reference" in Visual Studio. NET ".
Crystal Reports management components include:
-Crystaldecisions. crystalreports. Engine
-Crystaldecisions. Shared
-Crystaldecisions. reportsource
-Crystaldecisions. Web
-Crystaldecisions. Windows. forms.
The "assembly version" of all Crystal Reports management components must be the same.
================================
Solution:
Deploy a program that uses Crystal Reports for Visual Studio. NET 2002
------------------------------------------------
1. Make sure that the "assembly version" of the Crystal Reports management component is 9.1.3300.
2. Download the complete crnet deployment guide:
Http://support.crystaldecisions.com/communityCS/TechnicalPapers/crnet_deployment.pdf.asp? Recdnlreq1_record&dnlpath=crnet_deployment=
Deploy a program that uses Crystal Reports for Visual Studio. NET 2003
------------------------------------------------
1. Make sure that the "assembly version" of the Crystal Reports management component is 9.1.5000.0.
2. Download the complete crnet deployment guide:
Http://support.crystaldecisions.com/communityCS/TechnicalPapers/crnet_deployment.pdf.asp? Recdnlreq1_record&dnlpath=crnet_deployment=
3. Replace the Merge Module in 'crnet_deployment=' with the following merge statement:
Crystal_database_access2003.msm
Crystal_database_access2003_enu.msm
Crystal_managed2003.msm
Crystal_regwiz2003.msm
Vc_user_crt71_rtl_x86 _ ---. MSM (used by ADO. Net-based reports)
Vc_user_stl71_rtl_x86 _ ---. MSM (used by ADO. Net-based reports)
