I used crystal Report 2008 in visual studio 2008(window Project) run on windows 8 64 bit But when I try to use the report, I get the following error at runntime: Crystal Reports: An error has occurred while attempting to load the Crystal Reports runtime. Either the Crystal Reports registry key permissions are insufficient, or the Crystal Reports runtime is not installed correctly.

Apr 06, 2010  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. Currently, there are only two versions of Crystal Reports with native 64 bit runtime (CR 10.5 and CR 10.2). Crystal Reports XI release 2 (version 11.5) and Crystal Reports 2008 (version 12.1.x) support 64 bit Operating systems, but in a 32 bit mode only.V. The last poets this is madness rar file free.

Please install the appropriate Crystal Reports redistributable (CRRedist*.msi) containing the correct version of the Crystal Reports runtime (x86, x64, or Itanium) required. Now i have the solution. We already follow the steps suggested: When compiling the application in Visual Studio.NET 2008 you will need to force it to 32 bit mode. You can do this by right-clicking the project name in the Solution Explorer and select Properties.

For VB.NET Click Compile, then Advanced Compile Options. For the Target CPU drop down box, change it from 'AnyCPU' to 'x86' then click OK. For C#.NET Click Build and change the Platform Target option from 'Any CPU' to 'x86'. You should then be able to run the application on a 64 bit OS without error. See more:http://dotnetfish.blogspot.com/2010/02/either-crystal-reports-registry-key.html. 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.