How can we help you today? How can we help you today?
Steven_Cool
Activity overview Badges (0) Posts (0) Comments (2)

Activity overview

Latest activity by Steven_Cool

First Problem: You saw an error saying "Keyword not supported: 'trust server certificate'". To fix this, you removed Trust Server Certificate=True from your connection details. Second Problem: Then you got another error saying "Keyword not supported: 'multi subnet failover'". To fix this, you removed Multi Subnet Failover=False from your connection details. Third Problem: After that, you faced another error saying "Error connecting to database.. The certificate chain was issued by an authority that is not trusted." This means the system didn't trust the security certificate. Final Solution: You followed advice from a website and added Trust Server Certificate=True again at the end of your connection details. Now it worked! So, here is what your connection details should look like: <p><ShadowConnectionString>Data Source=ip;Initial Catalog=Chuck2_Connect5;User ID=clu;Password=;Pooling=False;Encrypt=False;Authentication=SqlPassword;TrustServerCertificate=True</ShadowConnectionString></p><div></div> This way, you should be able to connect without any problems. If you still facing any issue, then do let me know i'll try to figure out! / comments
  1. Community
  2. SQL Change Automation
  3. Keyword not supported: 'trust server certificate'.
First Problem: You saw an error saying "Keyword not supported: 'trust server certificate'". To fix this, you removed Trust Server Certificate=True from your connection details. Second Problem: The...
0 votes
To address the issues you're encountering with your connection string, let's break down the steps and provide a comprehensive solution. Problem Breakdown Initial Error: "Keyword not supported: 'trust server certificate'" Removed Trust Server Certificate=True Second Error: "Keyword not supported: 'multi subnet failover'" Removed Multi Subnet Failover=False Third Error: "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.)" Solution: Added Trust Server Certificate=True which made the connection work. Solution Explanation 1. Correcting the Keywords Based on the errors, the keywords used in your connection string need to be properly formatted. Specifically: Use TrustServerCertificate instead of Trust Server Certificate . Remove Multi Subnet Failover if it's not supported. 2. Updated Connection String The correct format should be: <p><ShadowConnectionString></p><p>&nbsp; &nbsp; Data Source=ip;Initial Catalog=Chuck2_Connect5;User ID=clu;Password=your_password;Pooling=False;Encrypt=False;TrustServerCertificate=True;Authentication=SqlPassword;</p><p></ShadowConnectionString></p> Steps to Resolve the Issue Correct the Connection String Syntax: Ensure there are no spaces in TrustServerCertificate . Remove Multi Subnet Failover if it's not supported or necessary. Trusting the Server Certificate: Setting TrustServerCertificate=True instructs the SQL client to trust the server's certificate without validating it against a trusted certificate authority. This is useful in development or testing environments but should be used with caution in production. Using Proper Authentication: Ensure that the User ID and Password are correct. The Authentication=SqlPassword setting is used for SQL Server authentication. Complete Corrected Connection String Here is the corrected connection string based on the provided information: <p><ShadowConnectionString></p><p>&nbsp; &nbsp; Data Source=ip;Initial Catalog=Chuck2_Connect5;User ID=clu;Password=your_password;Pooling=False;Encrypt=False;TrustServerCertificate=True;Authentication=SqlPassword;</p><p></ShadowConnectionString></p> Additional Considerations Security: Using TrustServerCertificate=True bypasses the validation of the server's SSL certificate. This can expose your connection to security risks, such as man-in-the-middle attacks. For production environments, it is recommended to use a trusted certificate issued by a recognized certificate authority. Password Management: Ensure that your password is securely managed and not hardcoded in the configuration files. Summary Correct the keywords in the connection string (TrustServerCertificate ). Remove unsupported keywords (Multi Subnet Failover ). Ensure the connection string is properly formatted and secure. If you follow these steps, your connection string should work correctly without the errors you encountered. If you need further assistance, feel free to ask! / comments
  1. Community
  2. SQL Change Automation
  3. Keyword not supported: 'trust server certificate'.
To address the issues you're encountering with your connection string, let's break down the steps and provide a comprehensive solution.Problem Breakdown Initial Error: "Keyword not supported: 'tr...
0 votes
Total activity
3
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
1