Skip to Content
May 17, 2022 at 09:19 PM

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

1487 Views Last edit May 18, 2022 at 03:13 PM 2 rev

Hi Team,

I am using the CR Runtime Engine (CR Runtime 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 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.