Purpose

This Jive Document aims to help Visual Studio developer troubleshoot issues with Crystal Reports when connecting to ADO .NET Datasets.

Overview

Searching the SCN and using the techniques described in this document will resolve most issues when passing ADO .NET Datasets to SAP Crystal Reports.

Possible issues and errors

For the most part, the issues are; slow performance, incorrect data, no data, prompt for login credentials to a database and more. The following errors are common:

"Unknown Database Connector Error"

"Failed to retrieve data from the database"

“Query Engine Error 'C:\WINDOWS\TEMP\temp.....rpt”

“Log on failed...”

Prerequisites

• It is assumed that the developer is familiar with creation of datasets and the basic limits when using datasets with Crystal Reports. For more details see the following resources:

      Crystal Reports Guide To ADO.NET

      Reporting Off ADO.NET Datasets

• Ensure that you are working with the latest Service Pack for your version of Crystal Reports. The following Jive Dcuments list the latest updates and links to the updates:

     Crystal Reports for Visual Studio 2010 Updates & Runtime Downloads

     Crystal Reports 2008 (12.x) Updates & Runtime Downloads

     Crystal Reports for VS 2005 and VS 2008 Updates & Runtime Downloads

Basic Troubleshooting Steps

If the issue exists on a deployed system, but the application works on the development system, ensure that the Crystal Reports runtime matches the two systems. Use the Modules  utility to check what DLLs and veriso of theDLLs used by an application.

Search the SCN community for solutions. You can use the SCN search page, or use the text search box located in the top right corner of each SCN space:

For SAP Crystal Reports for Visual Studio 2010  see KBase 1525432 - Could not load file or assembly 'file:///<Path>crdb_adoplus.dll' or one of its dependencies.

Advanced Troubleshooting Steps

The following steps may apply on development as well deployed systems.

Create an XML file off of your dataset. Make sure this is done just before you set the dataset to the report:

rpt.Load(rptPath)
myDataset.WriteXml(xmlPath, XmlWriteMode.WriteSchema)
rpt.SetDataSource(myDataset)

1. Copy the above created XML to your development system
2. Open the problem report in the Crystal Reports designer
3. In the Desigger, go to the Database menu and select “Set Datasource Location”
4. In the “Replace with:” pane, expand the “Create New Connection” folder
5. Double click the “ADO .NET (XML)” icon
6. Browse to the location of the XML file you created in step (1)
7. Click on the path to the XML. The <Update> button should enable
8. Click on the <Update> button

One of a two possibilities should happen now:

1. You will get a “Map Fields” dialog. This indicates that the XML written off of the dataset does not match what the report is expecting. This may be due to incorrect field names, incorrect field types, etc. It is up to the developer to eliminate the differences.
2. Incorrect data or no data. There is an issue with the dataset and the developer will need to determine why the data is not present in the dataset. Looking at the XML may be a good place to start.
   

Related Content

Related Documents

Crystal Reports Guide To ADO.NET

Reporting Off ADO.NET Datasets

Crystal Reports for Visual Studio 2010 Updates & Runtime Downloads

Crystal Reports 2008 (12.x) Updates & Runtime Downloads

Crystal Reports for VS 2005 and VS 2008 Updates & Runtime Downloads

SAP Crystal Reports .NET API Guide

SAP Crystal Reports .NET SDK Developer Guide

Report Application Server .NET SDK Developer Guide

Report Application Server .NET API Guide

Related Notes

1525432 - Could not load file or assembly 'file:///<Path>crdb_adoplus.dll' or one of its dependencies

1598993 - Logon Failed. Error in File xxx.rpp... when using ADO .NET dataset with TTX based reports (64 bit)

1474461 - Unknown Database Connector Error when connecting to a Dataset in a VS .NET application