Best IT Recipes

SQL Server Agent gives: Remote procedure call failed (0x800706be)

Does anyone know a solution to this problem and cannot start SQL Server services.

enter image description here

+25
sql-server-2008-r2
Jul 21 '12 at 6:20
source share
7 answers

With all due respect, “The right to click on the configuration manager and run as administrator” is a fictitious answer. I also have this problem with the following series of events: I download the Windows Azure SDK from here: http://www.windowsazure.com/en-us/develop/downloads/ , which installs SQL 2012 Express; I am trying to start SQL Server Configuration Manager, and the installation of SQL 2012 violated it, so I received a “remote procedure failure”. This is true even if I run as administrator. Microsoft says that they cannot reproduce it, but I contacted them again because now I reproduced it twice. And, if there is any doubt: refusing to install SQL 2012 makes the problem go away, and the configuration manager works again. I wrote about this here: http://dbarrowstechblog.blogspot.com/2012/09/the-remote-procedure-call-failed.html ; still have not decided.

+9
Oct 18 '12 at 15:59
source share

Solution: Install SQL Server 2008 R2 SP2 , restart, open SQL Server Configuration Manager and ALL.

Source: Frozen Bytes

+12
Sep 25 '13 at 18:47
source share

No need to reinstall or upgrade an instance of SQL Server 2008 R2. I got the same error, and it can be solved by simply starting the standard MSSQLSERVER service.

How to start this service:

Go to Administrative Tasks> Services> Select the Standard Services tab> start the SQL Server Agent service (MSSQLSERVER) and you're good to go.

+11
Jun 16 '14 at 4:28
source share

Check out this link http://blogs.lessthandot.com/index.php/datamgmt/dbadmin/remote-procedure-call-failed .

It offers both a much simpler and more elegant solution (IMO)

+6
Apr 29 '14 at
source share

This error only occurs after installing Microsoft Visual Studio 2012 in my production machine.

Since this is a WMI error, I recompiled the MOF → mofcomp.exe file "C: \ Program Files (x86) \ Microsoft SQL Server \ 100 \ Shared \ sqlmgmproviderxpsp2up.mof"

I also did not register and re-register the sql provider DLL → regsvr32 "C: \ Program Files (x86) \ Microsoft SQL Server \ 100 \ Shared \ sqlmgmprovider.dll", but the problem was not resolved.

Decision:

I applied SQL Server 2008 R2 SP2 on my instance of SQL 2008 R2 and fixed the problem with Sql Server Configuration Manager. You can download the installation here ... http://www.microsoft.com/en-us/download/details.aspx?id=30437 .

+2
Oct 18 '13 at 4:19
source share

Ok, stop it.

Is this a new installation?

  • Open SSMS in integrated security mode
  • Right-click the server name in the object explorer tree on the left.
  • Select properties → Then select the Security page on the left.
  • In the "Server Authentication" section, select "SQL Server and Windows Authentication mode"
  • Click OK
  • Exit SSMS completely.
  • Open SQL Server Configuration Manager (on the Configuration menu, on the Microsoft SQL Server 2008 R2 menu from the Start menu
  • Select an instance on SQLExpress and restart the server instance (but this is normal for non-express)
  • Exit SSCM - and check the open SSMS again, but with "SQL Server Authentication" selected in the Authentication Type drop-down list, enter your SQL user ID and password.
0
Jun 09 '13 at 15:11
source share

installing SP3 on SQL Server 2008 worked for me ... let it try Thanks !! don't forget to vote if this helps you

0
Dec 24 '14 at 5:42 on
source share


More articles:


All Articles