How to troubleshoot the error message: "Crystal Error 534 - Error detected by database DLL" in Microsoft Dynamics SL

INTRODUCTION

In Microsoft Dynamics SL, when you try to print a custom report or to preview a custom report, you receive the following error message:

This article describes how to troubleshoot this error message.

MORE INFORMATION
To troubleshoot the error message, follow these steps.

Note Before you follow these steps, make sure that no other users are logged on to Microsoft Dynamics SL.

1. Start Microsoft SQL Server Profiler. To do this, use the appropriate method:
   
   Method 1: If you are running SQL Server 2005 or SQL Server 2008

   1. Start SQL Server Management Studio, and then connect to the server that hosts the Microsoft Dynamics SL databases.
      

   2. On the Tools menu, click SQL Server Profiler.
      

   3. Click File, click New Trace, and then connect to the server that is running SQL Server and that hosts the Microsoft Dynamics SL databases.
      

   Method 2: If you are running SQL Server 2000

   1. Click Start, point to All Programs, point to Microsoft SQL Server, and then click Profiler.
      

   2. Click File, point to New, click Trace, and then connect to the server that is running SQL Server and that hosts the databases for Microsoft Dynamics SL.

2. In the Trace Properties dialog box, click Run.

3. Open the Reports Options Interpreter (ROI) screen for the custom report, and then click Print Preview. You receive the following error message:

   Crystal Error 534 – Error detected by database DLL

   Note Do not click OK when you receive this error message.

4. Switch to SQL Server Profiler, and then click Stop Selected Trace on the toolbar.

5. In the Details pane, use the Copy command to move the SELECT statement to the Clipboard.

6. Start Query Editor or SQL Query Analyzer, and then select the appropriate application database.

7. Use the Paste command to move the SELECT statement from the Clipboard into the Query pane, and then press F5 to run the SELECT statement.
   
   Note Use the results from step 7 to determine what to modify in the report to correct the problem.

Note These troubleshooting steps can also be used if the expected data does not appear in the report. These steps help you determine whether the problem is in the query that is contained in the report, or whether the problem is related to suppression in the report.