DateTime Parameter issue with the MS SQL stored Procedure when generating Report

[sathishbabu_gnanasambanda]

Hi Team,

I am using the CR Runtime Engine (CR Runtime 13.0.23.2819) using the SQL Database (2014) and executing a SPROC to run reports.

The .NET windows Application was working fine with TLS1.0 enabled, but when we disable TSL 1.0 and Enable TLS 1.2, the CR did not work with the SQLOLEDB Driver, so we upgraded the CR Runtime to (CR Runtime 13.0.31.4010) and Tried with the new driver installed MSOLEDBSQL19 Driver, it supported the TLS1.2, but some of the reports that has DateTime as one of the Parameter, it is not working and throwing a syntax error at the Convert function. Below is what we get when we trace the SQL request in the profiler. Browsed through lot of forums, but seems this latest driver is not supported by CR yet. Is that still holds true or is there any fix for the below ?

exec "ARxDb"."dbo"."SP_Name";1 CONVERT(DATETIME, '2022-03-24 13:56:03', 120), CONVERT(DATETIME, '2022-03-24 13:56:03', 120), '03770' (which is not a valid statement for executing the sproc)

Need to find the correct driver that supports both TLS 1.2 and also that does not throw the DateTime convert error.

Thanks in advance.

Sathish

[DellSC]

I changed the primary tag on your question to "SAP Crystal Reports, version for Visual Studio" as this is the tag for questions about using the .NET SDK. The "SAP Crystal Reports" tag is generally for questions about report design and the Crystal Reports desktop software.

-Dell

[former_member11696]

Yes you do need to upgrade to SP 32, releasing tomorrow:

Follow this WIKI:

https://wiki.scn.sap.com/wiki/display/BOBJ/Crystal+Reports%2C+Developer+for+Visual+Studio+Downloads

The other issue Microsoft updated their client dll name, for CR to be able to use the recent Clients you need to manually upgrade each report.

Open CR Designer, open your report, Click on Menu Database, Set Datasource Location.

In the new list of connection select OLE DB or ODBC and select the latest OLE DB Client from the list. If using ODBC then your DSN needs to be updated to also use the latest Client.

Unfortunately there is no mass update API that can update the report when saved. You can update the report to use the new connection info but it doesn't get saved, only works in the current session which is why you need to update the reports manually.

Use Google and search for this KBA - 2269180 - Disabling TLS 1.0 and 1.1 causes Crystal Reports and .NET application to fail to connect to MS SQL Server

It's older but should answer a few questions.... Using a MS Client that supports TLS 1.2 is Client side configuration only, other then updating the reports to recognise and use the updated client.

Don

[sathishbabu_gnanasambanda]

Sure, Thanks Don.

Will wait for tomorrow and hope the SP 32 will support the MSSQLOLEDB Driver for both the TLS 1.2 and the DateTime Format issue.

Thanks

Sathish

[former_member1264559]

Hi Don,

I'm trying to make sense of the Wiki but it's practically unreadable. Can you post a direct link to the SP32 downloads here, please as I'm going around in circles and I'm going blind with the different fonts and colours.