Yesterday my SQL Server 2008 R2 installation decided to pull a looney tunes on me and GO KA BOOM! One minute I was debugging a knockout.js binding issue, the next trying to understand why all of a sudden my Web API call to SQL Server couldn’t open a connection. The initial error was complaining no instance was available or was not currently running. Say what!? Two seconds ago all was golden with my data requests. After doing the normal checks it was time to load SQL Server Configuration Manager. There she blew, KA BOOM! The SQL Server Configuration Manager error message was nothing I’d seen before and hinted to an issue with WMI integration.
Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 and later servers with SQL Server Configuration Manager. Invalid class [0x80041010]
Remote Procedure call failed [0x800706be]
After looking at Services to verify my SQL Server 2008 Engines and SQL Server Browser services are running decided to check SQL Server Configuration Manager. KA BOOM!
This error appears to happen when .mof files (Managed Object Format (MOF)) don’t get installed and registered correctly during set-up. In an attempt to resolve this issue, I executed the following mofcomp command in command prompt to re-register the *.mof files:
mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof"
According to blogs, support threads and stackoverflow threads mofcomp.exe should resolve the WMI error. Unfortunately, yesterday I was not one of the lucky ones. The error no longer occurs with SQL Server 2008 R2 Configuration Manager but remains for SQL Server 2012 Configuration Manager. Plus a new error has reared its ugly head, SQL Server 2008 Configuration Manager is now displaying
Remote Procedure call failed [0x800706be] as seen below.
After more research found an article by SQL Dude, SQL Server 2012 Configuration Manager WMI Error – Remote Procedure call failed [0x800706be] with a similar scenario. I too am running SQL Server 2008 and SQL Server 2012 side-by-side. After checking wbemtest utility to connect to the SQL namespace, query the list of SQL Service, and reviewing the Application Event log it was clear I had the same issue. While the order in which SQL Server versions installed differ, the ultimate solution is the same.
Install SQL Server 2008 R2 SP2, restart, open SQL Server Configuration Manager and ALL is good.
If you have SQL Server 2012 running side-by-side on the same machine with SQL Server 2008/2008 R2, then you need to have SQL Server 2008 SP3 or later (or) SQL Server 2008 R2 SP1 or later. This is required to obtain the edition information when performing a SQL Server discovery across the enterprise. I applied SP2 on my SQL 2008 R2 instance and that fixed the issue with configuration manager. If you run into this issue, this piece of information might help you.
- Update Center for Microsoft SQL Server
- SQL Server 2012 Configuration Manager WMI Error – Remote Procedure call failed [0x800706be]
- SQL Server Configuration Manager : Cannot connect to WMI provider – Invalid class [0x80041010]
- The remote procedure call failed (0x800706be)–Windows Azure SDK installation broke SQL Server Config Manager?!?
- Remote Procedure call failed in SQL Server Configuration Manage