Partager via

SCOM 2007,Alert generated from WMI Probe Module Execution Failure rule

  • Article

PROBLEM DESCRIPTION:
=====================
You needed assistance in troubleshooting the “Module was unable to connect to namespace” and “WMI Probe Module Failed Execution” Error.

Alert: WMI Probe Module Failed Execution
Source: 123.com.tw
Path: 123.com.tw
Last modified by: System
Last modified time: 2009/3/13 上午 00:00:00 Alert description: ExecQuery failed
Query: 'SELECT DeviceID, Name, Description, FileSystem, Compressed, Size, DriveType, SupportsFileBasedCompression FROM Win32_LogicalDisk WHERE (DriveType=3 or DriveType=6) and FileSystem!=null'
HRESULT: 0x80004005
Details: 無法指出的錯誤
One or more workflows were affected by this.
Workflow name: Microsoft.Windows.Server.2000.LogicalDisk.Discovery
Instance name: 123.com.tw
Instance ID: {12345678-ABCD-A123-A1A1-2C3FA9235EE5}
Management group: JimmyTest
Alert view link: "https://Jimmytest-SCOM/default.aspx?DisplayMode=Pivot&AlertID=%11334ef13f2-6dc5-478c-aa18-c49cef097356%7d"
Notification subscription ID generating this message: {12345678-6B9D-7CAE-8EEC-5535DB2E3F6F}

CAUSE:
======
This is related to a known Bug. The WMI Query looks for "SystemDrive" which apparently not present on the Windows 2000 Machines.

RESOLUTION :
==========
Please disabled the rule for Windows 2000 servers.

RELATED KNOWLEDGE BASE ARTICLES :
=========================
Problems occur on a management server that is running System Center Operations Manager 2007 Service Pack 1 when certain management packs are installed
https://support.microsoft.com/?id=951979

Comments

  • Anonymous
    January 01, 2003
    Now that the scripts have been updated, make sure not to restart the health service on this server, otherwise the script will be overwritten with the original version from the MP. This is one of the limitations of the workaround, as