We have an Exchange 2007 server running on Windows 2008 Enterprise x64, and I recently discovered a strange problem with the WMI after getting some strange SCOM monitoring alerts. The SCOM error I get: 'Microsoft.Windows.Server.LogicalDiskHealthCheck.vbs : The class name 'Win32_Volume' did not return any valid instances. Please check to see if this is a valid WMI class name.. Provider failure' So I started the Windows Management Instrumentation Tester (wbemtest) and ran this query:SELECT * FROM Win32_Volume The error I get in return is: Number: 0x80041004 Facility: WMI Description: Provider failure I started the WMI Control MMC and did a backup of the WMI repository to check for other inconsistencies, but the backup went through OK. After restarting the server, the wbemtest query (SELECT * FROM Win32_Volume) works fine again. But every time we do a full backup of this server, the same WMI error returns. We use EMC Networker backup software (NetWorker Module for Microsoft Applications version 2.2.0.94). I see only one other error in the system log (no errors in the application log), this error is also logged during backup.: Event ID: 10 Source: VDS Dynamic Provider Description: The provider failed while storing notifications from the driver. The Virtual Disk Service should be restarted. hr=80042505 Any suggestions on how to remedy this recurring WMI problem ? JohnW

Hello,did you saw this one:http://social.technet.microsoft.com/Forums/en/winserverfiles/thread/8b638934-d122-4823-b883-cacc1870ecd4Did you also cross check with EMC support if that is a known problem?Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.

Hi, Yes, I saw that thread - but unfortunately it didn't provide a solution for me. EMC support has no knowledge of a bug in their backup client. Other suggestions ? JohnW

Lo and behold, we found a solution: Even though the guys at EMC support had never heard of such a problem, we uninstalled the backup agent (Networker Module For Microsoft Applications v2.2 build 94), rebooted the server, and installed a later version v2.2 build 96 - and we haven't had the problem since. JohnW