unable to load crystal report in windows server 2012 - crystal-reports

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

Related

Will SSRS reports built with Report builder 3.0 run on SSRS 2019?

I have a report that was built be a former colleague using Report Builder 3.0. The reports are running nicely on SSRS 2008 R2. We are provisioning a new server since loading the report via HTTPS is interfering with IIS using HTTPS on the same machine.
When we provision the virtual server, we will most likely use the 2019 version of SSRS to host the report as I have a license for it. My question is, will reports built using report builder 3.0 load correctly in the new environment or does the report need to be upgraded to a newer version and if so, how would I go about that?
I'm not super familiar with building the reports. I did manage to update the report to include a few new fields in the database earlier this year. Additionally, How would I go about finding the report on the server so I could move it to the new server?

SAP Crystal Reports for Visual Studio 2013 do not work in IIS 7.5

I am using Crystal Reports for Visual Studio 2013. The reports work fine on my local computer and in Visual Studio on the production server.
When I deploy them in IIS 7.5 I am getting the following error:
Failed to open the connection. ReportName
3400_4400_{A861BA52-167D-4EAF-AAAF-32B2FB34FFAA}.rpt
Operating System: Windows Server 2008 R2 Enterprise;
System Type: 64-bit Operating System;
Database: MySQL;
I copied the aspnet_clients folder in the wwwroot folder and in the application folder.
Any help would be appreciated.
Thank you.
There is 2 things which may cause this issue,
Are you installed the Crystal report runtime? if no, then here is
link1, link2. You can choose 64 bit option.
If you installed CR-runtime, then crystal report does not have connect to sqlserver. So for this, if you able to check your local crystal report with prod sqlconnection, check that and still you have issue, means you are not give sql server credential to crystal report at run-time. Check this link.
Crystal Report throws 'Failed to open the connection.' only on postback
http://www.codeproject.com/Questions/667950/crystal-reports-connection-to-sql-server-database
http://aspalliance.com/532_Understanding_the_Login_Failed_Error_in_Crystal_Reports.3
I have some updates!!! I can't believe this was the issue....so frustrating!!!...
On my production server I only created a User DNS...which worked fine with Visual Studio...but not with IIS. After I created a System DNS the report worked fine in IIS as well...

How to run Visual Studio 2005 Crystal Reports app on Windows 8.1 - says can't find CR runtime

I have a VS2005 forms app that uses Crystal Reports (built on a Windows Server 2003 system). I can run the app in Windows 8.1, but when I try to open a report, I get an error saying it cannot find the Crystal Reports runtime. I've installed the CR2005_x86 runtime, and the C++2005 runtime for good measure.
I've also installed VS2005 on the Win 8.1 machine (with its SP1 and SP1 for Vista), can open/edit the reports within VS2005, and can build the app, but this too says it cannot find the CR runtime.
In both cases running with Admin priviledges.
Can anyone help? What am I missing or do I need to upgrade (eg to VS2012)?
Regards,
Tom

Crystal Reports XI compatibility with Windows 2012

I have a Crystal Reports application that is hosted in IIS on a windows 2003 32 bit Server. The Crystal reports version in use is Crystal Reports XI Release 2 SP 2.
We are migrating our applications to Windows 2012 64 Bit Servers. I am not sure if this version will work support on 2012 server.
Can anyone please tell me if it will work on 2012? If not, is there any workaround?
While it's not supported, you may have luck with updating your Crystal to service pack 6.
See this page for links/details on doing so:
https://blogs.sap.com/2011/06/07/where-did-all-the-crystal-reports-xi-r1-and-r2-fixes-go/
We faced two scenarios using Windows 2012 64 bit Server and Crystal Reports 10.2.0.
In the first one, everything is working fine until now.
In a second one, I was working fine too, except when someone would try to save the report as an Excel file. It would crash the IIS ASP.Net process. Something on KERNEL32.dll, but I don't have the full message in English to post.
We tried to format the server and reinstall Windows 2012 Server, but it was useless.
We researched about it and all the references and possible solutions ended up at an orientation to install Crystal Reports 13.0.12.
We installed the newer version and everything is working fine.
Please note the the version numbers are a bit confusing. I always check the version number in windows "programs and resources".

VS 2010, SAP Crystal Reports, Windows Server 2008

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.