Can't get SQL Server to start or connect to my local database engine through SSMS

Question

SQL Server has been working fine but since Friday I have not been able to connect to the database engine in SSMS. This coincided with my having to power the laptop off durin

Answer 1

Just saw this post, in short, you will need to apply the Service packs and the cumulative updates for it to work, on newer operating systems the SSL certificates are being changed to disable SSL2, SSL3, etc. using the newer TLS1.2 and SQL Server is not supporting it out of the gate, you need to apply the patches to enable its support and it will work again.

Answer 2

A colleague into a similar problem - with pretty much the same error log. Turned out the root cause was his attempt to install SQL server on a domain controller using a system account. If you MUST install SQL server on domain controller, let SQL server service run under a network account. https://support.microsoft.com/en-us/kb/2032911

Answer 3

Your error seems to have to do with the certificate you installed.

This article suggests changing the service the SQL server will log in as, you can do this at install, or via the surface configuration management tool.

http://social.msdn.microsoft.com/Forums/en-US/sqlsecurity/thread/56f14665-3f00-41ff-b002-bb5e86b3f219/

Answer 4

BACKUP YOUR REGISTRY

---

THIS IS ONLY AN OPTION - AND GENERALLY A LAST RESORT - WEIGH THE CONSEQUENCES ON YOUR OWN

DO NOT TAKE THIS ADVICE AS THOUGH I HAVE SEEN YOUR REGISTRY AND KNOW THE EXACT STATE OF YOUR MACHINE

---

In short, the very first error you're seeing:

2013-03-05 12:17:41.87 spid12s Error: 17190, Severity: 16, State: 1.

2013-03-05 12:17:41.87 spid12s Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.

is surrounding issues with keys that already exist in your registry. So, do what I said first, backup your registry, and then delete the key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

and then try to reinstall Microsoft SQL Server 2012. If this doesn't work - you're probably going to need to backup your machine data and rebuild it.

Answer 5

I know it's probably too late to help with the original poster, but we had this same issue and nothing we tried resolved the problem. Finally, we opened a technical incident with Microsoft and this is the solution that we were provided:

• Take backup of below registry key.

HKLM\SOFTWARE\Microsoft\Cryptography\MachineGuid This key should ideally have the GUID of the machine without curly braces, so {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} becomes xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

• Then delete the braces.
• Try to reboot and start the SQL service . If service don’t start then Uninstall and reinstall SQL.

The above solution worked on two separate machines exhibiting this problem.