Microsoft SQL: A connection was successfully established with the server, but then an error occurred

[LucianoS]

Estimados usuarios, he recurrido al foro porque creo que estoy en un problema que para mi es bastante grande, el dia de hoy intente  ingresar a mi sql server management studio v18.4 una nueva base de datos, a la cual queria importar un archivo excel, al darme un error, instale un Microsoft Access Database Engine 2016 Redistributable, logre subir el excel pero al momento de actualizar el reporte y de esta manera tambien descargar el excel desde el Powerbi (como tablas) tengo el  siguiente problema: Microsoft SQL: A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - La cadena de certificación fue emitida por una entidad en la que no se confía.)

No tengo problemas para conectarme desde Sql server management studio, pero sí desde powerbi al momento de actualizar.

 Creo que al instalar el Microsoft Access Database Engine 2016 Redistributable, me elimino el certificado.. o algo así, no soy expero pero necesito us ayuda porfavor!

 

[goransvaland]

Reinstall Power BI Desktop solved this error message.

[v-luwang-msft · Accepted solution]

HI @LucianoS ,

If you're getting this error after January 2022, possibly after migrating from System.Data.SqlClient to Microsoft.Data.SqlClient or just updating Microsoft.Data.SqlClient to version 4.0.0 or later, it's because MS has introduced a breaking change::

https://docs.microsoft.com/en-us/sql/connect/ado-net/introduction-microsoft-data-sqlclient-namespace...

Breaking changes in 4.0

Changed Encrypt connection string property to be true by default.

The default value of the Encrypt connection setting has been changed from false to true. With the growing use of cloud databases and the need to ensure those connections are secure, it's time for this backwards-compatibility-breaking change.

Ensure connections fail when encryption is required

In scenarios where client encryption libraries were disabled or unavailable, it was possible for unencrypted connections to be made when Encrypt was set to true or the server required encryption.

Rick Strahl has posted a detailed explanation on his blog

The change was made in this SqlClient pull-request in August 2021, where there is additional discussion about the change.

The quick-fix is to add Encrypt=False to your connection-strings.

Similar question refer:

https://stackoverflow.com/questions/17615260/the-certificate-chain-was-issued-by-an-authority-that-i...

Did I answer your question? Mark my post as a solution!

Best Regards

Lucien