Hi Iam getting the below warning alerts in SCOM2007 R2 monitoring console active alerts, most of the alerts getting, can any one suggest to close the alerts. Alert 1: Module was unable to connect to namespace '\\.\ROOT\CIMV2' This has happened 294 times since this instance was loaded. Alert 2: WMI Probe Module Failed Execution - ExecQuery failed Configuration Alert 1: This alert was coming only on one particular Windows 2000 Server with the following discription. HRESULT: 0x8007000e Details: Not enough storage is available to complete this operation. Alert 2:This alert was coming on all Windows 2000 servers with the following discription. Query: 'SELECT * FROM Win32_Processor' uery: 'SELECT * FROM Win32_BaseBoard Query: 'SELECT * FROM Win32_ComputerSystem' Query: 'SELECT DeviceID, Name, Description, FileSystem, Compressed, Size, DriveType, SupportsFileBasedCompression FROM Win32_LogicalDisk Causes Alert 1:The alert was misleading as we are able to connect to above mentioned namespace by logging on to the server. Alert2: This alert was coming on all Windows 2000 Servers. The classes mentioned in the query doesny exist on Windows 2000 operating system. Resolutions Alert 1: Restarting the agent service has resoved the problem. Alert2: Create an Override for Windows 2000 Server computer group. Additional Information Alert1: Use WBEMTest tool to check the WMI connectivity. Alert2: Use WBEMTest tool to execute the query and check for classes.

It might be an issue with WMI on that particular machine. A few pointers: Look at older threads on the topic http://social.technet.microsoft.com/forums/en-US/systemcenter/thread/50b362c3-e439-41ba-b0d7-69635f6e4067/ Some WMI fixes for Win2003 http://blogs.technet.com/b/yongrhee/archive/2010/07/02/list-of-wmi-related-hotfixes-post-service-pack-2-for-windows-server-2003.aspx A page with suggested OM and Windows hotfixes http://blogs.technet.com/b/kevinholman/archive/2009/01/27/which-hotfixes-should-i-apply.aspx This said, Windows Server 2000 is out of support so nothing gets tested on it anymore. It might simply be that some new query in the base OS uses classes that Windows 2000 did not have, or use properties that existing classes didn't have... and so on. I am also moving this thread to the "OpsMgr general" forum, since it isn't an APM question. Thanks,

In addition, please check the issue referring to the following posts: Getting lots of Script Failed To Run alerts? WMI Probe Failed Execution? Backward Compatibility Script Error? http://blogs.technet.com/b/kevinholman/archive/2009/06/29/getting-lots-of-script-failed-to-run-alerts-wmi-probe-failed-execution-backward-compatibility-script-error.aspx Anti-virus software may cause script failures in OpsMgr 2007 http://blogs.technet.com/b/operationsmgr/archive/2009/01/22/anti-virus-software-may-cause-script-failures-in-opsmgr-2007.aspx WMI leaks memory on Server 2008 R2 monitored agents http://blogs.technet.com/b/kevinholman/archive/2010/06/09/wmi-leaks-memory-on-server-2008-r2-monitored-agents.aspx Hope this helps. Thanks. Nicholas Li TechNet Community Support