Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cannot connect to SQL Server
See original GitHub issueOn my development machine EF successfully connecting to SQL Server, I’ve deployed the .NET 6 app with EF Core 7 on Windows Server 2012r2 and SQL Server 2014. Now I’m getting this error message:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
I’ve included TrustServerCertificate=True in connection string with no luck.
In server log I can see these errors:
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 1200.
A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 1202.
What can be the issue? Login and password are correct.
Issue Analytics
- State:
- Created 3 months ago
- Comments:27 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The issue will be fixed in the next update of CryptoPro CSP
yeah