 |
 |
 |
 |
 |
 |
||||
 |
||||
 |
||||
|
|||||||||||||||||
 |
Debugging UtilitiesCRVersion CRVersion.exe This is a very simple application that when executed, in command line, on a report server will report the DLL and ENGINE versions of the CRPE32.DLL. If the ENGINE is anything other than 1793, the Parallel Crystal version 2.4, 2.5, 2.6, or 2.7 software will not install. The correct output should look like this :
dcg.bat dcg.bat This is a batch fine that should be executed, in command line, on a report server. It will collect vital network data in the form of a text file that will be created in the same directory in which the batch file was run. This file should be emailed to Dynalivery’s Tech Support department at techsupport@dynalivery.com. When executed in the command line the output should look like this :
DorUtility.exe DorUtility.exe This is a simple utility that verifies that the .dor file contains valid data by using the .dor file and the .rpt file to generate output to HTML. To access the .dor file it is neccessary to edit the PCRESERVER_DOR_CLEANUP key and enter the value of “false”, “0” or “no”. This key value controls whether the DOR file on the report server should be deleted after the output is generated. The default value for this is “true”. By toggling the setting to off the .dor file will not be deleted. Instead it will be placed in the <<PATH TO DYNALIVERY>\PCRE\DORTemp directory. The GUI for DorUtility looks like this :
JavaTester Source code for JavaTester When installing Parallel Crystal for the first time it is important to validate the installation on the local report server before beginning development your own applications. For versions of Parallel Crystal earlier than v2.5 these validation steps were done manually. Installation validation tools have been built in to Parallel Crystal v2.6 for both COM (COM Tester) and Java (Java Tester) clients. Running box.rpt through these applications (and outside your web/portal server) acts as a debugging tool that will verify that PCRE is installed, running correctly, and that the application can reach it from the JDK on the client machine. These applications can be run from the start menu of the report server and the source code is installed in the <<PATH TO DYNALIVERY>>\ PCRE\Docs\SampleSource directory. Empty.rpt As their names suggest, this set of "empty" report templates are .rpt files with no database connections, no saved data, no Crystal parameters, no formulas, and even no fields. However, they are a very highly valuable debugging tool. They allow you to add one element at a time to your .rpt, to help you find the precise location and reason for errors. The technique of making minimal changes to a pre-existing empty report template also makes it easier for you to communicate with Dynalivery. Our technical support department typically asks customers to submit reproducible cases. This task can be difficult as Dynalivery does not have or seek access to your confidential database content or the Crystal parameters that your application might supply at run-time. We have provided separate copies of the empty report template for three versions of Crystal Reports, versions 7, 8.5, and 9. Please note that there are differences in the feature sets of these versions and they may be reflected by subtle differences in the underlying .rpt file format. Also, the "save as" feature of the various Crystal Reports Designers may not be 100% effective. Please use the version of the empty report template that matches your report engine. Annotate_Report_Server_Log Annotate_Report_Server_Log.bas (Keywords : Log, Reading Log, How do I read the log ?, server.log) Use this Excel macro to import our server.log file for easier reading. This macro will need to be imported into Excel through the Visual Basic editor (Tools>>Macro>>Visual Basic Editor). Once it is imported it can be run from the Macro menu under the tools menu. Important Note: This utility will not work as expected if you are outputting files to text. |
|||||
| BACK TO TOP BACK TO START |
|
