ReCrystallize Pro Support Frequently Asked Questions

Unable to connect to data source warning /
Common database connection and logon issues with troubleshooting steps.

Synopsis:

When attempting to view a Crystal Report on the web using ReCrystallize Pro's Dynamic option to view the report with "live" data, the following message is displayed:

ReCrystallize Warning: Unable to connect to data source using the following information.

More Information:

Dynamic reports connect to the database each time the report is viewed in order to retrieve fresh data.  The connection process attempts to log on to the database and tests the connection for each database table that is used in the report.  If the connection test fails, the web page displays the message, "ReCrystallize Warning: Unable to connect to data source using the following information."

A number of issues can prevent the database connection from succeeding.  This article outlines some common issues and solutions.

Issues and Troubleshooting:

1.  Incorrect connection details or database password.

ReCrystallize Pro's database connection screen is designed to provide all required connection details to log on to the database including

• Server Name or ODBC DSN
• Database / Table Name
• User Name
• Password

With the exception of the password, ReCrystallize Pro will default these entries correctly based on the database connection properties stored in the rpt fie.  In most cases these values should not be changed except to provide a database password if one is required. It is possible to override the connection details in order to use a different ODBC DSN, different database user account and so on when the report is viewed on the web; however, changing any of these values incorrectly can lead to log on failures.

For databases that require a password (e.g. Oracle and SQL Server), providing no password or an incorrect password will cause the connection to fail.  The password should be provided in the ReCrystallize Pro wizard's database logon screens and is stored in the dynamic.asp or dynamic.aspx file.  Please check the dynamic.asp or dynamic.aspx file to ensure that the password is correct.  Please verify that you can refresh the report in the Crystal Reports designer using the same username and password to log on to the database.

2.  SQL Server ODBC configuration.

When using the Microsoft SQL Server database, the ODBC configuration should use the following settings:

• TCP/IP connection
• SQL Authentication

3.  ODBC User DSN

An ODBC User DSN will allow reports to connect to the database and refresh in Crystal Reports but will fail when viewing the report on the web.  Because the report is run by the web server rather than a normal user account, a System DSN must be configured in ODBC.

4.  On 64-bit versions of Windows, a 64-bit ODBC connection is configured.

When using a 64-bit version of Windows, the ODBC settings available from the Start Menu through Administrative Tools create 64-bit ODBC connections.  The Crystal Reports runtime used on the web server is 32-bit and therefore requires 32-bit ODBC connections and cannot utilize 64-bit ODBC connections.  The only exception is the Crystal Reports 2011 64-bit runtime available with ReCrystallize Pro 14 or higher. In most instances, the 32-bit Crystal Reports runtime is used even if the Windows OS is 64-bit.

To configure a 32-bit ODBC connection, use the the 32-bit ODBC Data Source Administrator.  From Windows Explorer or a command prompt, open 

C:\Windows\SysWOW64\odbcad32.exe

5.  Insufficient file system or network permissions to for file-based database types.

When using a file-based database such as Microsoft Access or FoxPro, file system and/or network share permissions must allow the IIS web server to read the database file. For example, the IUSR_* account on the server may require Read access to the directory and/or network share where the database file (.mdb, .dbf, etc.) is located.  As a troubleshooting step, temporarily add the Everyone group with read access to the directory, file, and network share (if applicable).  If this allows the server to connect to the database and display the report, remove the Everyone group and determine the specific account(s) that require permissions to read the database file.  If the database file is located on a network resource, it may be necessary to set up a domain account with access to the database file and then configure IIS to use the domain account.