Hello, After the upgrade to SP1 of SCE2007 we receive a lot of these alerts... WMI Probe Module Failed Execution. The details are almost everytime the same: Object enumeration failed Query: 'SELECT Version,Caption,BuildNumber,CSDVersion,ServicePackMajorVersion,ServicePackMinorVersion,SerialNumber,InstallDate,SystemDrive,WindowsDirectory,TotalVisibleMemorySize FROM Win32_OperatingSystem' Error: 0x80041017 Details: One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DiscoverWindowsOSProperties Instance name:xxxxxxxxxxxxxx Instance ID: {EFA34817-3121-4F54-D8D7-3BF2E8509DCF} Management group: xxxxxxxx_xx Anybody got any ideas? Many thanks in advance, brgds, Mike

Have you noticed if its specifically WIndows 2000 machines?I have beenr receiving similar messages on my remaining Windows 2000 machines: Object enumeration failed Query: 'SELECT Version,Caption,BuildNumber,CSDVersion,ServicePackMajorVersion,ServicePackMinorVersion,SerialNumber,InstallDate,SystemDrive,WindowsDirectory,TotalVisibleMemorySize FROM Win32_OperatingSystem' HRESULT: 0x80041017 Details: Invalid query One or more workflows were affected by this. Workflow name: Microsoft.SystemCenter.DiscoverWindowsOSProperties Instance name: xxxxx Instance ID: {1AE3E2F0-0D0C-54A3-69FE-DF6AA951CEAE} Management group: ADMINSRV_MG

Hey Tim, Many thanks for the quick response. No, it is coming on all of my machines. XP, Server 2003 and 2000 server. I don't have any 2000 pro's left in the company. Brgds, Mike

Hi Mike, This is a known issue, which is under investigation and will be fixed in the future. You can just safely ignore the alerts. You can also disable the Rule which generates the alerts by following these steps: 1. Open SCE console and navigate to Authoring pane; 2. Expand Rules and find a rule named "WMI Probe Module Execution Failure"; 3. Right-click it and choose Overrides -> Disable the Rule -> For all objects of type: Agent. Hope it helps.

Dear, Many thanks for your response. I've disabled the rule as you said and will check tomorrow morning if there are no more alerts. Many thanks, brgds, Mike

Are you supposed to disable this rull for all Type for just "Type: Agent"?

If you're receiving this error on Dell clients check outKB948730.

Yog Li - MSFT wrote: Hi Mike, This is a known issue, which is under investigation and will be fixed in the future. You can just safely ignore the alerts. You can also disable the Rule which generates the alerts by following these steps: 1. Open SCE console and navigate to Authoring pane; 2. Expand Rules and find a rule named "WMI Probe Module Execution Failure"; 3. Right-click it and choose Overrides -> Disable the Rule -> For all objects of type: Agent. Hope it helps. Can you tell us what the problem is?

Has a hotfix been released yet for this issue?

Hi Rick, Please check thefollowing KB article, which is also appliable for SCE: 951979Problems occur on a management server that is running System Center Operations Manager 2007 Service Pack 1 when certain management packs are installedhttp://support.microsoft.com/default.aspx?scid=kb;EN-US;951979The hotfix include some lastest MP. You need to import into SCE console to update them.Hope it helps,Yog Li - MSFT

kinda puzzled how this new mp's gonna solve the problem for win2k clients.i've found out that it fails on win2k servers because the select statement isn't correct. When manually run "'SELECT Version,Caption,BuildNumber,CSDVersion,ServicePackMajorVersion,ServicePackMinorVersion,SerialNumber,InstallDate,SystemDrive,WindowsDirectory,TotalVisibleMemorySize FROM Win32_OperatingSystem" fails as well. However, when i remove the property "SystemDrive" it runs perfectly. Well at least the error makes sense now... 0x80041017 = invalid query :)I was just wondering if that property doesnt exist in win2k sp4 and that e.g. the "System.mom.backwardcompatibility.library.mp" solves it?

Rob1974 I believe that you're right, Server 2000 machines do not contain the SystemDrive property and that's where the query fails.

Hi Yog Limay be the problem still appear on System Center 2007 R2?I have a lot of servers with this errors.Regards.Alejandro.Alejandro Mazzitelli | http://geeks.ms/blogs/amazzite

I'm still seeing it with R2 also on 2003 machines.Ralph Bley

You have to check the error code. there are lots of reasons why this could fail (timeouts, access denied, etc), but the specific one mentioned here has been solved.