After flash EOL, we have upgraded SAP Crystal Reports, version for Eclipse software and lib, from 12 to latest CR version. Reports started working fine in HTML but there are few reports with multipage and large data where we are getting Java assertion error.
07:29:24,446 ERROR [][JRCCommunicationAdapter] (catalina-exec-30) detected an exception: java.lang.AssertionError.
Related
Error : crystal report load fail(after long time of loading)
I developed c# app contain sap crystal report and it doesn't work on another machine ..
Single tip I installed sap crystal report runtime 32bit
Tools I used in development :
.netframework 4
Crystal report runtime 64bit
Sql server 2014
Thank you I hope you will help me !
I suggest add your report ro your current working project if you are using vs 2010 :
Some errors comes up load report failed:
First: check report path.
Secode: crystal report need to log in into your database working.
I am getting an error while importing a BIRT report to Maximo.
The error is
bmxaa5457e - The report import process failed. Verify the specified information is correct before proceeding again.
Note that report is correct, I got a correct preview in Eclipse. There is nothing like images or other properties related to report.
This didn't work. Java 2 security checkbox is also unchecked.
What version of Eclipse BIRT are you using to design the reports and what version of BIRT does your Maximo support? The issue might be that you're creating reports in a newer version than your Maximo supports.
I need help I developed a Web site and added SAP Crystal reports when run it from VS 2010 in debugging mode all reports works fine, but when I try to run it from IIS with System I.P and its shows nothing no error and crystal reports shows no Reports even no blank report. . is there any issue running SAP Crystal Reports in production environment.
Take a look at crystal reports viewer does not load when asp.net application is deployed to server
Often an issue with the run times not being installed or incorrect versions etc.
I am getting the following error when we add the Crystal Report Engine dll. The Crystal Report version we are using is V9.2. Can I get the correct code to open Crystal Report RPT file in Crystal Report Viewer?
'C:\WINDOWS\assembly\GAC\CrystalDecisions.CrystalReports.Engine\9.2.3300.0__692fbea5521e1304\CrystalDecisions.CrystalReports.Engine.dll' is attempting managed execution inside OS Loader lock. Do not attempt
to run managed code inside a DllMain or image initialization function
since doing so can cause the application to hang.
In application, if user tries to open a crystal report file. The PF Usgae goes high and Server almost hangs. Is the above error causing the server to Hang?
To solve this problem I had to install the Crystal Report Runtime Engine for .NET Framework 4.0, on our server. The Engine was downloaded from link: http://businessobjects.com/jump/xi/crvs2010/.
While stepping through the code in debug mode in Visual Studio 2010 the message above was displayed. I supressed it in Visual Studio 2010. Under the menu
Debug > Exceptions > Managed Debugging Assistants
I then located LoaderLock and unchecked the Thrown checkbox.
I have a desktop application that was migrated from .Net 1.0 to .Net 4.0. The application is using Crystal Reports and ttx files as the data definition files. The actual database queries happens in business objects and the data are set using SetDataSource() method.
After I upgraded this to .Net 4.0 (and Crystal Reports for Visual Studio 2010, version 13), the reports still working great on my developer workstation. But when I installed the application on the test machines I started getting errors like this:
Error in File temp_****{****}.rpt: Failed to load database information.
Where the asterics signify some kind of GUIDs.
The odd thing is that the reports that I did not touch continue to work. Only the reports where I had to update the data source (TTX file) generate this error.
I am also getting this error:
The keycode assembly, BusinessObjects.Licensing.KeycodeDecoder.dll, cannot be loaded.
but I do not know if this is related.
The Keycoder error is not the problem. That is currently a warning message that seems to have no effect on anything (as best I can tell).
Don't be confused by the GUID stuff either. It's just a temp name that Crystal gives the report object.
The real error there is simply "failed to load database information". Something in your TTX update is at fault.
You might try running the report in Crystal 2008 on the machine giving you the problem. Your report is out-of-sync with the TTX file.