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.
Related
I have one application installer that uses crystal report for reporting. However since the installer does not have any crystal report related dll/ocx or other files, I am not able to run the application.
Can you please tell all the dependency files for Crystal Report ? I already tried to copy over Crpe32.dll, Crystal32.ocx but no success.
Please advise.
Thanks,
Anurag
You can download the run time for crystal report from the SAP website and run it.
Crystal Reports VS 2008
Crystal Reports VS 2005 & 2008
I have created a web application .net 2008 with crystal report. I have deployed it in windows server 2012 64 bit OS. The server is installed with 3.5 and 4.0 .net frame work. The problem is, the crystal report is not displayed in the web page. It doesn't throw any error.
Thanks in advance.
In windows server 2012 it runs IIS 8. Previous versions of crystal report doesnt support IIS8. For running Crystal report for IIS 8 you have to install new
crystal report*(v. 13.0.6.x)*
on your win server machine. Please check following link for downloading crystal report.
http://scn.sap.com/docs/DOC-7824
See below articles.
http://scn.sap.com/community/crystal-reports-for-visual-studio/blog/2012/10/16/report-appears-blank-in-browser-after-deploying-a-crystal-reportsnet-web-application
Also, make sure you are using a supported browser version.
See supported platforms for CR for VS developer version.
http://scn.sap.com/docs/DOC-21990
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 am developing a win application ( in .net 2005 ) in which i have to use crystal reports. But now it generates crystal query engine. Then I have to reinstall .net. Is there any workaround for this
This depends on the version of Crystal Reports you are using, but you might make sure that crqe.dll is properly registered on your machine by using regsvr32. Also, if you ever had a previous version of Crystal Reports on this computer, the problem could also stem from conflicting DLL version.