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...
Related
I have a Crystal 8.5 Report in a VB6 application.
The crystal report not run on client machine and get error
"Run-time error '713' Application-defined or object-defined error".
But the crystal report work on programmer machine.
how to run the crystal report successfully on client machine ?
With Thanks.
Crystal Reports is a separate control (OCX) file that needs to be packaged together with your application (EXE) because your client doesn't have it installed on his machine. That's why you need to create an installation package.
Have you tried packaging the application in the form of an installation kit with the "Package and Deployment Wizard" in your Visual Studio installation? That should include all dependencies necessary to run on client machines.
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
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
Failed to load database information. Details: The database DLL crdb_ado.dll could not be loaded. Error in File (filename) Failed to load database information.
I am receiving this error when i try to run a crystal report from my page. on the server I have installed the CRRedist2008_x86 and the dll file is in the business objects folder, but for some reason it is still not loading. I also checked to make sure I have the msvcp60.dll which is also needed but still am unable to run the report.
The server is running Windows Server 2008, has Visual Studio 2005 installed on it (not sure if that makes any difference). The application ran fine on my local machine, but after uploading it to the server, it's not wanting to play nice.
Any suggestions/help is appreciated.
Thank You
You should get Dependency Walker and open the crdb_ado.dll to confirm all the required files are there. Although checking for msvcp60.dll is generally the right idea, I've found that people are often looking for the wrong version of those files OR that other required DLLs are also missing.
Also, be sure the redist you are using matches the version of Crystal Reports you have referenced in your project. There is a difference between using, say Crystal Reports 2008 on top of Visual Studio 2005,, versus using the BUNDLED Crystal Reports that comes with Visual Studio 2005 (Or 2008, or 2010 for that matter.).
In fact, sometimes people don't realize that their .NET projects are referencing the "comes with Visual Studio" edition of Crystal Reports because they happen to have Crystal Reports version <whatever> installed on their PC.
That said, if you are pretty confident your redist of CRRedist2008_x86 matches what you are using, I'd focus on Dependency Walker to see if it is indicating a missing required file for the crdb_ado.dll.
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.