SQL Server service Remote Procedure call failed

Due to the development of the system, need vs version unification, so after a day of arduous struggle yesterday, the small part finally succeeded in writing in the 13 version of VS, the 12 version of VS, originally thought, 12 version of the VS build success, quickly set up the framework, and then hit the example, but Providence to get people, Small compilation of the database magically can't open, and after a half-day Baidu, the answer gradually surfaced, the next small part of the simple introduction of how to solve the SQL Server service remote procedure call failure problem, open SQL, connection, there is a problem:

The first method, as shown below

This problem, small series swollen is a familiar bright Nie, originally as early as September 1, 2014, the small series has been and this problem has been one side, details please see links in connection with SQL Server network-related or instance-specific errors occur , So the small part of the pace of the last solution, began to solve the problem, but Providence to get people, although the same mistake, but not necessarily the same cause, so small series began a section of Baidu Road. Next, I will share with you how to resolve the SQL Server service remote procedure Call failure resolution, small series dragged the gills think, maybe this computer before the installation of Visual Studio 2013, built-in SQL Server 2012 conflicts with it, causing the new R2 version to be too low. The error appears as shown:

Strange, before all the services are gone, was taken by the monster, joking ' (*∩_∩*), 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, as shown in:

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). As shown in the following:

So far, a lot of small partners should be able to solve the problem, there may be some small partners because of the RP, when the start of SQL Server (MSSQLSERVER) 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. As shown below:

Then, open the database, you can connect to Oh, out of the above solution, the small force also to small partners to briefly introduce two solutions:

The second option is to upgrade the database
Use a later version of the database, or upgrade SqlServer2008 to SP1 or SP2.

The third method is to manually start the database service entry
Here's how:
Right-click computer → administration → services, locate SQL Server (MSSQLSERVER), right-click, and select Start. There is no problem logging into the database at this time, but after restarting the system, the problem will persist.

Small Series of words: The blog, the small part of the main simple introduction of the SQL Server service remote procedure call failed to solve the problem, finally understand that the world's furthest distance is not life and death, but you sit in front of the computer but not even the database, there are problems, not scary, What is scary is that we are seemingly simple things our hearts, may solve a simple problem will take us a half-day time, but the problem solved the kind of joy and joy, than a child to eat big white rabbit toffee also happy, project development, not to be continued ...

SQL Server service Remote Procedure call failed