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

26

Does Anyone knows the solution to this problem m not being able to run the SQL Server Services.

enter image description here

sql-server-2008-r2
asked on Stack Overflow Jul 21, 2012 by Subek Shakya • edited May 15, 2019 by Telarian

6 Answers

13

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

Source: Frozen bytes

answered on Stack Overflow Sep 25, 2013 by Fernando JS
12

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.

How to start this service:

Open Administrative Tasks > Services > Select Standard services tab > start SQL Server Agent(MSSQLSERVER) service and you are good to go.

9

With all due respect, "Right click on configuration manager and run as administrator" is a bogus 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; immediate I try to run SQL Server Configuration Manager, and the installation of SQL 2012 has broken it such that I get the "remote procedure call failed". That is true even if I "run as administrator". Microsoft says they can't reproduce this, but I've contacted them again because I've now reproduced this twice. And, if there's any doubt: un-installing SQL 2012 causes the problem to go away, and the configuration manager works again. I blogged about it here: http://dbarrowstechblog.blogspot.com/2012/09/the-remote-procedure-call-failed.html ; haven't solved it yet.

answered on Stack Overflow Oct 18, 2012 by David Barrows
2

This error occurs only after I have installed the Microsoft Visual Studio 2012 setup in my work machine.

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

I also un-registered and re-registered the sql provider DLL –> regsvr32 "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmprovider.dll" but issue not resolved.

Solution:

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

answered on Stack Overflow Oct 18, 2013 by kombsh • edited Dec 11, 2013 by Brad Larson
0

Ok, Stop this.

Is this a new Installation?

  1. Open SSMS in Integrated security Mode
  2. Right click on server name in Object explorer tree at the left
  3. Select properties -> Then choose the "Security" page at left
  4. Under Server Authentication, select "SQL Server and Windows Authentication mode"
  5. Click OK
  6. Exit SSMS completely
  7. Open "SQL Server Configuration Manager" (in Configuration menu under the "Microsoft SQL Server 2008 R2" menu item from start menu
  8. Select you instance on SQLExpress and restart the instance of the server (but this is ok for non express too)
  9. Exit SSCM - and to verify open SSMS again, but with "SQL Server Authentication" selected in the Authentication type dropdown - put in your SQL user ID and password.
answered on Stack Overflow Jun 9, 2013 by rachmann
0

installing the SP3 on SQL server 2008 worked for me..so give it try Thanks!! dont forget to vote up if this helps you

answered on Stack Overflow Dec 24, 2014 by user4390667

User contributions licensed under CC BY-SA 3.0