Getting Provider load failure in WMI after SQL 2012 Express uninstall

Getting Provider load failure in WMI after SQL 2012 Express uninstall by dalahira

Active

Type:	Bug
ID:	779763
Opened:	2/21/2013 6:44:05 PM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

I have an application that uses WMI to determine the configuration of SQL Server instances in a computer. I have 2 versions of SQL Server installed, SQL 2008 R2 Express and SQL 2012 Express. Everything works fine until I uninstalled SQL 2012, now I'm receiving this error:

************** Exception Text **************
System.Management.ManagementException: Provider load failure
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
...

*****************************************

First, I thought this could be a problem only in my computer, however I was able to replicate this error consistently on other computers.

Then I also used "wmiexplorer" to browse SQL WMI, "wmiexplorer" also threw "Provide Load Failure" exception when I queried SqlServiceAdvancedProperties.

The error did not occur on SQL 2008 R2 uninstall when I tried it in different computers.

WMIExporer link: http://www.ks-soft.net/hostmon.eng/wmi/index.htm

Details (expand)

English

SQL Server 2012 - Express Edition

Setup

Windows 7 (all editions)

US English

1. Install SQL 2008 R2 Express or SQL 2008 Sp2 Express.
2. Install SQL 2012 Express.
3. Using wmiexplorer, browse the installed SQL intances.
4. Uninstall SQL 2012 Express.
5. Use wmiexplorer again, browse the installed SQL instances. Query SqlServiceAdvancedProperties, it will throw "Provider load failure".

see above

SQL WMI is working after SQL2012 Uninstall.

File Name	Submitted By	Submitted On	File Size
sqlImage1.png	dalahira	2/21/2013	199 KB
sqlImage2.png	dalahira	2/21/2013	105 KB

Hi Dalahira, thanks for taking the time to report this issue. Can you confirm that you have tried re-booting and let us know if the issue still reproduces?

thanks,
[SQL Server Team]