Sidd's SQL Solution

Hi All, and welcome back. As the computing power and networking is increasing day by day so is the need of more safer and stronger encryption channel methods and algorithms. And we want our databases and database server to use the same as well. But sometimes implementing them may cause undesired results like SQL Server not coming online. In case you’re also facing the same issue or planning to adopt new TLS standards like TLS 1.2 and don’t want to such problems then you should go through this post. Problem: We may require to make changes like enabling higher level cipher suite TLS 1.2 and disable TLS 1.0 for better security of our servers. But in case you make this changes it can be possible that after restart the SQL Services refuse to come online and fails. If you check the SQL Server error logs you’ll get the below errors: Error: 17182, Severity: 16, State: 1. TDSSNIClient initialization failed with error 0x139f, status code 0x80. Reason: Unable to initialize SSL sup...

So, it is a nice fine day and you’re in office doing your BAU. You got this new task of installing SQL Cluster (which you’ve probably done several times before) and after making all necessary arrangements and planning you started it. All went fine and then when the setup is almost done you got this strange error “Wait on the Database Engine recovery handle failed.” which ruins the rest of your day. No worries we are here to sort this out quickly for you. Problem Now the problem here is that SQL Server setup is able to install all the components but is failing for DB engine (and its group). You get the error pop-up stating the below error: “Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.” It may also give some link, which unfortunately (may) not lead you to anywhere. And at the end your see crosses against DB engine and its dependent components. Let me first tell you that why you got this error. In every SQL ...