SQL Server Agent gives- Remote procedure call failed (0x800706be)
-
Monday, June 20, 2011 4:38 PM
I can't access SQL Server 2008 R2 remotely on Windows 2008
1. TCP/IP Enabled for SQL Server Network Configuration Protocols, SQL Native Client 10.0 configuration clients, and SQL Native Client 10.0 configuration clients(32 bit)
2. Firewall disabled to make sure its not interferring with things.
I noticed the SQL Server Agent is Stopped. Not sure if this is the issue. When I try and turn this from disabled to Automatic or Manual, I get this error:
Remote procedure call failed (0x800706be)
It shouldn't be this difficult.
Thank you for your help in advance!
All Replies
-
Monday, June 20, 2011 4:45 PM
Hi
Have you enabled "Allow Remote Connections" in server properties. If Not, then open SSMS and connect to Server and right click on Server Name, click Properties -> Connections -> Check "Allow remote connections to this server"
Hope you enabled the TCP\IP on "SQL Server Network Configuration) as well.
After making the changes, restart the SQL Server service.
Arunraj Chandrasekaran, MCTS, Author: SQLXpertise.com
If you found this post useful, Please "Mark as Answer" or "Vote as Helpful" -
Monday, June 20, 2011 8:02 PM
Yes both of those things have been enabled before the problem.
Allow Remote Connections and Mixed Mode Authentication. However, all I'm trying to do is TURN on a service WITHIN the Server....so the login account should be the local Network account thats part of the install.
Thank you for your help in advance! -
Monday, June 20, 2011 9:00 PMAnswerer
Try opening the SQL server configuration manager with RUN AS ADMIN option and see if that makes any difference
Thanks, Leks- Proposed As Answer by Peja TaoModerator Wednesday, June 22, 2011 9:03 AM
- Marked As Answer by Peja TaoModerator Wednesday, July 13, 2011 6:59 AM
- Unmarked As Answer by Kalman TothMicrosoft Community Contributor, Editor Saturday, September 22, 2012 11:34 AM
-
Wednesday, June 22, 2011 9:12 AMModerator
Have you tried to start SQL Server Agent from the command prompt using:
SQLAGENT90 -C -V>C:\SQLAGENT.OUT
Best Regards,
Peja
Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.- Marked As Answer by Peja TaoModerator Wednesday, July 13, 2011 6:59 AM
-
Thursday, June 23, 2011 3:04 PM
Unfortunately I have exactly the same problem, i've tried all the suggestions from this post and still have the error when I try to change the Start Mode, it shows me:
WMI Provider Error
The remote procedure call failed.[0x800706be]
-
Friday, November 25, 2011 3:05 AMsame here. Somebody?
Leo Tohill -
Monday, February 27, 2012 6:21 PM
Installed SQL Server Express 2010, but I am not able to start the SQL Server Agent. (RPC error 0x00706be). Ran the SQL Server Configuration Manager both for the local user and as Administrator (Windows 7), but does have the same effect. I tried to run:
sqlagent.exe -c -v >c:\sqlagent.out
This runs normal, see the output in sqlagent.out:
Microsoft (R) SQLServerAgent 10.50.2500.0 Copyright (C) Microsoft Corporation. 2012-02-27 19:12:36 - ? [098] SQLServerAgent terminated (normally)
So the mystery deepens.
-
Tuesday, May 15, 2012 5:59 PM
+1. SQL Server Configuration Manager (run as administrator) shows SQL Server Services as "The remote procedure call failed. [0x800706be]
SQL Server 10.0 exess error. Note I've installed VS2012 Beta1 (default install) and never needed SQL on this box before that install (so unsure if VS2012 is related).
Thanks! -Zephan
-
Friday, June 08, 2012 6:20 AM
Does Anyone have short or Long solution for this?
-
Sunday, June 10, 2012 11:55 PM
Hello,
About the error message>> The remote procedure call failed.[0x800706be], in my case, the solution was to install SQL 2008 R2 SP1.
Regards,
Robert.
- Proposed As Answer by Zephan Monday, June 25, 2012 11:06 PM
- Marked As Answer by Kalman TothMicrosoft Community Contributor, Editor Tuesday, June 26, 2012 6:51 AM
-
Monday, June 25, 2012 11:10 PM
Yeah! I just confirmed installing SQL 2008 R2 SP1 fixed RPC error 0x800706be. Thank you Robert Ancajima for posting your observation!
For the record Opening SSCM As Administrator did not help solve this problem for me.
Thanks! -Zephan
-
Friday, August 17, 2012 7:36 AMI also had this problem after installing VS2012. Previously I had SQL Server 2008 R2 installed. I am now downloading the service pack and hopefully this will cure the problem.
-
Saturday, September 22, 2012 11:42 AMAnswerer
Any luck?
The following thread is on the same topic with solutions:
Kalman Toth SQL SERVER 2012 & BI TRAINING
New Book: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2012 -
Monday, November 12, 2012 2:41 PM
Yes .. Probably should be VS2012 related.. Getting RPC Error right after the installation ..
Updating to SQL Service Service Pack 2 .. Hopefully it should solve the issue
Manoj N Shenoy

