16-09-2021

Sap Crystal Reports For .net Framework 4.0

Symptom

Crystal Reports runtime engine for.NET Framework 4.0 (32Bit) EN 13.0.27.3480 SAPCrystal Reports runtime engine for.NET Framework 4.0 (32Bit) EN13.0.27.3480 Ralf Schmidt June 10, 2020 Leave a Comment. We made a project with Visual Studio 2010 and.NET 4.0 using Crystal Reports. But if we publish it on the server, it won't work. I remember that with Visual Studio 2008 you just downloaded an installer for the server, but I can't seem to find one for this version. HKEYCURRENTUSER Software SAP BusinessObjects Suite XI 4.0 For Crystal Reports for Visual Studio 2010 and above: HKEYLOCALMACHINE SOFTWARE Wow6432Node SAP BusinessObjects Crystal Reports for.NET Framework 4.0 (on 64 bit OS) HKEYCURRENTUSER Software SAP BusinessObjects Crystal Reports for.NET Framework 4.0. . 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.

Addin For Crystal Reports 2011 built for .NET framework 4.0 fails to load, this worked in previous builds

Environment

Cause

Crystal Reports 2011 Designer has a dependency on .NET 2.0 Framework

Resolution

Create a crw32.exe.config file and paste in the following:

<?xml version ='1.0'?>
<configuration>
<startup useLegacyV2RuntimeActivationPolicy='true' >
<supportedRuntime version='v4.0' />
</startup>
</configuration>

Save this to file to where crw32.exe is located:

C:Program Files (x86)SAP BusinessObjectsSAP BusinessObjects Enterprise XI 4.0win32_x86

Start up the Report Designer and open the View, Tool Bars menu and check on the External Command.

What this does is tell crw32.exe to use 4.0 framework. Found this MS kbase article:

According to MSDN: http://msdn.microsoft.com/en-us/library/w4atty68.aspx

Framework

If your application is built with the .NET Framework 4 but has a dependency on a mixed-mode assembly built with an earlier version of the .NET Framework, it is not sufficient to specify the .NET Framework 4 in the list of supported runtimes. In addition, in the <startup> element in your configuration file, you must set the useLegacyV2RuntimeActivationPolicy attribute to true.

Keywords

Sap Businessobjects Crystal Reports For .net Framework 4.0

Crystal Reports 2011, addins, .NET framework 4.0 , KBA , BI-RA , Reporting, analysis, and dashboards , BI-DEV-NET , BI Software Development Kits (SDKs) - .NET or Other , Problem

Product

4.0

Sap Crystal Reports For .net Framework 4.0 32 Bit

SAP Crystal Reports 2011 ; SAP Crystal Reports, developer version for Microsoft Visual Studio

Sap Crystal Reports For .net Framework 4.0 For Windows 7

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/