The SQL Dude!

On-Disk & In-Memory Pages that teach you the SQL way of life!

SQL Server 2012 Configuration Manager WMI Error – Remote Procedure call failed [0x800706be]

Posted by Sudarshan Narasimhan on December 5, 2012

I recently installed SQL 2008 R2 alongside my existing SQL Server 2012 instance. I wanted to change the service account for the SQL Agent service, so I opened SQL Server Configuration Manager (SSCM). To my surprise, I got this error. Bear in mind, this is a freshly installed OS and SQL combination.


Error Text: The remote procedure call failed. [0x800706be]

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

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

But the issue was not resolved. This was working before and all I did was to install another instance of SQL 2008 R2 which went fine without any issues.

Next, I used wbemtest utility to connect to the SQL namespace and query the list of SQL Service. I was able to connect to the namespace root\microsoft\sqlserver\computermanagement10, but the query “select * from SqlService” returned this error


Basically, this was the same error as before. Interestingly, I could connect to the SQL 2012 namespace root\microsoft\sqlserver\computermanagement11, and the query to list the SQL Services worked as well. I checked the application event log and found this “Application Error” Event ID 1000. This tells me that the wmiprvse.exe (WMI host process) is crashing due to an issue with svrenumapi100.dll. This is the DLL that SQL Server uses to perform discovery of services.

Log Name:      Application
Source:        Application Error
Date:          12/5/2012 10:49:28 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Faulting application name: wmiprvse.exe, version: 6.2.9200.16384, time stamp: 0x5010ad15
Faulting module name: svrenumapi100.dll, version: 2009.100.1600.1, time stamp: 0x4bb681be
Exception code: 0xc0000005
Fault offset: 0x00000000000514e6
Faulting process id: 0x1458
Faulting application start time: 0x01cdd30cad78774b
Faulting application path: C:\windows\system32\wbem\wmiprvse.exe
Faulting module path: C:\Program Files\Microsoft SQL Server\100\Shared\svrenumapi100.dll

Log Name:      Application
Source:        Windows Error Reporting
Date:          12/5/2012 10:44:58 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Fault bucket -1203304158, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: wmiprvse.exe
P2: 6.2.9200.16384
P3: 5010af6d
P4: svrenumapi100.dll
P5: 2009.100.1600.1
P6: 4bb682e9
P7: c0000005
P8: 0003a0bf

Attached files:

These files may be available here:


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.



17 Responses to “SQL Server 2012 Configuration Manager WMI Error – Remote Procedure call failed [0x800706be]”

  1. Jason said

    Thank you SQL Dude. You are the man! I ran into this exact instance except I had to install SQL Server CE under my existing SQL Dev Edition so that I could take advantage of some MVC development. Drove myself crazy trying to find a solution to this. I wish Microsoft would get it together with SQL. It really should not be this complicated. Anyway, thank you very much. If anyone is having trouble getting SQL services running, I definitely recommend this post.

  2. avo said

    Thx! Good job!
    I have MS server 2012 R2 + Sql server 2008 R2 and have this problem (WMI crash). I solved this problem by installing the service pack 2.

  3. Thomas said

    I can confirm that upgrading to sql server 2008 r2 sp2 resolved this issue.

  4. David Aronow said

    You are truly the SQL dude! Thanks for your help!

  5. Kiran said

    Uninstalled SQL 2008r2 and installed SQL 2012. Now in SQL Configuration Manager Remote Procedure call failed [0x800706be]” getting error.
    Any help me ASAP.

  6. Max said

    Finally found your post after 4 hours of searching.. Thanks a lot man. SP3 resolved my issue.

  7. Thirmurugan J said

    after installation of SQL SERVER 2008 R2 SP2 resolved the error. Thanks man. your are the real SQLDude!!!!!!!!

  8. […] SQL Server 2012 Configuration Manager WMI Error – … – I recently installed SQL 2008 R2 alongside my existing SQL Server 2012 instance. I wanted to change the service account for the SQL Agent service, so I opened SQL …… […]

  9. Mihir said

    Thank You

  10. hector said

    hi, I have the same error regarding rpcss, but I do not have sql 2012 along, I’ve tried to recompile the .mof file, register and unregister process, tried to apply SP 1,2 and 3, SP update process run ok but does not let me pick an instance, on services it states that is running but can not stop or restart the service in properties options are disabled on every tab.

    can anyone help 😦 ???

  11. Renzo said

    Sp3 is the solutions.. thanks.

  12. Max said

    Great article, thanks. I haven’t even notice that VS.Net 2010 installed 2008 SQL Express and screwed my 2012 installation. The SP3 for the 2008 fixed that. Thanks again you saved me quite some time.

  13. Maciej said

    Great job!

    Even under Windows 2010 with auto updates to share database of BCM for Outlook 2013 with other users, you have first install SQL 2008 SP4 manually. Thank you.

  14. […] SQL Server 2012 Configuration Manager WMI Error – Remote … – I recently installed SQL 2008 R2 alongside my existing SQL Server 2012 instance. I wanted to change the service account for the SQL Agent service, so I opened SQL … […]

  15. Faraz Fakih said

    Thanks uninstalling 2012 version helped me solved my problem.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: