Search results
17 gru 2021 · While setting TrustServerCertificate=True or Encrypt=false in the connection string is a quick fix, the recommended way of solving this issue is to provide a proper certificate for your SQL Server from a trusted CA.
11 lip 2024 · When connecting to SQL Server, you may receive the following error message: A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) (.Net SqlClient Data Provider)
19 lut 2023 · A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) (Microsoft SQL Server, Error: -2146893019)
1 maj 2017 · You likely don't have a Certificate Authority (CA)-signed certificate installed in your SQL VM's trusted root store. If you have Encrypt=True in the connection string, either set that to off (not recommended), or add the following in the connection string (also not recommended): TrustServerCertificate=True.
17 sty 2024 · When your client fails to validate the server certificate, you see the following error message in the client application: System.Data.SqlClient.SqlException: A connection was successfully established with the server, but then an error occurred during the login process.
24 mar 2024 · W tym artykule opisano problem występujący podczas uaktualniania aplikacji SNAC 11.0 do użycia sterownika OLE DB firmy Microsoft 19 dla SQL Server lub sterownika Microsoft ODBC 18.x dla SQL Server.
29 lip 2020 · Import error: 0x2, Windows Native Error: 0x80092004. The selected certificate does not contain server authentication key usage property. This property required to import certificate to SQL Server. Actually I have configured the CN the same as my node FQDN, and 'Contoso-DC-CA' was the issuer's name, below is the CheckSQLSSL tool running result ...
