SQL Server Agent Fails with Error The remote procedure call failed


SQL Server Agent is one of the important feature which allows DBAs to Create and Schedule jobs to perform regular maintenance or run application related jobs regularly. There are many other options provided by SQL Server Agent which include Creating Alerts and Operators, and sending database mails from Agent jobs or when the jobs fail, etc. SQL Server Agent service gets installed along with the SQL Server installation. A separate windows service gets added for SQL Server Agent and it is dependent on SQL Server Services. When the SQL Server Agent Service starts, a windows process is created for the SQL Server Agent and handles job execution, etc.

Although SQL Server Agent functions smoothly, sometimes it can fail due to various reasons. One of the error which DBAs may observed is the below mentioned error when you try to enable the SQL Server Agent service which is in disabled state. Most often or no this happens due to installation of any visual studio components which affects the files related to SQL Server.

WMI Provider Error
The remote procedure call failed.[0x800706be]

The above error can occur due to various reasons including some known issues. Below are some of the options which you can try to fix this error and then start the SQL Server Agent Service.

– Always use SQL Server Configuration Manager to make any changes to the SQL Server or SQL Agent services.

– Launch SQL Server Configuration Manager by “Run-as-Administrator”

– If the SQL Server Agent Service is in disabled state, then enable the service and then try to start the service. If you get the same error when you try to change it from disabled to enabled then try changing it from services.msc and after that come back to SQL Server configuration manager and then attempt to start the SQL Server Agent service.

– Apply latest Service Pack available for the SQL Server instance. Example, if SQL Server is of version SQL Server 2008 R2 SP1, then install SP2 which should fix any problems.

– If already the SQL Server is on latest version or latest service pack, then perform repair of the SQL Server instance using the SQL Server media.

– Try to start the SQL Server Agent service from command line using below command. Make sure command prompt is launched using “Run-as-Administrator”


– If there are multiple instances of SQL Server or related components installed on the same server, then use the configuration manager of the latest version. Example: If there are SQL Server 2008 R2 and SQL Server 2012 components installed on the server, then use the SQL Server 2012 configuration manager.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.


Leave a Reply

Your email address will not be published. Required fields are marked *