1 回答
- 最新
- 投票最多
- 评论最多
2
According to error, there is a certificate mismatch between the server name and the alternative names listed in the certificate.
To resolve this issue, you can try the following steps:
- Check the certificate to make sure it is valid and has the correct alternative names listed.
- Ensure that the server name is correct and matches the name listed in the certificate.
- If the certificate is not valid or does not have the correct alternative names, update or replace the certificate.
- If the server name has changed, update any references to the old name with the new name.
- Check the network configuration to ensure that there are no issues with DNS resolution or routing that could be causing the error.
已回答 1 年前
It would be helpful if you gave the exact library that you're referring to. For .NET code in Lambda, typically people are using either the older System.Data.SqlClient (max version 4.8.5) or the newer and recommended package Microsoft.Data.SqlClient (max version 5.1.0). There's an entity framework core package Microsoft.EntityFrameworkCore.SqlServer (max version 7.0.3) and the older Entity Framework 6 package EntityFramework (max version 6.4.4).
Since none of these are available in version 9.1.0, it's not clear exactly what library you're using. Are you possibly using the magic.lambda.mssql library? Or something else?
Hi , The lambda is written in Node.js and we have package.json file were the packages required and its dependencies mentioned . Based on a security vulnerability reported for dependency package(xmldom) we had to upgrade the MSSQL package in Visual Studio Code from Version 6.2.0 to Version 9.1.1 which is leading to the above error . We dont have the sql server connection error in lambda when the MSSQL version is 6.2.0. The mentioned versions are Npm MSSQL versions