A document processed by the JRC engine cannot be opened in the C++ stack

Question

I have created a crystal report in vs2010 with .net4.0. when I publish the website it throws the error \"A document processed by the JRC engine cannot be opened in C++ stack

Answer 1

copy and paste the folder (aspnet_client) from the (C:\inetpub\wwwroot) to the website folder and make sure that the .rpt file is in the same folder

Answer 2

this work for me

1. Right click the Rpt file.
2. Choose the properties

3. Changed

   a. Build Action as "Content"

   b. Copy to Output Directory as "Do not Copy"

   c. Put Empty for Custom Tool and Custom Tool Namespace

Answer 3

Making sure the file path is correct like @serop mentioned. Also i have noticed where reports folder wouldn't get published. So had to manually publish the report folder.

Answer 4

Just copy the .rpt file (crystl report template ) from local machine to specific server/machine's folder and I am prey sure you can run resolve the issue CrystalDecisions.Shared.CrystalReportsException: Load report failed.

For me it worked well and no error on server side. My application is able to store pdf file to share path according the code.

Answer 5

Found out the solution, I was First using Visual Studio 2005 with its own crystal report and then i upraded to VS2010 with seperate crystal report which i downloaded from SAP. I researched and found from SAP:

As each version of Crystal Reports has its' own specific runtime which must be correctly deployed, it is critical that the deployed runtime be in agreement with the Crystal Reports assemblies for Visual Studio .NET referenced in your project.

so i uninstaller pervious version and used only one version and it worked. :) thanks ta.speot.is for your concern. It was never a coding problem.

Answer 6

This just happened to me and after hours of headache I found it was a file permissions issue. For some reason when copying from our CR dev server to the shared custom .rpt directory the permissions on the file were all jacked up and I had to add permissions for several user groups back to the file.