SQL Sever connection failure -- SQL Sever remote process call failed, sqlsever

SQL Sever connection failure -- SQL Sever remote process call failed, sqlsever

Today, I started three layers of learning with great enthusiasm. I watched the video and knocked on the code. I felt like I hadn't knocked on the code for a long time, and my hands were a little new ...... The code is finally knocked out, and the database is to be created, and then the problem arises. My database was installed by reinstalling the system before returning home during the winter vacation. At that time, I connected the database and didn't use it again ...... Click again to see the problem.

I thought this problem was not very difficult. I used to check the configuration tool if the database could not be connected when I was in the data center ...... When I went there, there was nothing.

I did not directly address the problem of Baidu, but Baidu's database could not connect to the server:

Http://zhidao.baidu.com/link? Url = Response

According to Baidu, I did it, but I don't know where the system service is. I asked Juan's sister, who said it should be in the local policy, however, we all forget the commands of the local policy, So Baidu

Http://jingyan.baidu.com/article/49711c6148c372fa441b7c13.html

However, the SQL System Service is not in the local policy, followed by Baidu. We found it in the management tool-service-(service ).

Then it is automatically changed to manual.

Then, follow Baidu to check whether the network configuration of SQL Server is enabled.

Now it is time to solve the remote process call failure problem:

This problem occurs because the "Microsoft SQL Server 2012 Express LocalDB" service is automatically installed when Visual Studio2012 is installed, resulting in the failure of the original SQL2008. The solution is as follows:

I,

Open the control panel, find the program-> uninstall the program, unmount "Microsoft SQL Server 2012 Express LocalDB", and then open the SQLServer Configuration Manager. It shows that everything is normal and OK.

II,

Upgrade SqlServer2008R2 to SP1 or SP2. Http://www.microsoft.com/zh-cn/download/details.aspx? Id = 30437

 

All the problems have been solved. Then, let's take a look at the configuration tool and restore it to the familiar way ......

Connect the database again!

Summary: If you don't understand it, we need to check it step by step. I once again realized that there are always more problems with the methods of teacher Mi! In addition, we need to develop the habit of backing up data. We should not simply trust any one of them, so that multiple backups can prevent file loss and damage. Also, do not always think about how to solve the problem. In different situations, the cause of the problem is different. We must be good at solving the problem.