Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics SL forum
Answered

Crystal Print Engine Error 709

Posted on by 145

I am running Dynamics SL 7 FP1 SP4. I recently upgraded the SQL server from 2005 to 2008 in anticipation of moving my Dynamics installation to a new server. After the SQL upgrade most everything works fine except a few reports. When I run them I get the error "Crystal Print Engine Error 709 - Table not found". I am not using any custom tables or views. Any help would be appreciated.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Crystal Print Engine Error 709

    If no custom tables or views are involved, follow Rick's suggestion to run the synchronize security scenario in SL Database Maintenance. If you still encounter errors, you should post which reports are affected by the SQL upgrade. Starting a SQL profiler trace before launching the report can also help by identifying the statement that is causing the error.

  • Joseph Gattozzi Profile Picture
    Joseph Gattozzi 145 on at
    RE: Crystal Print Engine Error 709

    I saw this tech note but I am not using any custom tables or views.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Crystal Print Engine Error 709

    Here is the TK Doc that may help resolve this issue:

    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"

    View products that this article applies to.

    Article ID : 939712

    SYMPTOMS

    Consider the following scenario:

    • You are running Microsoft Dynamics SL 7.0.

    • You use a custom Crystal Reports report.

    • You log on by using Windows Authentication.

    In this scenario, you received 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.

    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 incorrectly set up 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.

    RESOLUTION

    Resolution 1

    Assign the appropriate rights to the custom table or to the custom view. To do this: 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 automatically be re-created.

    --------------------------------------------------------------------------------

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Crystal Print Engine Error 709

    It sounds like some tables may have been created (during a previous database update) under a different user.  Open SL Database Maintenance and run the synchronize all ownership and security process and see if that takes care of your issue.

    If not, identify one of the tables in question and look at its permissions under properties comparing those to a table that is not giving you an issue.

Helpful resources

Quick Links

Replay now available! Dynamics 365 Community Call (CRM Edition)

Catch up on the first D365 Community Call held on 7/10

Community Spotlight of the Month

Kudos to Saurav Dhyani!

Congratulations to the June Top 10 community leaders!

These stars go above and beyond . . .

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 287,696 Super User

#2
Martin Dráb Profile Picture

Martin Dráb 225,490 Super User

#3
nmaenpaa Profile Picture

nmaenpaa 101,148

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans