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!!!!!

Similar Messages

Crystal report Error "Failed to open the connection."

I have an ASP.NET application that access a database through ODBC. There is a problem when I run Crystal Report " Failed to open the connection. Failed to open the connection". Can someone tell me how can i overcome ths problem.

Moved to .NET SDK forum.
Search here, lots of posts on how to debug database access through a WEB app.
Don

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
mhortman:
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.

Getting Error:Failed to open the connection while calling crystal report

I am getting the below error while calling the crystal report from dot net app. I am using OLEDB to connect to database. It is working perfectly in our DEV environment but as soon as I move it to production information after changing the logon information in the report it start giving the below error.
Failed to open the connection.C:\WINDOWS\TEMP{C2FD97D9-2ADE-41BB-88FF-23A4DF20BC6F}.rpt
Details: [Database Vendor Code: 17 ]

Are you able to connect to the database from the production machine using a UDL file?
If you haven't tried this, here's how to do it. Take these steps on the machine that is hosting the application. Create a new text file on the desktop. Change the file extension to ".udl" (without the quotes). Double-click on this to bring up the OLEDB connection test: start on the Provider tab and select the appropriate provider. Click "Next" and on the following tab enter your connection information. Click the "Test Connection" button to test the connection. Does it connect to the database successfully?
If you click on "OK" to close the dialog and then open the UDL file with Notepad, you should see an OLEDB connection string. In this string should be the same property values for server, database, user id and password which you are providing through your application. If they are not the same, modify your application to use these values.
If testing your connection information with the UDL file works but your application is still failing when using the same credentials, try profiling or tracing the database. Do you see connection attempts from the application? Are there any errors?
If you're impersonating, have you set up windows authentication correctly for both the application and the database?

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.
Regards,
Navin

Failed to open the connection on CR Server 2008 .

Hi,
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 ?
Thanks

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
Thanks,
Gordon

Error"Failed to open the connection" - Named Instance of SQL Server 2005

"Failed to open the connection" error, when connecting to the Named Instance of SQL Server 2005
The report is throwing error, when changing the logon information dynamically through C#.
Code
     string reportPath = @"D:\NET\TestReport\TestReport.rpt";
     ReportDocument reportDocument = new ReportDocument();
     reportDocument.Load(reportPath);
     foreach(CrystalDecisions.CrystalReports.Engine.Table table in tables)
          TableLogOnInfo tableLogonInfo = table.LogOnInfo;
          tableLogonInfo.ConnectionInfo.ServerName = @"TestServer\Instance1"; //Connnecting to Named instance of SQL Server 2005
          tableLogonInfo.ConnectionInfo.UserID = "sa";
          tableLogonInfo.ConnectionInfo.Password = "password";
          tableLogonInfo.ConnectionInfo.DatabaseName = "TEST_DB";
          table.ApplyLogOnInfo(tableLogonInfo);
     crystalReportViewer1.ReportSource = reportDocument;
Error Message
     Failed to open the connection.
     Failed to open the connection.
     C:\DOCUME1\PUGALE1\LOCALS~1\Temp\{DF9593A5-5C80-4CBC-ABC3-EC4EF204A7EB}.rpt
The error is occuring only whenever i am connecting to the Named Instance of SQL Server 2005.
Thanks in Advance
Edited by: pugalendran p on Feb 2, 2009 10:32 AM
Edited by: pugalendran p on Feb 2, 2009 10:43 AM

Hi,
Following solution might help you to resolve the issue.
Solution1:
Issue happens because universe connection to the Database is not responding and the Data Source Name is not configured to write SQL Server 2005 database.
Resolution
Created new DSN connection under SYSTEM DSN to SQL Server 2005 Database.
Import the universe from the designer.
Go to File->Parameters.
Edit Connection.
On the Database Middleware Page expand SQl Server 2005->Select SQL Server 2005 driver.
Change the DSN to new DSN connection
Test the connection.
Save the Universe and Export it to the repository.
Solution2:
I am taking Oracle as an example over here.
This can be caused when the SQLNET.ora is located in a remote location using mapped drives.
Resolution
To resolve,
check the registry [HKLM\SOFTWARE\ORACLE] you should see a folder called HOME0
look for any paths that contain a mapped drive partition
Change the mapped drive letter to a UNC path (
server\folder)
Open a command prompt and do a tnsping using the tnsname and verify the location of the SQLNET.ora or TNSNAMES.ora
If the path is not updated to the new path
Reboot the server
Regards,
Sarbhjeet Kaur

"Failed to open the connection" - Add-on Crystal Reports (SAP B1 2007A)

I have Created One Crystal Report.
When I Preview Report (Administration>Crystal Reports>Select Report-->Print and Preview),
System displays the following error message.
" Failed to open the connection."
Can you help me?
Kind regards
Margarida Pedroso
PT

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
Thanks,
Gordon

Failed to open the connection in Crystal Reports

Hi All,
I have Created One Crystal Report.
When I Preview Report (Administration>Crystal Reports>Select Report-->Print and Preview),
System displays the following error message.
" Failed to open the connection."
Where as when I view the same report directly from Crystal Designer (Administrator --> Crystal Reports Administrator --> Crystal Designer ). It is working fine.
BR
Dixit Patel
Edited by: Dixit Patel on Dec 11, 2008 4:43 PM

Hi Dixit,
I've just found the same problem,
could you let me know how to solved this problem?
because at first I installed and run the report,
it doesn't result any error message
Thanks for your help
regards,
alvin

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 13.0.2.0 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 I...in 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!!!
Shayne

Don't use localhost as your server name. It's a reserved name and should not be used in code.
Try this also [Kbase |http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333533353333333433363339%7D.do] 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. 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
    Account name: NT AUTHORITY\NETWORK SERVICE
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.;
http://social.msdn.microsoft.com/Forums/en-AU/sqlgetstarted/thread/27684811-1a59-4273-b7ed-3cc990b4f20a
Ludek
Follow us on Twitter http://twitter.com/SAPCRNetSup
Got Enhancement ideas? Try the [SAP Idea Place|https://ideas.sap.com/community/products_and_solutions/crystalreports]
Edited by: Ludek Uher on Dec 8, 2011 6:31 AM

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

We have too many reports designed by Crystal Reports XI Release 2 a time ago reports are old but we are calling them in asp.net 4.0 and connection through ODBC Data Sources (Driver SQL SERVER)
but when we refresh the report we are facing this issue....
Failed to open the connection.
Details: [Database Vendor Code: 17 ] Failed to open the connection.
AP Outstanding Check Run Detailed Ver 2 {CF3B13A2-F259-4B1D-ACC9-BF78F44D4AA5}.rpt
Details: [Database Vendor Code: 17 ]
here is the code to set ReportLoginInfo
CrystalDecisions.Shared.TableLogOnInfo logonInfo = new CrystalDecisions.Shared.TableLogOnInfo();
            string myTableLocation;
            foreach (CrystalDecisions.CrystalReports.Engine.Table myTable in rptDoc.Database.Tables)
                myTableLocation = myTable.Name;
                logonInfo = myTable.LogOnInfo;
                logonInfo.ConnectionInfo.AllowCustomConnection = true;
                logonInfo.ConnectionInfo.ServerName = ServerName; // dnsname
                logonInfo.ConnectionInfo.DatabaseName = DatabaseName;
                if (!(string.IsNullOrEmpty(UserID) || string.IsNullOrEmpty(Password)))
                    logonInfo.ConnectionInfo.UserID = UserID;
                    logonInfo.ConnectionInfo.Password = Password;
                    logonInfo.ConnectionInfo.IntegratedSecurity = false;
                logonInfo.ConnectionInfo.Type = CrystalDecisions.Shared.ConnectionInfoType.SQL;
                myTable.ApplyLogOnInfo(logonInfo);
                myTable.Location = DatabaseName + ".dbo." + myTableLocation;
                bool success = myTable.TestConnectivity();
Edited by: zeshansadiq on Nov 4, 2011 3:49 PM

resolved by me itself.
Do the following steps:
1. Open the report in the CR XI designer.
2. Select Database -> Set Datasource Location.
3. Set Datasource Location window will appear and in the replace with section connect to the database and replace these tables with the tables in the current datasource by clicking the update button.
4. After updating close the Set Datasource Location window.
5. Go to 'Database menu' and Click 'Verify Database' and click on u2019OKu2019.
6. Preview the report and the save the report.

Failed to open the connection after changing the connection in CMC

Hi
Below are our environment details:
BOXI 3.1 SP3
Solaris Sparc 10
Crystal Reports 2008 Sp3
Weblogic 11g
Our team is facing the problem as described below:
We have created Crystal Reports using JDBC connection and it works fine
in an environment(SIT).
When we migrate these reports to the another environment(UAT) we get
the error "Failed to open the connection"
After migrating we indeed change the connection to Custom Database
Login Information in CMC.
So to troubleshoot we installed Crystal Reports in UAT environment and
had to perform Set DataLocation after which
the reports starting working fine.
Now when we are migrating reports to Production we have the same issue.
We cannot install Crystal Reports on Production this time and hence we
are stuck.
Please let us know if any known workaround or solution for the same.
Thanks
Kamal
Edited by: Kamalaksha Shetty on Nov 15, 2011 4:18 AM

Hi Meenal,
I am not 100% sure I understood the workaround of having Crystal Designer on the server. Can you connect from UAT designer to production and perform the same operation?
Check this KBA that describes this problem and a solution:
https://service.sap.com/sap/support/notes/1445067
Regards,
Julian

"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. 12.0.0.549, 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
            Response.Redirect("/errors/MissingReport.aspx")
        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
        InitializeReport()
    End Sub
    Protected Sub InitializeReport()
        Dim RD As New ReportDocument
        Dim CI As ConnectionInfo = MakeConnectionInfo(DB_Bonus)
        Dim RPF As CrystalDecisions.Shared.ParameterField = Nothing
        RD.Load(ReportPath)
        If ReportParams.SelectString <> "" Then
            Dim Adapt As New SqlDataAdapter(ReportParams.SelectString, DB_Bonus)
            Dim DS As New Data.DataSet
            Adapt.Fill(DS)
            RD.SetDataSource(DS.Tables(0))
        End If
        For Each kvp As KeyValuePair(Of String, String) In ReportParams.Formulas
            Dim FFD As FormulaFieldDefinition = Nothing
            Try
                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"))
                        Else
                            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
        Next
        For Each T As CrystalDecisions.CrystalReports.Engine.Table In RD.Database.Tables
            Dim TLI As TableLogOnInfo = T.LogOnInfo
            TLI.ConnectionInfo = CI
            T.ApplyLogOnInfo(TLI)
        Next
        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
Regards,
Rakesh Pati
SAP Business One Forum Team.

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.

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

Similar Messages

Maybe you are looking for