SAP CRYSTAL REPORT 2020 support ODBC DRIVER 18 FOR SQL SERVER?

[Srividya]

In our product, we have many crystal reports which are designed to fetch data using MS SQL stored procedure, it is getting launched successfully, when we use the ODBC Driver SQL Server, and while upgrading the MS SQL ODBC driver to "ODBC driver 18 for SQL Server", we are facing the below problem in SAP crystal report processing. 

05/02/2024 4:32:52 PM The table 'R_ADT_ADM001' could not be found. Error in File ADM002 5356_10864_{D00DEF7A-1D90-4C60-84AE-C2061BB38337}.rpt: The table could not be found. (-2147482939)

We are currently using the SAP crystal report run time "CRRuntime_32bit_13_0_15.msi" to invoke the report. 

On further analysis, when we open the Crystal Reports using the SAP Crystal Report 2020 and Set Datasource Location selected the Report ‘R_ADT_ADM007’ linked with Stored procedure are unable to open in the Sap crystal report, it prompts a Message “Data Object Cannot be opened/accessed”.

Kindly review and let us know any configuration we missed out or is the ODBC driver 18 for SQL Server supported.

[DellSC · Accepted solution]

The supported platforms doc for Crystal for Visual Studio is here:  https://www.sap.com/documents/2016/06/f871031e-757c-0010-82c7-eda71af511fa.html

It shows that version 18 of the ODBC driver for SQL Server wasn't supported until SP23 for SQL Server 2017 and SP27 for SQL Server 2019.  You are currently running SP 15.

In order to support version 18 of the ODBC driver, you will need to upgrade your application to the latest version of the SDK (currently SP35) by recompiling it with the newer version.  There were some changes made to the SDK at SP21 that mean that you'll have to make a couple of tweaks to your code to get it to work with the new version. Unfortunately, when SAP re-wrote the wiki, they removed the links from @DonWilliams  that show what the changes are.  I hope that by tagging him here, he'll respond with that information.

You may also have to update the .NET version targetted by your application - the minimum supported version is now 4.6, which was also supported by the SP15 that you're currently using.

Then you'll need to install the new runtime on the server when you deploy your application.

You can find the latest version of the SDK through links here:  https://help.sap.com/docs/SUPPORT_CONTENT/crystalreports/3354091173.html.  You'll download a .exe file to get the integration with Visual Studio.  This .exe needs to be installed by right-clicking on it and selecting "Run as Administrator".  The other files available for SP 35 are the various forms of runtime installs - you will select one and it will be installed ONLY when deploying your application.  DO NOT install a runtime on the computer where you're running Visual Studio.

-Dell

[sbalasubra46 · Accepted solution]

I am currently Investigating this task, as Srividya is held up in other priorites,

In response to your earlier post, we installed the Crystal Report for Visual Studio SDK (SP35) CRforVS13SP35_0-80007712.EXE 32-bit version and have rebuilt our crystal report component by setting the Target Framework to .Net Framework 4.8 and referenced the CrystalDecisions references as appropriate. However, it resulted in the same error Table not found.

Please note, we have a 32 bit Main Application, in which the crystal report component is invoked, where we use Stored Procedure to populate the data from the database, which, when the latest “ODBC Driver 18 for SQL Server” used it connects successfully to our Main 32 bit Application but failed to launch the crystal reports, as it unable to identify the stored procedure and results in Table not found error.

And to note, we find that, in the same environment, if we use the legacy ODBC Driver that is available as default in windows machine “SQL Server” it works fine without any error.

On further investigation, we installed the latest crystal report version 2020 and tried “Set Location” and “Verify Database” using the ODBC datasource “ODBC Driver 18 for SQL Server” unable to perform both above activities, even with a new SP created and linked.

Hence, It would be helpful, if you could get some technical assistance on launching the Crystal report that uses the stored procedure via the “ODBC Driver 18 for SQL Server”, would help our investigation.

- Suresh Balasubramanian

[DellSC · Accepted solution]

What version of SQL Server are you trying to connect to?

[sbalasubra46 · Accepted solution]

We tried with the SQL Servers both resulted in "The table could not be found. (-2147482939)"

1. Microsoft SQL Server 2022 (RTM) - 16.0.1000.6 (X64)

and

2. Microsoft SQL Server 2019 - 15.0.2104.1 (X64)

[mhotze · Accepted solution]

We observe the same issue when switching from ODBC Driver 17 to OBDC Driver 18 with SQL Server 16.0.1110.1 and 15.0.4355.3. With the reference from https://community.sap.com/t5/technology-q-a/existing-crystal-report-update-data-source-to-odbc-18-dr..., in my opinion, the ODBC function 'SQLProcedures' is suspected of having been changed by Microsoft. However, I could not confirm this with a test of the two driver versions. Both the ODBC driver 17 and the ODBC driver 18 return no result when calling 'SQLProcedures' with the value '<procedure_name>;1'. SQL Profiler, however, shows that the CR Engine does make a second attempt with the pure name. But unfortunately that doesn't change the fact that CR Engine doesn't seem to find the procedure. Hope this helps somehow.

[sbalasubra46 · Accepted solution]

I believe this post not Answered yet,

On further investigation, we installed the latest crystal report version 2020 and tried “Set Location” and “Verify Database” using the ODBC datasource “ODBC Driver 18 for SQL Server” unable to perform both above activities, even with a new SP created and linked.

However, these activities were working when we use the Datasource configured with “ODBC Driver 17 for SQL Server” .

Hence, It would be helpful, if you could get some technical assistance on launching the Crystal report that uses the stored procedure via the “ODBC Driver 18 for SQL Server”, would help our investigation.

Do SAP Crystal Report have support for SQLProcedures function when Datasource is used with “ODBC Driver 18 for SQL Server”?

- Suresh Balasubramanian