SQL Server service displays a workaround for remote procedure call failure _mssql

Just opened SQL Server 2008, want to create a new database, but found a problem, the problem because it has not been encountered before, so the following is a solution to solve the SQL Server service remote Call failure of several methods for your reference, the details are as follows

Let's look at the problems that arise:

The reason for this error may be that when we install VS2012 or other versions, this vs will automatically install the Microsoft SQL Server 2013 EXPRESSLOCALDB Service, resulting in SQL server2008, The SQL Server service in is displaying a remote procedure call failure. Knowing the reason to solve the other is quite simple.

First: Adopt a gentle way

obediently upgrade your own database to a higher version.

Second: Just a little bit .

If you use this database only once, go to the computer → admin → service, find the service that you want to open to the server (MSSQL server) to start OK.

Third: not to be

Of course, life, you have to learn not to do, because the teacher said: not will be the driving force of discovery. So, for every use can be normal use, can only wronged "Microsoft SQL Server 2013 () expresslocaldb" This service, fish and bear cake can not be both. So go to the control Panel to find this automatically installed service, to uninstall it, not a big impact on vs. After uninstalling, you can then turn on the services that are required under SQL Server services.

In other words,vs Why to automatically install "Microsoft SQL Server 2013 (s) expresslocaldb", the baby really don't know, but look at the surface, it should be a local database or something??? Baidu told me:VS2012 provides a local database engine, Microsoft SQL Server 2013 expresslocaldb, which makes it easy to manage and use the local database through VS2012 .

And then we'll share another set of solutions SQL SERVER 2008 R2 Configuration Manager appears with the remote Procedure call failure (0X800706BE) error prompt :

When SQL Server 2008 was not logged 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 can not open the situation, is very depressing. As shown in figure:

Through the Internet, we know that because of the coexistence of SQL Server2008 and VS2012, when you installed these two things in the computer, SQL will appear in the picture above.

Workaround: find "Microsoft SQL Server expres 2012LocalDB" from the control Panel or other assistive software to uninstall it. As shown in figure:

After uninstalling, refresh again, the SQL Server service comes out, the following figure, and then start the stopped SQL Server (MSSQLSERVER) by following the second red line in the following figure.

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

By looking at the Windows log file (the method of viewing the log file) you can see that it is because the port is occupied, it is easy to solve this problem, just to turn off the back three of the SQLExpress service, to ensure that only one boot per boot is good. The problem has finally been solved.

This is the full content of this article, I hope to help you successfully resolve the SQL Server service display remote procedure call failure problem.