Hi Gustavo,
thank you, this looks very interesting and i will this give a try at first.
The Clarion support at [email protected] suggested another approach, but i only try that one, when i am really not successful after all.
Ralph
Hello Tim,
thank you for this reply.
In the meantime Gustavo Saracca posted on clarionhub an interesting reply, that uses libcurl .
As curl (my Version is 8.9.1 ) supports many protocols, i will give this a try at first.
best regards from Germany
Ralph Rathmann
Am 08.11.2024 um 17:37 schrieb [email protected]:
> Ralph,
>
> As far as I know TLS 1.2 is supported (and has been for a while). I will ask the Dev Team for details about how to enable it but it may be that it has to be specifically enabled on the OS (for at least some versions/installs of Windows)
>
> Here is a post/thread from a while back. It is specific to MSSQL but some of the implementation details may apply.
>
> Robert(Support)
>
> > changing the MSSQL protocol from TLS 1.0 and TLS 1.1 up to TLS 1.2. They are experiencing problems and the
> > Clarion app can’t establish a connection with MSSQL.
> —
> I had a similar problem with a new installation of a SQL Server 2019, and at that time noticed that Bruce J had described that issue as well on Clarionhub.com at
> Bug in ODBC SQL Server and OLEDB driver on Windows server 2016 when connecting to SQL Server 2019 running on Windows Server 2022 Error 772 or 18 SSL Security Error
>
> Bruce solved it by re-enabling TLS 1.0; however, I resolved the issue by installing the latest Microsoft SQL Native Driver on the client servers running our application. Although our app wasn’t using the actual native driver in the connection string, the update still fixed the connectivity for OLEDB.
> You can download the driver here_
> https://www.microsoft.com/en-us/download/details.aspx?id=50402 .
>
> Of course the client will still need to have TLS 1.2 enabled on the OS level. By default, that should be the case in any of the currently supported Windows OS versions. On the Window Server, you can check it with Nartac Software’s IIS Crypto tool → Client Protocols ( these settings are just the registry values).