The SQL server service shows the solution to the remote process call failure, sqlserver

The SQL server service shows the solution to the remote process call failure, sqlserver

I just opened SQL Server 2008 and wanted to create a new database, but I found a problem. This problem has not been encountered before. So I will sort out several methods to solve the remote call failure of SQL server, for your reference, the specific content is as follows:

First look at the problem:

The cause of the above error may be that when we install VS2012 or another version, this VS will automatically install the "Microsoft SQL Server 2013 (2012) ExpressLocalDB" service, therefore, the SQL server service in SQL server shows that the remote process call failed. It is quite easy to solve the problem by knowing the cause.

First:Gentle approach

Upgrade your database to a later version.

Second:Just a moment

If you only use this database once, go to the computer → manage → service, and find the SQLserver (mssql server) Service to be enabled to start it.

Third:No

Of course, if you live your life, you have to learn not to do it, because "no" is the motive force behind discovery. Therefore, in order to be able to use the service normally every time, we can only grievance the service "Microsoft SQL Server 2013 (2012) ExpressLocalDB", and the fish and the bear's paw cannot have both sides. So go to the control panel to find the automatically installed Service and uninstall it. It has no major impact on. After uninstallation, enable the services required under the SQL server service.

Now,Why does VS automatically install "Microsoft SQL Server 2013 (2012) ExpressLocalDB ",The baby really does not 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 (2012) ExpressLocalDB". Through VS2012, you can easily manage and use local databases..

I will share with you another solution.SQL SERVER 2008 R2 Configuration Manager prompts "remote process call failed" (0x800706be) ErrorSolution:

In the past, when SQL Server 2008 was not available for login, it was always changed through "Computer Management" → "SQL Server service", "SQL Server (MSSQLSERVER )". However, the current problems have become the case that the SQL Server service cannot be opened, which is very depressing.

You can check it online to find out that 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" in the control panel or other auxiliary software and uninstall it.

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.

So far, many people should be able to solve the problem. It may be the reason for my RP. When I started SQL Server (MSSQLSERVER), a new problem emerged. 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.

The above is all the content in this article, hoping to help you solve the problem of SQL server Service display remote process call failure.