We have some applications connecting both to a MySQL DB and to a SQL Server DB. After upgrade from 9.9.014 to 9.10, we had to modify the parameters of the SQL Server connection made with the MS SQL Server NATIVE SRV driver, adding options “Encrypt” and “trustServerCertificate”, to avoid a certificate error.
We have blank applications that make use of both MySQL and SQL Server connections. For each sc_lookup() and sc_exec_sql() macro call, we specify the connection that has to be used. So, the default connection selected in ScriptCase for the application in the “SQL” menu, was totally irrelevant.
BUT…
Now, if the SQL Server connection has been selected as the default in the SQL option of the editor, everything works fine, while if the default connection of the blank application is the MySQL one, we get again the certificate error (in italian) on the SQL Server connection:
Si è verificato un errore durante la connessione al database:
SQLState: 08001 Error Code: -2146893019 Message: [Microsoft][ODBC Driver 17 for SQL Server]Provider SSL: Catena di certificati emessa da una Autorit� di certificazione non disponibile nell’elenco locale. SQLState: 08001 Error Code: -2146893019 …
It seems that the default connection makes use of all the security parameters specified, while when we use the SQL Server connection as “secondary”, it doesn’t read the security settings.
For blank applications, this is not a problem: we can set the SQL Server connection as the default. But we also have a Grid set up on MySQL fields, with a Run button working on the SQL Server DB. This button returns the certificate error, and we cannot change the default connection.
Thank you