Crystal Reports for.Net Framework 2.0 (X86) Installation problem The user of this application is running windows Vista. As per the norm, i sent him the crystal reports for.Net Framework redistributable to install, but when he tries to install it, he recieves the following error.
Hot fix for.Net Crystal Reports 10.2.3600.0 to fix problems with sub reports running on 64 bit operating systems ISSUE: Reports which contain subreports fail with error 'Missing Parameter Value' DEPLOYMENT SERVER OS: Windows 2008 with 64 bit.Net framework 2.0 DEVELOPMENT PC: Windows XP SP3 Visual Studio 2005 Prof.Net Crystal reports 10.2.3600.0 SYMPTOM: In Crystal Reports for Visual Studio.NET 2005, a subreport link is configured between a database field on the main report to a stored procedure parameter field in a subreport. When the report is run, a dialog appears and prompts for the linked subreport parameter field. The parameter field should have been automatically populated by the main report. SOLUTION For x86 PC's: For PC's running with 32 bit, Business Objects released a Crystal Reports hot fix for Visual Studio 2005. This can be downloaded at the following link. Reference knowledge base KBase Article ID:c2018840 Download the above patch and install it on your PC.
The issue would be resolved. ISSUE for x64 PC's: However, the patch from business objects does not fix the issue for PC's with 64 bit operating system. After searching for a long time on google I presumed that a readily available installable to fix issue with.Net Crystal Reports 10.2.3600.0 to fix problems with sub reports running on 64 bit operating is not available.
SOLUTION For x64 PC's: While deploying the application you need to deploy tto things. Install the windows installer package package for 64 bit PC's named 'CRRedist2005_X64'.
This package is located on your development PC which has visual studio 2005 installed. This can be located at the following location: C: Program Files Microsoft Visual Studio 8 Crystal Reports CRRedist X64 2. You need to create an additional Crystal Reports Runtime Package.
Instrument tuning software. The steps to create this additional Crystal Reports Runtime Package can be found at following URL The creation of this package includes 1 important step. Make sure that you checked 'X64 Compilers and Tools' while installing Visual Studio 2005.
In my case I hadn't checked this checkbox while installing visual studio 2005, so I had to reinstall visual studio 2005 to create this deployment package. After following the steps mentioned at the above link, I was able to create a deployable package successfully. After installing this package the issue was resolved.
I wonder why Business Objects didn't make a hot fix available for PC's with x64 like they did for x86 and instead choose to make available steps to create the package. Anyways the issue stands resolved and that's what matters.
I have a PC Windows Application that I deploy with ClickOnce. My app started out as a small app with Micrsoft Access as the database, so that users didn't have to install a big database package when they first use it. Because of the Access Database, I have it set to compile the app to x86 (otherwise when it's installed on an x64 machine it can't find the Jet Engine.) The problem I'm having now is that my application also uses Crystal Reports.
I use the Prerequisites window on the Publish Tab of my project's properties to have this included when the user installs. When a user with an x64 machine installs my application, it installs Crystal Reports for x64. When they run the app (which is compiled for x86) it looks for the Crystal Reports x86, can't find it, and blows up with the message 'An error has occurred while attempting to load the Crystal Reports runtime' etc. If the user manually installs the x86 version of Crystal Reports the application then works just fine. So my question is.is there anyway to force an x64 machine to install the x86 version of Crystal Reports?and No, I cannot change it to a different database. The app started out small but has grown quite large and changing the database would be too painful at this point.
When answering a question please: • Read the question carefully. • Understand that English isn't everyone's first language so be lenient of bad spelling and grammar. • If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome. • Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.
Let's work to help developers, not make them feel stupid.