Workaround for "Remote Procedure call failed" "0x800706be" appears in SQL SERVER R2 Configuration Manager

When SQL Server 2008 was not able to log in before, it was always changed by "Computer Management" → "SQL Server service", "SQL Server (MSSQLSERVER)". But now the problem has become the SQL Server service cannot open the situation, it is depressed.

Through the online check, just know because SQL Server2008 and VS2012 coexistence problem, when your computer installed both of these two things, SQL will appear in the situation.

Workaround: Find "Microsoft SQL Server expres 2012LocalDB" from the control Panel or other auxiliary software to uninstall it.

After uninstalling, refresh again, the SQL Server service comes out, for example, and then follow the second red box in the start of a stopped SQL Server (MSSQLSERVER).

So far, a lot of people should be able to solve the problem, it may be the reason for my RP, when I started SQL Server (MSSQLSERVER), there are new problems. Specific example:

By looking at the Windows log file (the way to view the log file) you can see that the reason for the port is occupied, it is easy to solve this problem, just need to turn off the SQLExpress service in the next three, to ensure that only one boot on each boot is good. The problem has finally been solved.

Workaround for "Remote Procedure call failed" "0x800706be" appears in SQL SERVER R2 Configuration Manager