When you run the .exe from SAP, it often unpacks the files into a temporary folder. Inside that folder, you will find the individual MSI files, including crruntime-64bit-13-0-20.msi . If you specifically need the standalone MSI for distribution via Group Policy (GPO) or SCCM, this is how you extract it.
installed first. Many Crystal Reports versions rely on the C++ 2015 redistributable to function. Permissions: Always run the
(Yes, same version – the runtime is version‑aware; 13.0.20 provides 13.0.2000.0 assemblies.) crruntime-64bit-13-0-20.msi
: It provides the necessary libraries to generate, export, and view report files (.rpt) within a .NET environment. Key Installation Details
Most users do not seek out this file voluntarily. It is typically a . There are two main scenarios where you will encounter this file: When you run the
: Usually requires the .NET Framework to be present on the machine.
Sometimes, the main software installs fine, but when you click a "Print Preview" or "Generate Report" button, the application crashes or throws an exception error (such as "Load Report Failed" or "Could not load file or assembly"). This indicates that while the software is installed, the specific Crystal Reports runtime engine (SP20) is missing from your system libraries. installed first
✅ After install, Crystal Reports runtime assemblies are placed in C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win64_x64
Given that crruntime-64bit-13-0-20.msi is typically a transient installer file, follow these guidelines:
| Scenario | Action | |----------|--------| | | After install, set Enable 32-Bit Applications = False in IIS app pool. Add assembly bindings to web.config . | | Windows service / EXE | Reference CrystalDecisions.*.dll version 13.0.2000.0 (they are binary-compatible with 13.0.20). | | Side-by-side with 32-bit runtime | Not supported – only one architecture of runtime version 13 can be installed per machine. | | Citrix / RDS | Install once per image. Use per‑machine installation, not per‑user. |