SAP Knowledge Base Article - Public

1246462 - Crystal Reports crashes when tables are updated to a SQL Server Stored Procedure using Set Data Source Location


  • Cannot update current connection with a stored procedure.
  • The connection name for the stored procedure does not change.
  • Crystal Reports crashes when connection is updated with SQL Server stored procedure.


  • SAP Crystal Reports 2013
  • SAP Crystal Reports 2016 
  • MS SQL Server

Reproducing the Issue

  1. In Crystal Reports, create a report to a MS SQL Server database.
  2. Under the menu "Database", select "Set Database Location"
  3. Update the connection to SQL Server, to a Stored Procedure.


  • The database tables are updated with the Stored Procedure but the connection name for the stored procedure doesn’t change, and this normal behavior.
  • But Crystal Reports crash because of the MS Windows Data Execution Prevention.


  •   Set the MS Windows Data Execution Prevention, to allow Crystal Reports:
    1. Right Click on My Computer, and select "Properties"
    2. Click on Advanced tab
    3. Click on Settings in the Performance frame
    4. Go to Data Execution Prevention (DEP) tab
    5. Check the option ‘Turn on the DEP for all programs and services except those I select:’
    6. Browse to the appropriate location and add the application crw32.exe
    7. Click OK

      Note: The above steps may be different, depending on the version of MS Windows used.

  • Rename the connection in Crystal Reports:
    1. In Crystal Reports, open the report, and under the menu "Database", select "Database Expert"
    2. On the Selected Tables panel, right click on the connection name, and select "Rename"
    3. Rename it to the newly created Stored Procedure connection.


CR , KBA , BI-RA-CR , Crystal Reports designer or Business View Manager , Problem


SAP Crystal Reports 2013 ; SAP Crystal Reports 2016