Comments on: FIX: SQL Server System Configuration Checker cannot be executed due to WMI configuration (Error:2147500034)

By: Brad

Brad — Tue, 19 Aug 2008 20:49:49 +0000

I had what I thought was the same problem as you, but it was apparently slightly different. For those who made it here looking for the same thing, I found the fix that worked for me here:

http://blogs.msdn.com/echarran/archive/2006/01/03/509061.aspx

There were various WMI errors all over the place from different things, but the one that seemed to matter was:
Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 servers with SQL Server Configuration Manager.
Invalid class [0x80041010]

The post above fixed this and off I went!

Have a good one!
Brad

By: RoboTastic » »Stupid SQL 2005 and AIM

RoboTastic » »Stupid SQL 2005 and AIM — Fri, 15 Aug 2008 02:04:53 +0000

[...] » FIX: SQL Server System Configuration Checker cannot be executed due to WMI configuration (Error:2... [...]

By: Luke

Luke — Fri, 15 Aug 2008 01:51:27 +0000

Wow! this fixed it for me. I am trying to uninstall SQL 2005 Express and this did the trick. I must have installed AIM after I installed AIM. Thanks!

By: Marlin

Marlin — Fri, 04 Apr 2008 14:25:13 +0000

hmm.. Chuck's website is non-functional. I am still stuck, but at least I know there is a possible solution

If you still know the answer could you email, or post the solution here. Not sure what is going on with that other blog.

By: Jay Andrew Allen

Jay Andrew Allen — Mon, 03 Mar 2008 19:57:23 +0000

Okay, this is weird. I have BOTH the problems you described! My wife (who works for AOL - I know, I know) installed AIM on my laptop, and it hosed my network discovery in the exact same way. Plus, I've been unable to remove SQL Server 2005 from my machine.

The fix definitely worked for SQL Server. I'll let you know after a reboot if the network auto-detect window works again.