Crystal Reports XI R2 runtime on Windows 7 x64 - crystal-reports

We are using Crystal Reports XI R2 (11.5.3300.0) in existing (32 bits) applications. We are in the process of upgrading to Windows7 64 bits.
During our compatibility tests, we bump into an issue indicating the crystal reports runtime is not available. I'm leaving out the exception detail here, as it is in Dutch, but basically it is saying that the runtime is not installed correctly, and that I should install the distributable CRRedist*.msi.
The problem I'm having is that I can't seem to find that distributable. When I check on the support site, https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=56787567, it refers to a bootstrapper in the Program Files folder. However, the indicated subfolder does not exist.
Anyone who has bumped into the same type of problems for this version of Crystal Reports (I'm aware of the fact that several versions have been released after this one)? Where can I find the redistributable?
Mind that our applications are compiled for x86, so I think that the x86 runtime should do the trick.
Thanks.

just a quick caveat to any answer for you, if performance is important you should know that the x86 dlls will be significantly slower under emulation in an x64 o/s

I know this is an old question, but it was something I ran into as well so I wanted to update it with my experience.
I was not able to locate a redistributable for 64 bit. Instead, I had to change the project I was compiling to target x86. By default the C# and VB projects have the property settings on the project set to AnyCPU. Change it to x86 and this problem goes away.
For VB.NET, right click on project and select properties, go to the compile tab. On VS 2012, you will find it on the Target CPU combo box on that screen. On VS 2008, you need to select "Advanced Compile Options..." and then you will find the Target CPU combo box.
For C#, right click on project and select properties, go to the Build tab and you will find it as "Platform target:" combo box.

Related

Is WinDbg still compatible with Windows XP?

I was looking for a debugger for Windows, other than GDB, which is freely accessible. I found WinDbg and it looks quite good so I wanted to give it a try. Now when I go to the MSDN page it offers to download the SDK for Windows 8. As this is a rather big package, I wonder if I can use this WinDbg version still for Windows XP?
Since my company still uses Windows XP for some time to come, I'm stuck with it for now. Is there another, free debugger which is user friendly?
I'm used to Visual Studio for debugging, which is quite nice. Currently I use Eclipse with GCC and GDB. GDB is good enough, but when I do some assembly I don't really like it, and all in all I don't find it very user friendly.
The latest WinDbg will work with Windows 2000 onwards and most commands work with Windows XP. There will be some that will only work with later versions, but these are documented in the included help file.
Just to ease your download pain, firstly there is the option to select what to download from MSDN, or you can just download the version you want here thanks to a kind person who is hosting the individual components.

Crystal reports database connection issues

Failed to load database information. Details: The database DLL crdb_ado.dll could not be loaded. Error in File (filename) Failed to load database information.
I am receiving this error when i try to run a crystal report from my page. on the server I have installed the CRRedist2008_x86 and the dll file is in the business objects folder, but for some reason it is still not loading. I also checked to make sure I have the msvcp60.dll which is also needed but still am unable to run the report.
The server is running Windows Server 2008, has Visual Studio 2005 installed on it (not sure if that makes any difference). The application ran fine on my local machine, but after uploading it to the server, it's not wanting to play nice.
Any suggestions/help is appreciated.
Thank You
You should get Dependency Walker and open the crdb_ado.dll to confirm all the required files are there. Although checking for msvcp60.dll is generally the right idea, I've found that people are often looking for the wrong version of those files OR that other required DLLs are also missing.
Also, be sure the redist you are using matches the version of Crystal Reports you have referenced in your project. There is a difference between using, say Crystal Reports 2008 on top of Visual Studio 2005,, versus using the BUNDLED Crystal Reports that comes with Visual Studio 2005 (Or 2008, or 2010 for that matter.).
In fact, sometimes people don't realize that their .NET projects are referencing the "comes with Visual Studio" edition of Crystal Reports because they happen to have Crystal Reports version <whatever> installed on their PC.
That said, if you are pretty confident your redist of CRRedist2008_x86 matches what you are using, I'd focus on Dependency Walker to see if it is indicating a missing required file for the crdb_ado.dll.

Crystal Reports error when deployed..Could not load file or assembly 'log4net

Please help. I have a web application that was built in VS2010 and we are using the CR plugin for 2010 and everything works perfect on our local machines. When we go to deploy the web application to Server 2008 the application runs fine until we try to get to a report. When we get to a report we receive...
Could not load file or assembly 'log4net, Version=1.2.10.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.
We have installed the CR2010 runtimes and the file log4net.dll version 1.2.10.0 is in the GAC so we are not referencing it in the application. When we add it as a reference we get this error no matter where we are in the application, not just on the report pages. Please help!
I received the same error message after accidently installing the x86 version of the crystal reports redist on a x64 machine.
Installing the correct x64 redist fixed the problem - http://downloads.businessobjects.com/akdlm/cr4vs2010/CRforVS_redist_install_64bit_13_0.zip
We just ran into the same problem and it turned out to not (in our case) be the version of the Crystal Reports redist (we installed the 32 bit versions on our 64 bit machines. The way we were able to fix the problem was to
Navigate to your virtual directory Application Pool -> Advanced Settings -> Set Enable 32-Bit Applications to True
and changed the managed pipeline mode from Classic to Integrated. After that we no longer got errors of the missing log4net dll.
We also had the same issue with the 64-bit redistributable installed. In our case, we set the "Enable 32 Bit Applications" setting to FALSE in the advanced Application Pool properties and that resolved the issue.
If you have a x86 development machine and your web server is a 64-bit machine, you may be running into the problem discussed here:
http://social.msdn.microsoft.com/Forums/en-US/vscrystalreports/thread/546059a6-7179-4027-8f16-822ac6dc189a/
Visual Studio is automatically deploying a 32-bit log4net.dll into the 64-bit web server, even if you don't have it referenced in your project. Just delete the log4net.dll from your bin directory once deployment has finished because it's not actually required by the CR runtime to work.
For me I had a VB Application project and under Compile options, I had "Any CPU" selected for Target CPU and I also had the "Prefer 32-bit" checked. When the compiled app ran on a 64 bit machine, which only had the x64 runtime installed it could crash with this error, because it tried running as a 32 bit app and wanted the 32 bit runtime. Unchecking this option and recompiling made it work correctly.
Install Crystal Reports for Visual studio Runtime engine for .NET Framework 64 bit
Solved my problems.
I have 2 NLB 2008 R2 Servers, my IISs are configured to run in x32.
In one server I have installed x64 and x32 SAP redist and I have the error, in second server only the x32 and works.
To get the first server work I uninstalled all versions and reinstalled only x32, but the server start work only after a reboot.
Bye
In my case I had the error while developing with Visual Studio 2022. I did what the other answers here say, installed Runtime 64-bit, because my machine is 64 bit, and then:
(in Visual Studio) Project Debug Properties > Web > Servers > Change Bitness to x64 (using IIS Express)

Crystal Reports in ASP.NET, language problems?

I have a bilingual ASP.NET project that includes a lot of rpt files which are Crystal Reports files. I have never really worked with these kind of things but I should now test that it's possible to deploy these in both languages and so on. By bilingual I mean that these reports should be shown in one of two langauges depending on which language is set in Control Panel. And that works if I run the application in Visual Studio (Debug -> run) but not if I deploy it.
By deploying I mean: project -> copy project, "only files needes to run this application" and copying only these files to iis catalogue. By doing this the reports are shown in language one no matter which of the languages is chosen in Control Panel.
Am I missing something crucial here?
IIS server doesn't use Control Panel language. Older versions of it use system default locale (what is set at OS install phase), newer versions allow set locale (language) in IIS options.

Detecting x86/x64 and installing correct .msi

I am finalizing an application that will soon be submitted for Windows Logo Program validation. One of the requirements is x64 compatibility. Specifically, Crystal Reports 2008 must work under x64.
My problem is that Crystal Reports basic 2008 (the one packaged with Visual Studio 2008) has no merge modules and must be installed using the provided .msi installers. They offer separate installers for x86 and x64.
So how would I detect x86 and x64 during install and then run the appropriate Crystal msi? Is this even possible without merge modules?
EDIT:
This:
IF PROCESSOR_ARCHITECTURE == x86 AND
PROCESSOR_ARCHITEW6432 NOT DEFINED THEN
// OS is 32bit
ELSE
// OS is 64bit
END IF
seems to tell me how to detect it (thanks MicSim). But how do I perform this in an MSI? Is it a custom action? And then how do I trigger different required msi's for the x32 and x64 crystal reports?
And why doesn't the x86 crystal installer work under WOW64? You have to install x64 Crystal to work with your WOW64 x86 app. Frustrating...
EDIT 2:
Okay, so detecting x86/x64 seems to be covered here. Now how about manually triggering an msi of your choosing?
The easiest way I have found to detect a 64-bit operating system is to use the VersionNT64 property. This property can be used in conditions for components or custom actions (eg. the condition Not VersionNT64 will only be true for 32-bit operating systems).
As for installing other MSI packages during your installation, that is a little trickier. Windows Installer will only allow one MSI to be running the Execute Sequence at a time. This means that you must either install your Crystal Reports MSI during the UI Sequence using a custom action (be careful if you do this, the UI Sequence is skipped if the MSI is run in silent mode), or create some kind of bootstrapper program that will run both the Crystal Reports MSI and your own in sequence.
I have never created my own bootstrapper, but InstallShield has a bootstrapper program built into their setup.exe; they call packages installed this way prerequisites.
Just googled it: If you have an MSI project you could check the properties like described here.
For further information about detecting process and OS architecture you might want to read this MSDN blog about "HOWTO: Detect Process Bitness".
You can trigger the Crystal Reports MSI with a custom action that executes [SystemFolder]msiexec. Just specify "/i [YourFolderWithCRMSI]msiname.msi" as the arguments.
According to this forum, Crystal Reports now includes a merge module for visual studio 2008.
HREF=https://smpdl.sap-ag.de/~sapidp/012002523100005986132008E/cr10_net_mm.zip
Edit (from the author): It turns out that this doesn't work for the Crystal Reports that comes bundled with Visual Studio 2008.