SQL Server Remote call failed

This article mainly introduces a workaround for the SQL Server service to show that the remote procedure call failed, and also provides a solution to resolve the "Remote Procedure call failed" (0X800706BE) error prompt in SQL Server R2 Configuration Manager. Interested in the small partners can refer to

Just opened SQL Server 2008, want to create a new database, but found that there is a problem, this problem because have not encountered before, so the following troubleshooting SQL Server service Remote call failed several methods, for your reference, the specific content is as follows

First look at the problems that arise:

The reason for this error may be because we are loading VS2012 or other versions, this vs will automatically install the "Microsoft SQL Server expresslocaldb" service, resulting in SQL server2008, The SQL Server service shows that the remote procedure call failed. Knowing the cause of the other is pretty straightforward.

First: Adopt a gentle way

obediently Upgrade your database to a higher version.

Second: Just a moment .

If you use this database only once, go to the computer → manage → service, find the service to open SQL Server (MSSQL server) to start is OK.

Third: not on

Of course, life, you have to learn not to, because the teacher said: not will be the driving force of discovery. So, in order to use the normal use every time, can only be wronged "Microsoft SQL Server (EXPRESSLOCALDB)" This service, fish and bear cake can not be combined. So go to the control panel decisively find this automatic installation of the service, to uninstall it, there is no big impact on vs. After uninstalling, then turn on the required services under the SQL Server service.

Then again,vs why to automatically install "Microsoft SQL Server (expresslocaldb)", the baby really do not know, but look at the surface meaning, should be a local database or something??? Baidu told me:VS2012 provides a local database engine "Microsoft SQL Server expresslocaldb", through VS2012 can easily manage and use the local database .

And then we'll share another set of solutions for SQL SERVER R2 Configuration Manager "Remote Procedure call failed" (0X800706BE) error prompt :

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.

The above is the entire content of this article, I hope to help everyone to successfully resolve the SQL Server service display remote procedure call failure problem.

SQL Server Remote call failed