FAQs and solutions for deploying Crystal Reports
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. When distributing data to the client"Query Engine Error"
5. Load crpe32.dll failed
6. in ASP. NETProgramAn error occurred while loading the report: "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). These module files are in the 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. this module contains CR for.. Net management module, such as crystaldecisions and crystalreports. engine. DLL, crystaldecisions. web. DLL, and crystaldecisions. windows. forms. DLL ......
Managed_chs.msm is supported by the Chinese version of this module.
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 is usedThe 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.
InIn the Vs. net installation project, only the 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.
(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"
The query engineDLL (crqe. dll) is not correctly registered on the customer's computer.
To solve this problem, you can manually register on the customer's computer.Crqe. dll, use the following command:
Regsvr32 "C: \ Program Files \ common files \ crystal decisions \ 1.0 \ bin \ crqe. dll"
IfCrqe. 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.
You can find and register the correct version by using any of the following three methods: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 merging module to the installation project. ATL. MSM is part of Visual Studio installer 1.1 and can go to the Microsoft website.
-------------------------
3. Run the prompt "this field name is unknown" on the Win98 client"
Report onThe Win2000 client is running normally. When the Win98 client is running, the message "this field name is unknown "?
This is because the report is usedIn the SQL Server database, the field name is changed to the English field name because the field name is Chinese.
-------------------------
4. When distributing data to the client"Query Engine Error"
(1)"Installation Project"To include the following merging modules:
Vc_crt.msm
Vc_stl.msm
(2) In addition, make sure that msvcr70.dll and msvcp70.dll are stored in"System Directory".
-------------------------
5. Load crpe32.dll failed
Below isThe steps for deploying crystal report 9 in cr9net_deployment.pdf are as follows:
OpenWindows applications.
In Solution Explorer, right-clickWindows application solution, pointing"Add"And then click"Create a project".
In"Add a new project"In the dialog box, select"Project Type"In the pane"Install and deploy a project"And then select"Template"In the pane"Installation Project". Click"OK"Button.
In solution resource management, right-click the installation project and point"Add"And then click"Project output".
In"Add project output Group", Select"Primary output"And then click"OK".
All dependencies will be automatically added, as shown in figureDotnetfxredist_x86_enu.msm and dotnetcrystalreports. MSM.
You needDotnetcrystalreports. MSM is excluded from the project. Right-click this module in Solution Explorer and select"Exclude".
In Solution Explorer, right-click the installation project and point"Add"And then click"Merge Module".
In"Add Module"In the dialog box, select the following merge modules to add to the installation project, and then 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-clickLicense. MSM file, and then select"Attribute".
In"Attribute"Window, expandMergemoduleproperties, and then"License key"Enter a valid license key in the properties box.
Note:A license key must be provided whenever the Crystal Reports application is deployed.
Slave"Generate"In the menu, select"Generate a solution"To generate an application.
-------------------------
6. An error occurred while loading the report in ASP. NET: "load report failed"
EnsureASPnet local users have"Full Control".
-------------------------
7. When the. NET 9.1 program is deployed to Windows 98, an error occurs: "load report failed"
The query engineDLL (crqe. dll) is not correctly registered on the customer's computer.
to solve this problem, copy dbghelp. DLL to the "C: Windows \ System32" folder on the client computer.