€ Don't know why this Windows 7 64-bit Home Premium worked with a.NET 20 application and Crystal Reports for.NET 2.0 for a NET Framework 2.0 is already present on the target system. Both MSI installers The SAP Community is the quickest way for users to solve problems, learn more about SAP solutions, and invent. 
Posted by Jeff-Net Fan Support on 14 June 2012 08:48 AM 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 ( or later) installer directly from Microsoft: (Install and/or repair your.Net 4 or 4.5 installation) Note: Microsoft now has a.Net repair tool: --- 2) Next, download and run the Crystal runtime engine installer separately: SP3: Note: SP3 is the runtime service pack we recommend the most.
It is most stable of the runtime service packs. SP20: 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 is recommended by Jeff-Net for being most stable): SP1: SP2: SP3: SP4: SP5: SP6: SP7: SP8: SP9: SP10: SP11: (This release was pulled by SAP for being too buggy) SP12: SP13: SP14: SP15: SP16: SP17: SP18: SP19: SP20: --- 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. Note: Updating an existing Crystal runtime installation to 21 or later? We recommend.
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: SP22: --- 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 SP10 to SP3), you will need to manually uninstall (and clean up) the later service pack/runtime engine. Then install the previous one.
I also have a few applications with Crystal version 8.x. I have no problems with Windows 7 - 32 bit. 64 bit is giving me fits right now. The problem involves passing the path to the system workgroup file to crystal through the registry so crystal can access the database that is controlled by user permission. Another application using Crystal 8.x using ADO to pass the recordsets to Crystal runs with no problems.
Radeon 6470m kext. So, it seems to depend on your method of data access. Hope this is helpful to you. ===================================================== Update - I found the answer for passing the info to crystal 8.x through the registry - The entries that would normally be in the HKLM Software. Key need to be moved to the HKLM Software Wow6432Node. The keys in this location are passed to 32 bit programs running in the 64 bit environment.
So, now I have no remaining problem. Warning: Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved.