Тёмный

Uncover the Secret to Solving That "Trust Server Certificate Connection Error" in Azure Data Studio! 

SQL Server 101
Подписаться 17 тыс.
Просмотров 7 тыс.
50% 1

You may see a Connection error in Azure Data Studio. How can you resolve it?
My SQL Server Udemy courses are:
70-461, 70-761 Querying Microsoft SQL Server with T-SQL: rebrand.ly/que...
98-364: Database Fundamentals (Microsoft SQL Server): rebrand.ly/dat...
70-462 SQL Server Database Administration (DBA): rebrand.ly/sql...
Microsoft SQL Server Reporting Services (SSRS): rebrand.ly/sql...
SQL Server Integration Services (SSIS): rebrand.ly/sql...
SQL Server Analysis Services (SSAS): rebrand.ly/sql...
Microsoft Power Pivot (Excel) and SSAS (Tabular DAX model): rebrand.ly/mic...
----
In this video, we'll show you how to solve the "trust server certificate connection error" in Azure Data Studio!
This problem can occur when you're trying to connect to a server using a certificate that was issued by an authority that is not trusted. We'll show you how to identify and solve this problem using Azure Data Studio!
When you are in Azure Data Studio, and you create a new connection to an on premises SQL Server or SQL Server on a Virtual Machine, you may receive the following error:
A connection was successfully 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.)
Encryption was enabled on this connection, review your SSL and certificate configuration for the target SQL Server, or enable "Trust server certificate" in the connection dialog.
Note: A self-signed certificate offers only limited protection and is not a recommended practice of production environments. Do you want to enable "Trust server certificate" on this connection and retry?
There are two ways to resolve this error:
1. If the SQL Server you are connecting to is in a production environment (in other words, it is a licensed Enterprise or Standard SQL Server installed on a Windows Server at work), then ideally the administrator of that SQL Server would ideally install a certificate from a trusted certificate authority. Then, this error would not occur.
2. If the SQL Server you are connecting to is not in a production environment (such as SQL Server Developer or Express on your computer), then you should click "Enable Trust server certificate", or change "Trust server certificate" to True.
----
Links to my website are:
70-461, 70-761 Querying Microsoft SQL Server with T-SQL: idodata.com/que...
98-364: Database Fundamentals (Microsoft SQL Server): idodata.com/dat...
SQL Server Essential in an Hour: idodata.com/sql...
70-462 SQL Server Database Administration (DBA): idodata.com/sql...
DP-300: Administering Relational Databases: idodata.com/dp-...
Microsoft SQL Server Reporting Services (SSRS): idodata.com/mic...
SQL Server Integration Services (SSIS): idodata.com/sql...
SQL Server Analysis Services (SSAS): idodata.com/sql...
Microsoft Power Pivot (Excel) and SSAS (Tabular DAX model): rebrand.ly/mic...
1Z0-071 Oracle SQL Developer - certified associate: idodata.com/iz0...
SQL for Microsoft Access: idodata.com/sql...
DP-900: Microsoft Azure Data Fundamentals: idodata.com/dp-...

Опубликовано:

 

3 окт 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 9   
@shailendrarai4525
@shailendrarai4525 3 месяца назад
You are great, your tip helped me and it saved my lot of time. Thank you.
@samirgurbanov113
@samirgurbanov113 Год назад
Super. I had another problem but I've found solution here. Thanks
@timusius
@timusius Год назад
When editing job steps in the SQL agent, the dialog does not have any way of setting "trust server certificate". It's like it uses it's own connection with default "NOT trusting the server certificate", and not the same options that was used to log into the server. Because of this it blocks any use of the SQL Agent. This must clearly be a bug in SSMS, or is there some work around that I have overlooked?
@SQLServer101
@SQLServer101 Год назад
Hi Timus. Thank you for your question. I'm afraid I don't know of any such workaround. Please have a look at learn.microsoft.com/en-us/troubleshoot/sql/database-engine/connect/error-message-when-you-connect for more details. Phillip
@RobertEdwards1974
@RobertEdwards1974 7 месяцев назад
Is there a way to make this a default option? Always trust the certificate when we create a new connection?
@SQLServer101
@SQLServer101 7 месяцев назад
Hi Robert. Thank you for your question. I don't think so - and that could be dangerous, so I assume you can't. Phillip
@abdikahiye3781
@abdikahiye3781 8 месяцев назад
Its still showing me error ,"login failed for user"😢
@SQLServer101
@SQLServer101 8 месяцев назад
Hi Adbikahiye. Thank you for your question. There might be another reason for the failure. Phillip
@abdikahiye3781
@abdikahiye3781 8 месяцев назад
@@SQLServer101 Microsoft SQL error 18456 is what am experiencing pls any help and its not the authentication mode ,the problem is server type . When the server mode is on Analysis services it accepts but When the server mode is on Database Engine this error occurs 😢 🙏
Далее
Azure Data Studio Features in 20 Minutes
18:54
Просмотров 37 тыс.
Solving one of PostgreSQL's biggest weaknesses.
17:12
Просмотров 198 тыс.
SQL Server Error 40: Named Pipes Provider
7:30
Просмотров 50 тыс.