In addition to the above error message you may have also found that the SQLServerAgent service refuses to start. However I can almost guarantee that if you used SelfSSL to generate a self-signed SSL certificate, either to use with SSRS report manager or for some other purpose, chances are the below fix will work for you. Your situation maybe different and I can say from first-hand experience that there are a hundred different solutions suggested on a hundred different SQL forums on the internet. I spent 1.5 days trying to fix this on one of our databases and ultimately found this post which helped me solve the issue.
(provider: TCP Provider, error: 0 - The specified network name is no longer available.) (.Net SqlClient Data Provider). If you get the following error message when you try to connect to a SQL Server 2005 (maybe 2008?) database try the following fix.Ī connection was successfully established with the server, but then an error occurred during the pre-login handshake.
0 kommentar(er)
