SQL Server Service Remote process call failed, SQL Server call

SQL Server Service Remote process call failed, SQL Server call

Due to the need for a unified vs version for the development system, after a hard and arduous struggle all day yesterday, xiaobian finally succeeded in writing in the 13 version of vs and re-installed the 12 version of, I was thinking that the 12 version of vs was successfully built, so I quickly set up the framework, and then knocked on the example. However, Tianyi was confused, and the small series of databases could not be magically opened. After half a day of Baidu, the answer to the question gradually emerges. Next, I will briefly introduce how to solve the problem of SQL Server Remote process call failure, open SQL, and connect to the Server. The following problems may occur:

The first method is as follows:

This problem occurs in the form of a familiar joke, nie. As early as September 1, 2014, Xiao Bian had already had a relationship with this problem, for details, please refer to the link for network-related or instance-specific errors when establishing a connection with SQL Server, so xiaobian follows the steps of the last solution to start solving the problem, however, despite the same error, it may not be caused by the same reason, so xiaobian started a journey to Baidu. Next, let me share with you how to solve the failure of SQL Server Remote Process calling. Maybe this computer has installed visual studio 2013, the built-in SQL server 2012 conflicts with it, resulting in a new version of 2008 R2 being too low. The following error occurs:

 

Strange: all services have been lost before, And the monsters have been taken away. Joke '(* prop _ prop *)' and check it online, this is because SQL Server2008 and VS2012 coexist. When these two things are the same on your computer, SQL will happen. Solution: Find "Microsoft SQL Server Expres 2012LocalDB" on the control panel or other auxiliary software to uninstall it, as shown in:

After uninstalling the SQL Server instance, refresh it again and click "SQL Server service". For example, start the stopped SQL Server (MSSQLSERVER) in the second red line. As shown in:

So far, many small partners' problems should be solved. Some small partners may encounter new problems after starting SQL Server (MSSQLSERVER) due to RP. For example:

You can view the windows Log File (view the log file) to see that the port is occupied, and it is easy to solve this problem, you only need to disable the last three of SQLEXPRESS services to ensure that only one startup is enabled at a time. The problem is finally solved. As follows:

Then, open the database and you will be able to connect to it. In addition to the above solution, Xiaoqiang also briefed the partner on two solutions:

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

The third method is to manually start the database service item.
The method is as follows:
Right-click "computer"> "management"> "service", find SQL Server (MSSQLSERVER), right-click, and select "start ". At this time, there will be no problem logging into the database, but after the system is restarted, the problem will still exist.

Note:This blog post briefly introduces how to solve the problem of SQL server Remote process call failure. Finally, I understand that the farthest distance in the world is not between life and death, but you sit in front of the computer, but you cannot connect to the database. It's not terrible to have a problem. What's terrible is that we are put into our hearts by seemingly simple things, it may take us half a day to solve a simple problem, but the joy and pleasure of solving the problem is even better than eating white rabbit milk sugar when I was a child. project development, to be continued ......