Sap Crystal Reports For .net Framework 4.0

by

  1. Crystal Reports Runtime
  2. Sap Crystal Reports For .net Framework 4.0 Download

On 32-bit platforms: 'HKEYLOCALMACHINE SOFTWARE SAP BusinessObjects Crystal Reports for.NET Framework 4.0 Crystal Reports' On 64-bit platforms: 'HKEYLOCALMACHINE SOFTWARE Wow6432Node SAP BusinessObjects Crystal Reports for.NET Framework 4.0 Crystal Reports' Under this key, create the subkeys ' Export Pdf'. The full path of the new key will be. . Software patches for various versions of SAP Crystal Reports are available on this site. SAP Crystal Reports for Visual Studio is compatible with the following versions of Microsoft Visual Studio: 2019, 2017, 2015, 2013, 2012, 2010. Supported Platforms. Contact us for a different build.

Symptom

  • Advanced logging for the Crystal Reports .NET SDK.
  • How to turn on/off crpe logging for the Crystal Reports .NET SDK?

Environment

  • Crystal Reports for Visual Studio 2010
  • Crystal Reports 2008
  • Crystal Reports XI R2
  • Crystal Reports XI R1
  • Crystal Reports 10
  • Visual Studio 2003, 2005, 2008

Resolution

Crystal Reports .NET Logging


When regular troubleshooting fails you may need to dive deeper into an issue to find out what is going on. You can turn on CRPE logging in the CR .NET SDK by modifying a few registry keys.

How to turn logging on and off


The first thing to keep in mind is that logging slows down performance. Logging is not recommended for long term use. It can result in a very slow reporting system and it creates large log files on the system.

  1. Create two .reg files called logging-on.reg and logging-off.reg using Notepad.
  2. Copy the text from the appropriate section below into each .reg file and save it.
  3. Copy the .reg files to the system where you need to do your logging.
  4. Double click the logging-on.reg file and merge the contents into the registry.
  5. Restart IIS, service, or Windows application you are monitoring. Note: The logging won't work if the Crystal runtime files are already in memory.
  6. Run the application until the point of failure, or your error message.
  7. Locate the .log files in your temp directory.
    1. Windows XP; C:Documents and Settings<user>Local SettingsTemp
    2. Windows Vista, 7, Server 2008; C:Users<user>AppDataLocalTemp
    3. Windows Server 2008 running Visual Studio IDE creates a subfolder 2 ( in my case ) that VS uses as a temp folder. This is where the log files are located
  8. They will be named according to the application. For example, if your app is called mySlowReport.exe - the log files will be named:
    1. mySlowReport.crpe.bkgrnd.log
    2. mySlowReport.crpe.Diagnostics.log
    3. mySlowReport.crpe.functions.log
Sap businessobjects crystal reports for .net framework 4.0

It is best to open and analyze these log files in Excel.

Note: This logging doesn't work for the bundled version of the CR .NET SDK for Visual Studio .NET 2003.

Descriptions for the registry key values:


Destinations:

0 - No logging
1 - Log output to file
2 - Log output to the debug output window
3 - Log output to file and to the debug output window

Positions:

0 - No Logging
1 - Log on function entry
2 - Log on function exit (default)
3 - Log on function entry and exit

LogErrorsOnly:

0 - Output all log messages.
1 - Output only log messages associated with an error (non-zero return)

Crystal Reports Runtime

Crystal Reports for Visual Studio 2010

NoteThe log file extension created by Crystal for Visual Studio 2010 is .GLF.

Enable Logging

Disable Logging

Crystal Reports 2008

Enable Logging

Disable Logging

Crystal Reports 2011/2013/2016

Enable Logging

Disable Logging

Crystal Reports XI R2

Enable Logging

Disable Logging

Crystal Reports XI R1

Enable Logging

Disable Logging

Crystal Reports for Visual Studio 2005

Enable Logging

Disable Logging

Keywords

trace tracing , KBA , BI-DEV-NET , BI Software Development Kits (SDKs) - .NET or Other , How To

Product

Crystal Reports 2008 V0 ; Crystal Reports 2008 V1 ; SAP Crystal Reports XI ; SAP Crystal Reports XI R2 ; SAP Crystal Reports, developer version for Microsoft Visual Studio ; SAP Crystal Reports, version for Visual Studio .NET 2005 ; SAP Crystal Reports, version for Visual Studio .NET 2008

Sap Crystal Reports For .net Framework 4.0 Download

If you're getting installation errors installing the Crystal Reports runtime engine, running our FULL Report Runner installer, make sure you're installing with administrator permissions, and please try the following two steps...
Note: If you are simply UPGRADING your runtime engine, you do not need to do anything with .Net 4. Just download and install the higher runtime engine.
---
1) Download the .Net 4 (4.x, 4.5.x, 4.6.x, 4.7.x) installer directly from Microsoft:
https://docs.microsoft.com/en-us/dotnet/framework/
(Install and/or repair your .Net 4 or 4.5 installation)
Note: Microsoft now has a .Net repair tool:
https://docs.microsoft.com/en-us/dotnet/framework/install/repair
---
2) Next, download and run the Crystal runtime engine installer separately:
SP3: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_3.msi
Note: SP3 is the runtime service pack we recommend the most. It is most stable of the runtime service packs.
SP20: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_20.msi
Note: SP20 is the runtime service pack we recommend for later operating systems like Windows Server 2016 or later. SP20 now ships with our full installer instead of SP3.
---
All runtime engines here (SP3 or SP20 is recommended by Jeff-Net for being most stable) :
SP1: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_1.msi
SP2: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_2.msi
SP3:https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_3.msi
SP4: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_4.msi
SP5: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_5.msi
SP6: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_6.msi
SP7: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_7.msi
SP8: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_8.msi
SP9: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_9.msi
SP10: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_10.msi
SP11: (This release was pulled by SAP for being too buggy)
SP12: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_12.msi
SP13: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_13.msi
SP14: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_14.msi
SP15: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_15.msi
SP16: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_16.msi
SP17: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_17.msi
SP18: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_18.msi
SP19: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_19.msi
SP20: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_20.msi
---
As of 2018.300/2018.305, our software now supports SP21 and later. You must be on 2018.305 or later to use SP21, though. Please see this news release discussing SP21 and later.
Note: Updating an existing Crystal runtime installation to 21 or later? We recommend uninstalling the previous version first. This has not been an issue in the past, but for whatever reason, SP21 and later does not seem to install correctly with a previous version installed.
SP21: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_21.msi
SP22: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_22.msi
SP23: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_23.msi
SP24: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_24.msi
SP25: https://s3.amazonaws.com/jnsupport/runtimes/CRRuntime_32bit_13_0_25.msi
---
Replacing/Uninstalling a Later Service Pack with an Older One:
You can upgrade any service pack by installing a later one. If you need to install a previous service pack (like go from SP20 to SP3), you will need to manually uninstall (and clean up) the later service pack/runtime engine... then install the previous one. Please follow the steps in this KB article to install a previous service pack:
https://help.jeff-net.com/knowledgebase/article/uninstalling-a-crystal-runtime-service-pack-manually-removing-the-crystal-runtime-engine
---
The runtime engine gets installed here:
C:Program Files (x86)SAP BusinessObjectsCrystal Reports for .NET Framework 4.0
32-bit edition DLLs:
32-bit machine: C:Program FilesSAP BusinessObjectsCrystal Reports for .NET Framework 4.0CommonSAP BusinessObjects Enterprise XI 4.0win32_x86
64-bit machine: C:Program Files (x86)SAP BusinessObjectsCrystal Reports for .NET Framework 4.0CommonSAP BusinessObjects Enterprise XI 4.0win32_x86
64-bit edition DLLs:
32-bit machine: NA
64-bit machine: C:Program Files (x86)SAP BusinessObjectsCrystal Reports for .NET Framework 4.0CommonSAP BusinessObjects Enterprise XI 4.0win64_x64
---
SAP Recommended Trouble-Shooting Tools:
https://help.jeff-net.com/knowledgebase/article/sap-recommended-trouble-shooting-tools-and-using-crlogger-dll
SAP Service Pack Links and Issues Addressed and Fixed:
http://www.crystalreports.com/crvs/confirm/