You may end up getting “The remote procedure call failed. [0x800706be] WMI Error“ when you click SQL Server Services in SQL Server Configuration Manager as shown in the snippet below. This article explains the steps to troubleshoot “The remote procedure call failed. [0x800706be] WMI Error in SQL Server 2012”.
![The remote procedure call failed. [0x800706be] in SQL Server](https://www.mytechmantra.com/wp-content/uploads/2019/08/The-remote-procedure-call-failed-0x800706be.png)
This generally happens when you have SQL Server 2008 or SQL Server 2008 R2 running along with SQL Server 2012 on the same machine or you have installed Visual Studio 2012 which installed SQL Server 2012 components.
Recommended Solution
- First Option, will be to Install SQL Server 2008 SP3 or later / Install SQL Server 2008 R2 SP1 or later. Read the following article which explains How to Install a SQL Server Service Pack.
- Second Option, will be to recompile MOF file. The steps are mentioned below for your reference.
Recompiling MOF File to resolve “The remote procedure call failed. [0x800706be] WMI Error”
1. Open command prompt under administrative privileges i.e., using “Run as Administrator” and run as shown in the snippet below.
mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"

Now, you can go ahead and open SQL Server Services under SQL Server Configuration Manger to see all SQL Server Services.

Related Articles
- How to Configure TempDB on Local Disk in SQL Server 2012/2014 Failover Cluster to Improve Performance
- How to Fix Cannot execute script. Insufficient memory to continue the execution of the program (mscorlib) error in SQL Server
- Download SQL Server 2014 Developer Edition Free
- Licensing Arbitrage: Slashing SQL Server Core Costs with NVMe Storage
- COPY_ONLY Backup in SQL Server Step by Step Tutorial with Examples
- How to Use Dedicated Administrator Connection in SQL Server
- DROP IF EXISTS – Simplifying Database Cleanup Scripts in SQL Server 2016
