Activity overview
Latest activity by larkbegin
The issue you encountered stems from the fact that version 4.2.20168 of your driver doesn’t recognize certain keywords in your connection string. Initially, you received an error for “trust server certificate” because that keyword (with spaces) isn’t supported in this version. Removing it led to another error for “multi subnet failover,” indicating that this parameter, too, isn’t supported. The certificate chain error then occurred because, without the ability to trust the server certificate explicitly, the connection process couldn’t bypass the SSL validation—the certificate was issued by an untrusted authority. The Stack Overflow discussion you mentioned pointed out that appending a correctly formatted trust parameter at the end of your connection string could resolve this. In your final working string, you removed the unsupported “Multi Subnet Failover=False” and changed “Trust Server Certificate=True” to “TrustServerCertificate=True” (without the spaces), like so: Here is code <p><ShadowConnectionString></p><p> Data Source=ip;Initial Catalog=Chuck2_Connect5;User ID=clu;Password=;Pooling=False;Encrypt=False;Authentication=SqlPassword;TrustServerCertificate=True</p><p></ShadowConnectionString></p> This adjustment works because the driver now correctly recognizes the keyword and bypasses the SSL certificate validation, allowing a successful connection. Essentially, you’ve aligned your connection string with the driver’s supported parameters, which is why this solution resolves the error. Lark from Profit Parrot
/ comments
The issue you encountered stems from the fact that version 4.2.20168 of your driver doesn’t recognize certain keywords in your connection string. Initially, you received an error for “trust server ...