SAP Knowledge Base Article - Public

3054292 - Report based on MS SQL Server with encrypted columns fails to execute in Crystal Reports

Symptom

  • Unable to refresh report connecting to MS SQL Server with encrypted columns.
  • Is it possible to refresh a report based on MS SQL Server with Always Encrypted Columns in Crystal Reports?

Environment

  • SAP Crystal Reports 2016
  • SAP Crystal Reports 2020

Reproducing the Issue

  1. In Crystal Reports, create a report based on MS SQL Server.
  2.  Add a table with encrypted column.
  3. Add a filter on the encrypted column.
  4. Refresh the report, and it fails to execute. 

Resolution

Below are the test results when refreshing a report in Crystal Reports based on MS SQL Server with Always Encrypted columns:

  • Crystal Reports support the following MS SQL Server middleware on tables with ‘Always Encrypted’ columns.
    • Microsoft ODBC Driver 13 for SQL Server (sqlncli13.dll)
    • Microsoft ODBC Driver 17 for SQL Server (MSODBCSQL17.dll)
    • Data Direct ODBC 8.0.2 (ODBC SQL Server Wire Protocol Driver Setup)
          
  • Crystal Reports does not support following MS SQL Server middleware on tables with ‘Always Encrypted’ columns.
    • Microsoft JDBC Driver for SQL Server - version 8.2
    • Microsoft OLEDB Driver for SQL Server (MSOLEDBSQL.dll) - version 18

Note: Do not perform actions like: filter(lookups), equality joins, grouping,... on 'Always encrypted' columns when creating a report in Crystal Reports using the Report Creation Wizard. You can do these actions on other non 'Always encrypted' columns. 

  • Workaround:
    It is possible to add filter to Saved Data Selection, instead of the Record Selection Formula.

Keywords

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

Product

SAP Crystal Reports 2016 ; SAP Crystal Reports 2020