Shulou(Shulou.com)05/31 Report--

What this article shares with you is the solution to the failure of remote procedure calls displayed by SQL server services. The editor thinks it is very practical, so I share it with you. I hope you can get something after reading this article. Let's take a look at it.

Just opened SQL Server 2008, want to create a new database, but found a problem, this problem has not been encountered before, so here are several methods to solve the failure of remote invocation of SQL server services, the details are as follows

Let's take a look at the problems:

The reason for the above error may be that when we install VS2012 or other versions, the VS will automatically install the "Microsoft SQL Server 2013 (2012) ExpressLocalDB" service, which causes the remote procedure call to be displayed by the SQL server service in SQL server2008. Knowing the reason, it's pretty easy to solve the rest.

First: in a gentle way

Obediently upgrade your database to a higher version.

Second: make do with it.

If you only use the database this time, go to the computer → to manage the → service, and find the service SQLserver (MSSQL SERVER) to start OK.

Third: don't make do with it.

Of course, in life, you have to learn not to make do with it, because what teacher Mi said: no will be the driving force of discovery. Therefore, in order to use it normally every time, we can only be aggrieved by the "Microsoft SQL Server 2013 (2012) ExpressLocalDB" service. We can't have both. So go to the control panel and decisively find the auto-installation service and uninstall it. It won't have a big impact on VS. After uninstalling, then open the required services under the SQL server service.

Then again, why does VS automatically install "Microsoft SQL Server 2013 (2012) ExpressLocalDB"? the baby really doesn't know, but on the surface, it should be a local database or something. Baidu told me that VS2012 provides a local database engine "Microsoft SQL Server 2013 (2012) ExpressLocalDB", which makes it easy to manage and use local databases through VS2012.

Let me share with you another solution to the "remote procedure call failure" (0x800706be) error message in SQL SERVER 2008 R2 configuration Manager:

In the past, when SQL Server 2008 could not log in, it was always changed through "computer Management" → "SQL Server Service", "SQL Server (MSSQLSERVER)". But now the problem has become the SQL Server service can not be opened, it is very depressing. As shown in the figure:

Through the online search, we know that it is because of the coexistence of SQL Server2008 and VS2012. When you have the same fashion in your computer, SQL will appear in the picture above.

Solution: find "Microsoft SQL Server Expres 2012LocalDB" in the control panel or other auxiliary software to uninstall it. As shown in the figure:

After uninstalling, refresh it, and the "SQL Server service" will come out, as shown in the following figure, and then start the stopped SQL Server (MSSQLSERVER) according to the second red wireframe in the following figure.

At this point, many people's problems should be solved, probably because of my RP. When I started SQL Server (MSSQLSERVER), there was a new problem. The details are as follows:

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, and it is also easy to solve this problem. You only need to turn off the last three of the SQLEXPRESS service to ensure that there is only one startup per startup. The problem is finally solved.

The above is the solution to the failure of remote procedure calls shown by SQL server services. The editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.