SQL Integration v18

[navarro3_16]

Hi

We did an integration between 3cx and our MSSQL database.

In version 16 the integration worked without any problem. This weekend we update to version 18 and it began to give the error that I attach in the image.

Do you know what could be happening? We have SQL 2014 and also the integration stopped working since the update was made

 

[edossantos]

This is a connection problem. In 3CX v18 only TLS 1.2 is allowed, and this causes that old databases not supporting this protocol can't get connected. You will need to upgrade your database, also due to security reasons, the TLS protocol that you were using is now considered unsecure.

 

[Evolute IT]

This is a connection problem. In 3CX v18 only TLS 1.2 is allowed, and this causes that old databases not supporting this protocol can't get connected. You will need to upgrade your database, also due to security reasons, the TLS protocol that you were using is now considered unsecure.

Hi

We did an integration between 3cx and our MSSQL database.

In version 16 the integration worked without any problem. This weekend we update to version 18 and it began to give the error that I attach in the image.

Do you know what could be happening? We have SQL 2014 and also the integration stopped working since the update was made

I believe there was an update once for SQL 2014 to support TLS 1.2, and it was also for SQL 2016.

Otherwise, I strongly recommend upgrading anyway and probably your OS as well if it's under 2016.

Windows Server and SQL Server came a long way since 2014!

 

[navarro3_16]

In these days I upgraded to Windows Server 2016 and SQL Server 2016. I also activated the TLS 1.2 protocol and it keeps giving the error.

Any other idea what it might be?

 

[edossantos]

In these days I upgraded to Windows Server 2016 and SQL Server 2016. I also activated the TLS 1.2 protocol and it keeps giving the error.

Any other idea what it might be?

This is definitely an issue with the version of TLS supported by the database server. Here another user reports that upgrading SQL Server to 2019 fixes the issue:
https://www.3cx.com/community/threads/3cx-with-mssql-crm-connection.84749/