Failed to open the connection, when view returns no data.

Hi Guys,
I'm having a minor issue.
I'm running a report in the crystalreportsviewer in
The report is retrieving it's data from a view.
The report also has a subreport with an overview with totals, using the same view and the same parameters as the primary report.
Now everything is working fine in a filled database.
But when the view does not return any data, i get the following error:
Failed to open the connection. Failed to open the connection. Details:
[Database Vendor Code: 53 ] Failed to open the connection. Details:
[Database Vendor Code: 53 ] Failed to open the connection.
Freight_Charges_By_Branch_By_Period_By_Customer {9D0460D7-5C9E-  4FD5-B190-AFD41693A143}.rpt
Can anyone please help me with this problem.
Thanks in advance!
Regards William

Lot of important info missing here:
1) What version of CR?
2) What CR updates have you applied?
3) What version of .NET?
4) Is this on your dev box or after you deploy?
5) Have you looked up error code 53 for your database? (This is the error code CR engine is simply passing through from the db client)
6) What is the database?
7) What connection method are you using?
8) Depending on the version of CR, can you run this report in the CR designer?
9) Copy and paste the code used to run the report.
Follow us on Twitter

Similar Messages

  • Error: Failed to open the connection when opening Crystal Report in CMC or

    Hello all,
    I am getting theError: Failed to open the connection when opening Crystal Report in CMC or Infoview
    with access database as the datasource which is in the network drive.

    Hi Sonali,
    This is because Crystal Reports does not recognize database connection from share drive
    1. Save the database locally on server machine
    2. Create a new database on server and link the new database with the database on Network.
    Steps to link the database.
    1.Create a new test database on server.
    2. Go to File --> Get External Data --> Link tables | Select the database on Network Drive.
    3. Select all the tables from the database.
    4. Save the Database  e.g. Test.mdb.
    5. Create an ODBC Connection on server machine, with the same name as on client machine using test.mdb database.
    Note: Click on Advanced button, enter the default user id and password for the odbc connection, it is not mandatory to give Login Name and Password, only if the user id and password are given then we need to provide the same user id and password in the CMC database configuration.
    6. Create a report using this ODBC connection, and save the report to Enterprise.

  • Failed to open the connection. Error in the Designer when copying ...

    I have two different systems I am developing an application on.
    I copy the entire directory from one system to the other. Both systems have the same environment:
    Visual Studio 2010
    Crystal Reports for Visual Studio 2010 (the production release, or I think it is the vesion is is the version on the assemblies)
    SQL 2008 R2
    Today, I started adding Crystal reports to this VS solution. I have a reportdriver class that exports all the reports to an HTTP Stream, but we can sit that aside for now. The problem I am having is strictly with the integrated designer.
    I have a bunch of existing reports written for an old Sybase databse. I have ported them to SQL and the table structure matches. I simply add the report to my project, point it to the new datasource (using "Set Datasource Location" - OLE ADO SQL) and then preview the report to be sure it runs.
    I am just using "localhost" as my server name for the OLE connection so theory... don't have to change the data source to view it on the other system. Both systems have SQL 2008 R2 installed locally. For my login credentials, I use SQL Security and use the same database login/password on both development machines andthe production server.
    Today, I copied my entire project to the other PC (as I do almost every day).. When I open any of the reports (in VS) and try to preview them I get:
    Failed to open the connection.
    Details: ADO Error Code: 0x80004005
    Source: Microsoft OLE DB Provide for SQL Server
    Description: [DBNETLIB][ConnectionOpen (Connect().]SQL Server does not exist or access denied.
    SQL State: 08001
    Native Error: 17 [Database Vendor Code: 17]
    I can only guess that I am using two different OLE ADO drivers on the two systems or there is something embedded in the rport or somewhere in my solution that "knows" I am not really on the same system that I initially set them up on and previewd them with.
    Am I on the right track? Any idea how I can fix this? Obviously, I don't want to have to setup the datasource for every report in my application (if I do that, the report works) when I copy it from the development to the production server.
    I am in a real bind here and under a fast aproaching deadline. Any help is much appreciated!!!

    Don't use localhost as your server name. It's a reserved name and should not be used in code.
    Try this also [Kbase |] SAP Note 1553469 - How to enable Database logging in Crystal Reports for Visual Studio 2010
    Edited by: Don Williams on Jan 30, 2011 6:02 AM

  • Failed to open the connection error using Business View OLE DB

    I have a Crystal Report built on a Business View with the db being accessed by an OLE driver.  Everything works fine using Crystal Designer, but when I try to access it through BOE I get the "Failed to open the connection" error.  I have the ole drivers installed on the server.
    We are on BOE 12.1.0.
    The db is IBM as400.

    Ok so I spent the day trying to find the differences between the working and the non-working application. I began by adding code one piece at a time to the working application. The goal was to try and get it to break on the deployment server. I found the lines of code that is causing the break on the deployment server. Here it is:
        private void setReportParameters()
                crystalReportDocument.SetParameterValue(0, reportUserName.Value);
                crystalReportDocument.SetParameterValue(1, reportArea.Value);
                crystalReportDocument.SetParameterValue(2, reportCDR.SelectedValue);
                crystalReportDocument.SetParameterValue(3, reportStatus.Value);
            catch (Exception ex)
                throw ex;
    This sub-routine is called from my button click code and is used to set the parameters for the report. Once I added this to the working application it broke also. My goal here is to send the parameters to the report from a form the user is filling out. Please keep in mind this code works in Visual Studio 2005 and my local IIS server running on my development machine. It breaks on the target deployment server
    The code broke on reports with sub-reports as well as report with no sub-reports. As soon as it was added and deployed the application through the "Failed to open the connection" error.

  • "Failed to open the connection" problem related to multiple tables in the report?

    Post Author: Gadow
    CA Forum: Data Connectivity and SQL
    System specifics:
    Web environment using ASP.Net 2.0 (from Visual Studio 2005 Professional)
    Crystal Reports 2008, v., Full
    We have set up the following method for displaying reports via our website:
    User is sent to a report-specific page. The user is given some filtering options specific to the report that will be viewed. When the user has specified the data filters, the user clicks a button.
    The page wraps up the report parameters -- selection query, formula values, report location, the name to be displayed, etc. -- into a class which gets put into the Session object.
    The page redirects to DisplayReport.aspx. ALL reports redirect to this page.
    DisplayReport.aspx retrieves the report parameters from Session. A ReportDocument object is created and loaded, then set with the data from the parameters class.
    A ConnectionInfo object is created and set with the relevant log on credentials. All of the reports draw from the same database, so the connection information is hard-coded as the same for all reports. The page then iterates through all of the tables in the Database.Tables collection of the ReportDocument and calls ApplyLogOnInfo to each table using the ConnectionInfo object.
    The page is rendered and the user gets the filtered report.
    We currently have seven reports. Five reports work fine and display the correctly filtered data with no error messages. Two reports generate a Failed to open the connection error and do not display. I have verified that the queries being sent to DisplayReport.aspx are valid, and as I said the connection information itself is hard-coded in the one page that displays the reports and this is identical to all reports.
    The five reports that do work all have a single data table, either an actual database table or a single view. The two reports that do not work all have multiple tables. As far as I can tell, this is the only difference between the sets; all seven reports are based on the same DSN and I have verified the database on all of the reports. All of the reports were written using Crystal Reports 8, and all of the reports display fine in a Windows app I wrote some years ago using Crystal Reports 8. Again, the only difference between those reports that do work and those that do not is the number of tables used in the report: one table or view in the reports that display, more than one table (tables only, none use views) in the reports that do not display.
    As for the code I am using, below are the relevant methods. The function MakeConnectionInfo simply parses out the components of a standard SQL connection string into a ConnectionInfo object. DisplayedReport is the ID of the CrystalReportViewer on the page.Protected Sub Page_Init(ByVal sender As Object, ByVal e As System.EventArgs)
            Dim o As Object = Session("ReportParams")
            Dim ReportURL As String = ""
            'Verify that there is a ReportParameters object
            If o Is Nothing OrElse o.GetType IsNot GetType(ReportParameters) Then 'Redirect to the error page
            End If
            ReportParams = CType(o, ReportParameters)
            'Verify that the report exists
            ReportURL = "/Reports/ReportFiles/" + ReportParams.ReportName
            ReportPath = Server.MapPath(ReportURL)
            If Not File.Exists(ReportPath) Then
                Response.Redirect("/errors/MissingReport.aspx?Report=" + ReportParams.ReportTitle)
            End If
        End Sub
        Protected Sub InitializeReport()
            Dim RD As New ReportDocument
            Dim CI As ConnectionInfo = MakeConnectionInfo(DB_Bonus)
            Dim RPF As CrystalDecisions.Shared.ParameterField = Nothing
            If ReportParams.SelectString <> "" Then
                Dim Adapt As New SqlDataAdapter(ReportParams.SelectString, DB_Bonus)
                Dim DS As New Data.DataSet
            End If
            For Each kvp As KeyValuePair(Of String, String) In ReportParams.Formulas
                Dim FFD As FormulaFieldDefinition = Nothing
                    FFD = RD.DataDefinition.FormulaFields(kvp.Key)
                Catch ex As Exception
                    'Do nothing
                End Try
                If FFD IsNot Nothing Then
                    Select Case FFD.ValueType
                        Case FieldValueType.DateField, FieldValueType.DateTimeField
                            If IsDate(kvp.Value) Then
                                FFD.Text = String.Format("Date()", Convert.ToDateTime(kvp.Value).ToString("yyyy, MM, dd"))
                                FFD.Text = "Date(1960, 01, 01)"
                            End If
                        Case FieldValueType.StringField
                            FFD.Text = String.Format("""""", kvp.Value)
                        Case Else
                            'For now, treat these as if they were strings. If things blow up here,
                            'we will need to add the appropriate formatting for the field type.
                            FFD.Text = String.Format("""""", kvp.Value)
                    End Select
                End If
            For Each T As CrystalDecisions.CrystalReports.Engine.Table In RD.Database.Tables
                Dim TLI As TableLogOnInfo = T.LogOnInfo
                TLI.ConnectionInfo = CI
            DisplayedReport.ReportSource = RD
        End Sub
    Does this approach not work with reports containing multiple tables, or is there something I'm missing? Any meaningful suggestions would be much appreciated.

    Dear Dixit,
    Please refer to the Crystal report landing page to get the details
    information about the support for crystal report issues.
    Please use the following thread to post your questions related to
    crystal report.
    SAP Business One and Crystal Reports
    Rakesh Pati
    SAP Business One Forum Team.

  • Crystal Server 2011 "Failed to open the connection" with 32 & 64 bit drivers are loaded

    Brand new installation of Crystal Reports Server 2011 with CR Developer 2011 as well.  Downloaded new Postgres and MySQL drivers for both the 32 and 64 bit ODBC definitions.  Created a new report on the server to eliminate any migration driver incompatibility issues.  Reports run fine in Developer but give the same "Failed to open the connection." 
    and still problems running the reports  If I Save Data with the reports, I can click View to see the data, but they will not refresh.
    All the articles I'm finding online seem to point to the issue with needing 32 & 64 bit drivers, but I've loaded both and built my ODBC connections with the 32 drivers in the SysWOW64 folder.
    Logged in as Administrator.  Any thoughts out there?  Are there some new security measures?
    Thanks in advance ...

    Yes, Designer and CRS are on the same machine.
    Good catch with the 5.1 driver.  I loaded up the mysql-connector-odbc-5.1.13-win32 driver and used that.  It alone failed when I made the ODBC connection with it.  I see on the CRS 2011 Feature Pack 3 .pdf file that it says "Only 64-bit database connector middleware is supported" ... I downloaded the other mysql-connector-odbc-5.1.13-winx64 64bit file, but teh .msi and .zip versions failed on the load.  Do I need that if it says that or should the first one be enough?
    I've been trying to use a normal User DSN, no?  Apparently I don't have access as a machine Administrator to do it as I get "You are logged on with non-Administrative privileges.  System DSNs could not be created or modified."  Having our server guys get that straightened out and we'll see.  Had not heard of that actually but will give it a go.
    You say I should create the DSN entries in the 64 bit version of the ODBC Data Source Administrator ... located in the system32 folder, not the SysWOW64 folder, where the 32 bit drivers are found, yes?  Isn't that the "wrong" location to use I've been reading?  Or are System DSNs different from a User DSN?
    BIG thanks for the replies.  I owe you beers!!!!!

  • CRS 2008 - Failed to open the connection.

    I just recently installed the evaluation of CRS 2008 onto my server. I can access every function in CMC and can see all reports that were published in InfoView. However, when I attempt to view a report, I get an error that states "Failed to open the connection. <<Report_Name.rpt>> "
    The server is a Windows 2003 R2 machine, with IIS 6.0 installed.
    During installation, I had checked both IIS & Java (along with the installation of Tomcat 5.5)
    I also installed Crystal Reports 2008, and all reports work perfectly in the developer. The database that the reports pulls data from is a Progress 9.1D database. Could the database be an issue even though I am connecting through an ODBC?

    Yes, the DSN is a system DSN and is located on the server that Crystal Reports Server 2008 is installed on. The Progress driver is also loaded. That driver is the MERANT 3.60 32-bit Progress SQL92 v9.1D.
    When I run the diagnostics, Web Intelligence Tier fails with the following error:
    "Error creating Dataproviders. null - Error viewing Web Intelligence Document. Cannot initialize Report Engine server. (Error: RWI 00226) - Scheduling Web Intelligence Report failed. --Document: " Diagnostic Web Intelligence Document Test" not found."
    I'm hoping this can shed some light on what is wrong.

  • Infoviewer Error - Failed to open the connection.

    I get the below error when tring to view a report from infoviewer?
    Failed to open the connection. Products.rpt Details: [Database Vendor Code: 12154 ]
    Also where can i find the log files for CMC and infoviewer?
    Thanks in advance

    Hi! I'm getting a similar error.
    Re: 08004:oracleodbcoraora-12154: TNS: could not resolve the connect ....
    Posted: Aug 22, 2011 5:56 PM in response to: John Fleming
    Edit Reply
    I am receiving a similar error.
    Failed to open the connection.
    Details: 08004:OracleODBCOraORA-12154: TNS:could not resolve the connect identifier specified Database Vendor Code: 12154
    I've seen all sorts of discussion on the intertubes about possible fixes however, none stated are practical or they do not address my error specifically. I've exhausted resources on the net as well as those available to me.
    I'm currently running SAP Crystal Reports 2011 on WIN7 64bit and using Oracle in OraClient 10g_home1.
    Please let me know what insight you have. I cannot roll back to previous versions of Windows nor less encryption.
    Thank you for your time.
    Thank you, again, for your time.
    Jeff Embree.

  • CrystalReportViewer Failed to Open the connection Unable to retrieve Object

    I am getting the following Error on trying to view a report in the CMC and the Infoview.
    Failed to Open the connection. ReportName
    Unable to retrieve Object.
    Failed to open the connection. ReportName
    I have recently re-installed Crystal Reports Server XI  on a server after a disk failure. I had a backup of my CMS database. I reinstalled the Crystal Servwer without atttaching this database, however crystal did not create a new db so I attached my old one.
    I have deleted all my old ODBC connections and recreated them with new names and then reconnected my reports in Crystal Reports XI using the "Set Datasource Location" option and the report works fine.But as soon as I try to view it after uploading it as an object onto the server, I get the above error.
    Any help would be appreciated.

    I am tagging into this unanswered question as well because I think I have a similar issue.  In my case I have a report which runs correctly in Crystal Reports designer but when I move it to the scheduler it fails on a "Failed to connect" to the report.  In have used "Set data location" to no avail.  When I go to Admin Tools and look at the complete list of datasources for all my reports this particular datasource is listed twice.  The group of reports under one of the datasources works correctly.  The reports listed under the second datasource all fail.  The two datsources are spelled exactly the same and when I sompare the database details for a successfull and a failing report using this datasource they are the same (in the console and in infoview).
    I have also checked the ODBC connections on the Crystalserver and there is only one occureence.
    Any ideas?

  • CR2008:Failed to open the connection. Failed to open the connection. Report

    I've just upgraded from Crystal XI R2 to Crystal 2008. All my reports open happily in Crystal 2008. I have also deployed the Crystal 2008 runtime to a Windows 2003 SP2 R2 server running ASP.NET 1 and ASP.NET 2. Before the Crystal 2008 runtime was installed on top of the already present Crystal XI R2 Runtime I could view RPT files via the .NET report viewer (version XI). Now that Crystal 2008 runtime is installed I receive an error message when I try to view the reports, again, via the .NET report viewer (version 12), although no code has changed apart from all references changed from XI to 2008.
    Code is:
    CrystalDecisions.CrystalReports.Engine.ReportDocument oReportDocument = new CrystalDecisions.CrystalReports.Engine.ReportDocument();
    Tables oTables = oReportDocument.Database.Tables;
                   foreach (CrystalDecisions.CrystalReports.Engine.Table oTable in oTables)
                        TableLogOnInfo crTableLogOnInfo = oTable.LogOnInfo;
                        crTableLogOnInfo.ConnectionInfo.IntegratedSecurity = true;
                        crTableLogOnInfo.ConnectionInfo.DatabaseName = "DB" ;
                        crTableLogOnInfo.ConnectionInfo.ServerName = "server" ;
    CrystalReportViewer1.ReportSource = oReportDocument;
    Error message is: 'Failed to open the connection. Failed to open the connection'.
    Any help would be great.

    You are correct in that there are no database connectivity changes in CR 2008.
    If you do not have SP0 for CR 2008, download it from here:
    If that does not help, I'd like to check if the correct dlls are loading when using CR 2008. To do that, download the modules utility from here:
    Then do the following:
    1) unzip the download
    2) Run the app with the CR 2008 references
    3) get the error. leave the error on the screen
    4) Start modules
    5) Go to the File menu, select New List -> Memory Modules
    6) Expand "By process"
    7) Find the app exe (or the .NET dev env)
    8) Click on that
    9) Go to the View menu and select Details
    10) Look to see if there are any dlls loading form the CR XI r2 directory (c:\Program files\Business Objects\Common\3.5\bin)

  • Failed to open the connection on CR Server 2008 .

    1. I used trial version of CR Server 2008 V1 SP3, I upload a rtp file into this server and try to view. but after parameters input, I got "Failed to open the connection".  this rpt work very will on my CR Server XI version.
    2. on this new CR server, this rpt file database configuration, I used "use original database logon information from report" and select "Prompt the user for database logon".
    3. on my old CR server, when I view this RPT, system will prompt a logon information to let me logon DB, but on new server, system didn't show the DB logon screen before input parameter.
      On client PC, I has set a system DSN when I created this rpt file. Does anybody can help ?

    You may check these threads:
    Re: Crystal Reports Add-on error on workstations
    Crystal Report Add On - Connection error.
    Crystal Reports install errors on workstation

  • Failed to open the connection: Error Code 17

    Here's an odd one.
    VB.NET Winform
    Visual Studio 2008
    .NET framework 2.0
    Crystal Reports 2008
    ODBC connection
    I have three reports, living in the same directory. They are essentially identical, except for the grouping. All three run successfully within Crystal reports.
    From a report viewer Winform in VS, two of the three run. As I am dealing with a small data set, the reports render quickly. On the third report, There is a long pause when the report viewer form opens, then I finally get an error:
    "Failed to open the connection.
    Details: [Database Vendor Code: 17]
    Failed to open the connection.
    CallReportByExtension 58F5C135-7BA3-4215-898A-DADA6C7DAD9C.rpt
    Details:[Database Vendor Code: 17]
    I was initially getting similar errors on all three reports, before changing the datasource location to my ODBC connection. I have double-checked the location, verified the database, etc.
    What am I doing wrong? I can provide the VB code if requested, but since the other two reports work properly, I doubt it's code. I do know that I am passing the report name and path correctly to the report viewer form.
    As I am about to kick my monitor through the window and become a street denizen, I would greatly appreciate any help that would be offered.
    Mike Beckner

    Thanks for the reply. This code works...two of the three reports work.
    Imports CrystalDecisions.CrystalReports.Engine
    Imports CrystalDecisions.Shared
    Public Class frmReportViewer
        Dim m_datStartDate As Date
        Dim m_datEndDate As Date
        Dim m_strReportPath As String
        Dim m_strReportName As String
        Dim m_strStaticPath As String = "c:\Program Files\CallReportViewer\Reports\"
        Dim crConnectionInfo As New ConnectionInfo
       *****Omitting property declarations--I assign the report name and path via these properties. *****
        Private Sub frmReportViewer_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
        End Sub
        Public Sub LoadReport()
            Dim crReportDocument As New ReportDocument
            Dim crTableLogonInfo As New TableLogOnInfo
            Dim crTables As Tables
            Dim crTable As Table
                With crConnectionInfo
                    .ServerName = "CallWhereData"
                    .DatabaseName = "CallWhereData"
                    .UserID = "MyID"
                    .Password = "MyPassword"
                End With
                Me.Text = m_strReportName
                crReportDocument.Load(m_strStaticPath & m_strReportPath)
                crReportDocument.SetParameterValue("1StartDate", m_datStartDate)
                crReportDocument.SetParameterValue("2EndDate", m_datEndDate)
                crTables = crReportDocument.Database.Tables
                For Each crTable In crTables
                    crTableLogonInfo = crTable.LogOnInfo
                    crTableLogonInfo.ConnectionInfo = crConnectionInfo
                CrystalReportViewer1.Dock = DockStyle.Fill
                CrystalReportViewer1.ReportSource = crReportDocument
            Catch ex As Exception
            End Try
        End Sub
    End Class

  • Failed to open the connection.  ReportName

    Post Author: mhortman
    CA Forum: General
    I just installed CR Server, and am trying to run my first report, and this is the error message that comes up when I try to preview it:In the Crystal report Viewer:Failed to open the connection.
    Yesterday Sales
    Unable to retrieve Object.Failed to open the connection.
    Yesterday Sales The report is named Yesterday Sales.   The documentation says something about removing the duplicate ODBC connection, but the ODBC on the machine I developed the report, and on the server are different. Any Help????Thanks

    Post Author: GraemeG
    CA Forum: General
    The documentation says something about removing the duplicate ODBC connection, but the ODBC on the machine I developed the report, and on the server are different.
    That might be your problem - the report is expecting to find the odbc conector it has been assigned and can't so it fails. Not knowing the version you're using, I suggest you defined an odbc driver on the development machine the same as the one on the server (or vice versa depending on which is less distruptive). Make sure your report is using that connection and republish it. It should work fine.
    Just in case you're not sure how, in XI you change the odbc connection by right-clicking on the 'Database fields' section within Field Explorer, Create new connection and then re-assign each table in the top window to the new odbc connection in the bottom window.

  • Failed to open the connection - database vendor code 17

    I'm upgrading a Windows Forms application from 1.1 to 4.0.  In the reporting form, the list of reports you can choose are pulled from a folder where the .rpt files reside.  Once the user chooses a report and executes it, vb code populates the current database connection information and displays the report in the report viewer control.
    The following things are true:
    - Version 1.1 works on my systems and my customers systems
    - The code has not been changed, except that it now targets .Net 4.0 instead of 1.1
    - The exact same .rpt files are being used
    - Version 4.0 connects to the same database my customer is using, and I can run the reports just fine from here.
    - Version 4.0 is able to connect to the database just fine from my customers systems (using the same connection information provided to the report)
    - My customer installed this:
    The only problem is that my customer encounters this error when trying to run any report from his systems:
    Failed to open the connection.
    Details:  Database Vendor Code: 17
    Failed to open the connection.
    Orders.BOL.TaskDetail {393C9017-0ED1-4E1E-8824-E222F4B9D14C}.rpt
    Details:  Database Vendor Code: 17
    I read all of the articles I could find, and they either don't describe this exact situation, or there is insufficient information for troubleshooting this issue.  Are there steps that I've missed to make Crystal Reports for VS2010 work on my customer's systems?
    Your help is appreciated,

    Hi Mark,
    More information required -
    - Does this happen with all reports or few?
    - What is the connection type used for the report to connect to the database (OLEDB,ODBC etc)
    - Are you changing the database at runtime?
    few things you could check
    - Check if the database is accaessible from the client machine with proper permissions / rights.
    - If its an ODBC connection check if the DSN with same name is created on the client machine.
    - Check the driver / provided used by the report to connect to the DB, verify that the same is installed on the client machine. (SQL NAtive client, SQL Server etc)
    Also take a look at below articles discussing the simillar issue.
    [CR for VS2010: Failed to Open Connection [Database Vendor Code: 17 ]|CR for VS2010: Failed to Open Connection [Database Vendor Code: 17 ]]
    [1474461 - Unknown Database Connector Error when connecting to a Dataset in a VS .NET application |]
    Hope this helps,
    - Bhushan.

  • Failed to open the connection. Details: [Database Vendor Code: 53 ]

    I'm upgrading one of our applications from Visual Studio 2005 to 2010. In the process I'm also switching our reports to run using Stored Procedures instead of Tables/Views.  Everything runs fine on development machines after all the migration work.  On the server however, it does not work. And I am getting the error message ""
    Server is Windows 2003 Server 32 bit.  And yes, I have installed the latest runtimes version 13.0.2000.0 on the server.  There have been no other changes on the server other than to switch the target framework on the website in question from .net 2 to .net 4, and then to modify the web.config file to remove references to the older Crystal Reports and replace with references to the newer version.
    I've seen many other threads on this "failed to open the connection" errors but none of them are my problem except there is one post that remains unanswered where someone had the same Database Vendor Code 53.  I don't know what that error means, spent a considerable amount of time researching that before asking this question.
    Lastly, it appears that this error only happens when the report is pulling data from a Stored Procedure rather than Tables/Views.  If I re-copy the previous reports, they still work.
    The ODBC drivers haven't changed, nor should they. They are fully up to date on that server machine.
    I can't think of anything else that would be indicative of anything other than this is a bug.  Here is the error text as it shows up in the event log:
    Event code: 3005
    Event message: An unhandled exception has occurred.
    Event time: 12/7/2011 3:49:50 PM
    Event time (UTC): 12/7/2011 11:49:50 PM
    Event ID: 38ce5b5487984e8aa8d2b84493d859a8
    Event sequence: 17
    Event occurrence: 1
    Event detail code: 0
    Application information:
        Application domain: /LM/W3SVC/739252194/Root-1-129677751941252500
        Trust level: Full
        Application Virtual Path: /
        Application Path: D:\Websites\ACE5\Clients\TST\
        Machine name: ACE1
    Process information:
        Process ID: 5436
        Process name: w3wp.exe
    Exception information:
        Exception type: InternalException
        Exception message: Failed to open the connection.
    Failed to open the connection.
    Details:  [Database Vendor Code: 53 ]
    Failed to open the connection.
    Details:  [Database Vendor Code: 53 ]
    Failed to open the connection.
    PackSlipTST0 {638463B4-2196-492A-BD6E-9D82CB1862D5}.rpt
       at CrystalDecisions.ReportAppServer.ConvertDotNetToErom.ThrowDotNetException(Exception e)
       at CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext reqContext)
       at CrystalDecisions.CrystalReports.Engine.FormatEngine.ExportToStream(ExportRequestContext reqContext)
       at CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToStream(ExportOptions options)
       at CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToHttpResponse(ExportOptions options, HttpResponse response, Boolean asAttachment, String attachmentName)
       at CrystalDecisions.CrystalReports.Engine.ReportDocument.ExportToHttpResponse(ExportFormatType formatType, HttpResponse response, Boolean asAttachment, String attachmentName)
       at Distribution_PackingSlips_default.ExportPackingSlips(String CrystalReportPath, Boolean UseStoredProcedure)
       at Distribution_PackingSlips_default.Page_Load(Object sender, EventArgs e)
       at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
       at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
       at System.Web.UI.Control.OnLoad(EventArgs e)
       at System.Web.UI.Control.LoadRecursive()
       at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    Failed to open the connection.
    Failed to open the connection.
    Details:  [Database Vendor Code: 53 ]
    Failed to open the connection.
    Details:  [Database Vendor Code: 53 ]
    Failed to open the connection.
    PackSlipTST0 {638463B4-2196-492A-BD6E-9D82CB1862D5}.rpt
       at CrystalDecisions.ReportAppServer.Controllers.ReportSourceClass.Export(ExportOptions pExportOptions, RequestContext pRequestContext)
       at CrystalDecisions.ReportSource.EromReportSourceBase.ExportToStream(ExportRequestContext reqContext)

    Lots of great info here, except for the database; MS SQL? Oracle? Etc?
    Database Vendor Code 53 is an error code that the CR engine simply passes straight from the database it's self. E.g.; look at your database error code and you should be able to find a verbose description of the error.
    As a test, what happens if you add the report to your project and run it in the CR design part of the .NET IDE?
    - A quick google search of Error 53 (for MS SQL - an assumption) comes up with a number of good hits. E.g.;
    Follow us on Twitter
    Got Enhancement ideas? Try the [SAP Idea Place|]
    Edited by: Ludek Uher on Dec 8, 2011 6:31 AM

Maybe you are looking for