WMI Corrumpt? - Workflow Runtime: Failed to run a WMI query
Hi John, have you installed wmi fix? it fixes leaks in win32_service namespace. http://social.technet.microsoft.com/Forums/en-AU/operationsmanagergeneral/thread/9469cca5-33ab-471c-9d1f-4da7af7c8e6d
November 21st, 2011 10:05am

Hi John, have you installed wmi fix? it fixes leaks in win32_service namespace. http://social.technet.microsoft.com/Forums/en-AU/operationsmanagergeneral/thread/9469cca5-33ab-471c-9d1f-4da7af7c8e6d I have not. Sorry, I didn't see that the last time. I just downloaded it. It says the server will need a restart, so I will do that after hours and let you know. Thanks.
Free Windows Admin Tool Kit Click here and download it now
November 21st, 2011 11:10am

Workflow Runtime: Failed to run a WMI query I get thousands of these for one particular server. I run; winmgmt /verifyrepository and it says it is consistent. I found a couple different blogs on rebuilding the WMI repository and I did that. Still get the alerts. If I go into Server Mgt and do properties on WMI Control I get this: I had tried the fix in this thread and I still get the alerts after doing that: http://www.msfn.org/board/topic/109030-how-to-fix-wmi-corruption/ Anyone know of any other fixes for this problem, other than to just disable the alert?
November 21st, 2011 4:43pm

That didn't work so well. When I run the patch I get the message "this update does not apply to this computer". I downloaded it from my Windows 7 computer the first time, actually, they have to email you the link. But I'm sure I chose the right version. When that didn't work I did it from the server, and you only get one choice then; Server 2008 R2. But the same message. No joy with that.
Free Windows Admin Tool Kit Click here and download it now
November 21st, 2011 6:41pm

Hi, Would you please provide us more details about the error? Please check the WMI issue with the methods in for the second problem in the table: Operations Manager 2007 R2 Management Pack Guide - Troubleshooting http://technet.microsoft.com/en-us/library/dd279686.aspx For troubleshooting WMI issues, I would like to share the following with you for your reference: WMI Troubleshooting Tips http://blogs.technet.com/b/configmgrteam/archive/2009/05/08/wmi-troubleshooting-tips.aspx WMI Troubleshooting Techniques http://technet.microsoft.com/en-us/library/cc180763.aspx WMI Troubleshooting http://msdn.microsoft.com/en-us/library/aa394603.aspx Hope this helps. Thanks. Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
November 22nd, 2011 5:10am

Nicholas, when I run WBEMtest, and try to connect to root\cimv2, I get this error: Thank you for the other links but, I have previously gone through the steps to rebuild the repository. And afterwards running; winmgmt /verifyrepository reports that it is consistent. And I also don't believe it is a memory leak. We have many 2008 R2 servers. Probably 30. And only this one server is getting this particular alert. They are all patched at the same level, seems like if one had a memory leak, they all would. We will either call Microsoft on this one or, disable the alert. The server runs fine. And after reading your links I see that rebuilding the repository risks making things worse by causing other problems. I don't need that.
Free Windows Admin Tool Kit Click here and download it now
November 22nd, 2011 9:19am

Nicholas, when I run WBEMtest, and try to connect to root\cimv2, I get this error: Thank you for the other links but, I have previously gone through the steps to rebuild the repository. And afterwards running; winmgmt /verifyrepository reports that it is consistent. And I also don't believe it is a memory leak. We have many 2008 R2 servers. Probably 30. And only this one server is getting this particular alert. They are all patched at the same level, seems like if one had a memory leak, they all would. We will either call Microsoft on this one or, disable the alert. The server runs fine. And after reading your links I see that rebuilding the repository risks making things worse by causing other problems. I don't need that.
November 22nd, 2011 5:12pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics