Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Remote Procedure call failed with sql server 2008 R2

I am working with SQL Server 2008 R2. I am unable to connect to my database remotely. I got the following error.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

I have checked the SQL Server properties and I enable the Allow remote connections.

I have checked the Service manager and SQL Server service are running.

I have checked the configuration manager, I can't see any services under SQL Server Services and it shows Remote Procedure call failed

enter image description here

So please guide me.

like image 684
Karthik Bammidi Avatar asked Sep 27 '12 10:09

Karthik Bammidi


People also ask

Does SQL Server Configuration Manager work with remote procedure call 800706be?

It is working well and I had changed sql server settings through Sql Server Configuration Manager many times ,it was worked well. But today when I open SQL Server Services entry in Sql Server Configuration Manager, it shows an error message saying The remote procedure call failed 800706be.

How to fix SQL Server 2008 R2 SP2 is not working?

Solution: Install SQL Server 2008 R2 SP2, restart, open SQL Server Configuration Manager and ALL is good. Show activity on this post. No need to re-install or update your SQL Server 2008 R2 instance.

How to fix “SQL Server Configuration Manager not responding” error?

And in the “ SysWOW64 ” directory, search for “ SQLServerManager “. Now, if there are multiple versions of SQL Server Configuration Manager then, run the latest version out of them. As discussed in the second reason, the SQL Server Services could also be the reason behind the error.

Do I need to re-install or update SQL Server 2008 R2?

No need to re-install or update your SQL Server 2008 R2 instance. I got the same error and it get resolved by simply starting the MSSQLSERVER standard service. Open Administrative Tasks > Services > Select Standard services tab > start SQL Server Agent (MSSQLSERVER) service and you are good to go.


2 Answers

Open Control Panel > Administrative Tools > Services > Select Standard services tab (under the bottom) > Find start SQL Server Agent

Right Click and select properties,

Startup Type : Automatic,

Apply, Ok.

Done.

like image 103
sunnyuff Avatar answered Oct 06 '22 00:10

sunnyuff


I just had the same issue and was able to solve it by installing Service Pack 1.

like image 29
John Avatar answered Oct 06 '22 00:10

John