Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Error message when you run a custom Crystal Reports report in Microsoft Dynamics SL: "Crystal Print Engine Error: 709 The table could not be found"

Error message when you run a custom Crystal Reports report in Microsoft Dynamics SL: "Crystal Print Engine Error: 709 The table could not be found"

Symptoms

Consider the following scenario:
  • You are running Microsoft Dynamics SL 7.0 or Microsoft Dynamics SL 2011.
  • You use a custom Crystal Reports report.
  • You log on by using Windows Authentication.
In this scenario, you receive the following error message:
Crystal Reports Helper Application for Solomon IV
Get SQL Query failed Report: C:\Program Files\Microsoft Dynamics SL\Usr_Rpts\03730DET.RPT
Crystal Print Engine Error: 709 - Error in File C:\Program Files\Microsoft Dynamics SL\Usr_Rpts\03730DET.RPT:

The table could not be found.

↑ Back to the top

Cause

Cause 1

This error occurs because the following conditions are true:
  • The Crystal Reports report uses one or more custom tables or custom views.
  • Either the E7F575915A2E4897A517779C0DD7CE Microsoft SQL Server user or the MSDSL SQL Server application role does not have the required permissions to the custom table or to the custom view. See Resolution 1 in the "Resolution" section.

Cause 2

An Open Database Connectivity (ODBC) connection is set up incorrectly to use Windows Authentication instead of SQL Server authentication. When you first run a Crystal Reports report on a new workstation, an ODBC connection is created for the Microsoft Dynamics SL system database and for the Microsoft Dynamics SL application database. This connection should be set up to use SQL Server authentication, even if you use Windows Authentication to log on to Microsoft Dynamics SL. See Resolution 2 in the "Resolution" section.

↑ Back to the top

Resolution

Resolution 1

Assign the appropriate rights to the custom table or to the custom view. To do this, follow these steps:
  1. Start Microsoft SQL Server Management Studio.
  2. Expand Databases, expand the Dynamics SL database, and then expand Tables or Views.
  3. Locate the custom table or the custom view in the list.
  4. Right-click the custom table or the custom view. Then, select Properties.
  5. In the Select a Page pane, click Permissions.
  6. Click ADD, type MSDSL, and then click OK.
  7. For the Select permission, click to select the Grant check box.
  8. Click ADD.
  9. Click Browse. Then, click to select the check box next to the E7F575915A2E4897A517779C0DD7CE user.
  10. Click OK two times.
  11. For the Control permission, click to select the Grant check box.

Resolution 2

To resolve this problem, delete the ODBC connections, and let Microsoft Dynamics SL re-create the connections. To do this, follow these steps:
  1. Click Start, click Settings, and then click Control Panel.
  2. Click Administrative Tools.
  3. Click Data Sources (ODBC).
  4. On the User DSN tab, remove any entries for the Microsoft Dynamics SL system database and for the Microsoft Dynamics SL application database.
  5. On the System DSN tab, remove any entries for the Microsoft Dynamics SL system database and for the Microsoft Dynamics SL application database.
  6. Log on to Microsoft Dynamics SL again, and then try to use the report again. The User DSN entries should be re-created automatically.

↑ Back to the top

Keywords: kbmbspartner, kbexpertisebeginner, kbtshoot, kbmbsmigrate, kbprb, kbexpertiseinter, kbsurveynew, kb

↑ Back to the top

Article Info
Article ID : 939712
Revision : 1
Created on : 1/7/2017
Published on : 8/2/2011
Exists online : False
Views : 94