table of Contents:
1, report the report
2. When deploying to Windows 98 / ME, an error: "Load Report Failed"
3, in Win98 client running prompt "The field name is not known"
4, "Query Engine Error" when distributing into the client
5, Load crpe32.dll failed
6. When loading a report in the ASP.NET program, an error: "Load Report Failed"
7, when deployed .NET 9.1 program to Windows 98, error: "Load Report Failed"
------------------------------------------------
1, report the report
The problem is published in the report.
Projects that use crystal reports need to include three components: report (* .rpt), module (* .msm), run library (* .msm), these module files are in C: / Program Files / Common Files / Merge Modules / Directory.
(1) Report (* .RPT)
The crystal report file created when the user is programmed.
(2) Module (* .msm)
Managed.msm This module contains the management module of Cr for VS .NET, such as Crystaldecisions, CrystalReports.EnGine.dll, Crystaldecisions.Web.dll, and Crystaldecisions.Windows.Forms.dll ......
Managed_chs.msm is the Chinese version of the module.
Database_access.msm This module contains a database of databases, coupled to different databases, exports documents and chart components in RTF and HTML formats.
Database_access_chs.msm is the Chinese version of this module.
RegWIZ.MSM registration information module, it is very important, you must enter the registration serial number of the crystal report in this module, if not fill, it is not possible to pass
(3) Running library (* .msm)
If the report file uses ADO.NET's DataSet dataset object, then VC_CRT.MSM and VC_STL.MSM modules must also be included in the installation project. And the "Module Retargetable Folder" item of the file installation attribute of the two modules must be modified to become a system directory.
In the VS.NET installation project, the system detected only the DOTNETFXREDIST_X86_CHS.MSM and Managed.MSM, and the other modules we need to be joined manually.
(1) In the Solution Explorer, right-click the installation item to select "Add" -> "merge module (M)"
(2) In the "Add Module" dialog, select Managed_chs.msm, Database_CHS_CHS, DATABASE_ACCESS_CHS, REGWIZ, VC_CRT.MSM, and VC_STL.MSM modules
(3) Recover the installation project, no problem, only the generated installer is 7, eight megabytes.
-------------------------
2. When deploying to Windows 98 / ME, an error: "Load Report Failed"
It is because query engine DLL (CRQE.DLL) is not registered correctly on the customer's computer.
To resolve this issue, you can manually register CRQE.dll on the customer's computer, use the following command:
Regsvr32 "C: / Program Files / Common Files / CRYSTAL DECISIONS / 1.0 / BIN / CRYSTAL DECISION / 1.0 / BIN / CRY.DLL" If CRQE.DLL is not successfully registered, the problem continues to exist, check the version of ATL.dll on the client computer. Atl.dll for Windows 98 / ME The correct version is 3.0.8449.
By using any of the following methods, you can find and register the correct version of ATL.dll.
(1) Upload IE6.0 in the customer's computer.
(2) On the customer's computer, copy and register ATL.dll manually, and then run the installation package for Crystal Reports.
(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 Microsoft's website
Http://msdn.microsoft.com/vstudio/downloads/tools/vsi11/download.aspx Download, add a way to the same.
-------------------------
3, in Win98 client running prompt "The field name is not known"
Reports everything in Win2000 is normal, running in Win98 client prompt "The field name is not known"?
It is because the field names in the SQL Server database used in the SQL Server database are named in Chinese, and their field names are named in English.
-------------------------
4, "Query Engine Error" when distributing into the client
(1) "Installation Project" To include the following merge modules:
VC_CRT.MSM
VC_STL.MSM
(2) In addition, ensure that MSVCR70.DLL and MSVCP70.DLL in the "System Directory" of the client computer.
-------------------------
5, Load crpe32.dll failed
Below is the step of deploying CRYSTAL REPORT 9 in CR9NET_DEPLOYMENT.PDF:
Open the Windows application.
In the Solution Explorer, right-click on the Windows application solution, point to Add, and then click New Project.
In the Add New Project dialog, select Install and Deploy Projects in the Project Type pane, then select Install Projects in the Template pane. Click the "OK" button.
In the Solution Resource Management, right click on the installation item, point to Add, and then click Project Output.
In the Add Project Output Group, select "Main Output" and click OK.
All dependencies are automatically added, such as DOTNETFXREDIST_X86_ENU.MSM and DotNetCrystalReports.msm.
You need to exclude DotNetCryStalReports.msm in the project, right-click on the right click of this module in the Solution Explorer, and select "Exclude".
In the Solution Explorer, right-click the installation item, point to Add, and then click Merge Module.
In the Add Module dialog box, select the following to add the merge module to the installation item, and then click Open:
ReportEngine.MSM, CrNetruntime.msm, license.msm
Mapping.msm (optional, when you use Geographic Maps in the report)
VC_CRT.MSM, VC_STL.MSM (if you deploy Windows application uses the ADO.NET dataset, you also need to include VC_CRT and VC_STL merge modules)
In the Solution Explorer, right-click the license.msm file and select Properties. In the Properties window, expand MergeModuleProperties, then enter a valid license key in the License Key Properties box.
Note You must provide a license key whenever a Crystal Reports application is deployed.
From the Generate menu, select Generate Solution to generate an application.
-------------------------
6. When loading a report in the ASP.NET program, an error: "Load Report Failed"
Make sure that the ASPNET local user has "full control" permissions to the folder where the report is located.
-------------------------
7, when deployed .NET 9.1 program to Windows 98, error: "Load Report Failed"
It is because query engine DLL (CRQE.DLL) is not registered correctly on the customer's computer.
To solve this problem, copy DBGHELP.DLL from the development computer to the "C: Windows / System32" folder of the client computer.
