none
What is the proper way to fix WMI errors on WIndows 2003?

    Question

  • Hey guys,

    We recently made the move to SCCM 2012 SP1 and after the client push all my Windows 2003 servers are now experiencing the dreaded WMI crash bugs I've heard about on other forums:

    I've managed to tie the issue to the following error (via InventoryAgent.log):

    I've checked the following registry key.

    HKEY_LOCAL_MACHINE\Software\Microsoft\WBEM\Scripting

    and verified that the default namespace value is "root\cimv2".

    So (judging from what I've read elsewhere) the most likely culprit is a corrupt WMI repository. So I have to repair WMI and that's where I need help. Most of the guides and blogs I've read on this matter basically advise the following steps:

    1. Stop WMI Service
    2. Delete WMI Repository
    3. Start WMI Service
    4. WMI rebuilds automatically

    However I've read a few posts by some very smart Microsoft MVP-types that say this is a bad idea as it can break things. I've also heard that re-installing the SCCM Client rebuilds WMI automatically, so I'm wondering if just re-pushing the client to these servers if will fix the issue. Point is I need WMI fiexed, so what is the best (or "proper") way to repair a corrupt WMI repository?

    • Edited by ZeusABJ Tuesday, October 08, 2013 6:09 PM
    Tuesday, October 08, 2013 6:08 PM

Answers

  • Maybe I should simplify my questions:

    1. What is the safest way to repair  a corrupt WMI repository?
    2. If I re-install the SCCM client will it repair WMI automatically?

    As I said earlier... Do it exactly how you stated except I'd rename the repository instead of deleting it. I do that all the time.

    2. No it will not. The CM client would likely not even install if WMI is toast.


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    • Marked as answer by ZeusABJ Wednesday, October 09, 2013 1:31 AM
    Tuesday, October 08, 2013 11:16 PM

All replies

  • I seriously doubt ALL of your servers have bad WMI. Have you verified they have BITS 2.5 installed?

    If indeed WMI is the issue, and again I don't think it is, then... I do WMI like you said above all the time. I'd rename the repositroy instead of deleting it though.


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Tuesday, October 08, 2013 6:39 PM
  • I seriously doubt ALL of your servers have bad WMI. Have you verified they have BITS 2.5 installed?

    If indeed WMI is the issue, and again I don't think it is, then... I do WMI like you said above all the time. I'd rename the repositroy instead of deleting it though.


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Its not all, just our Windows 2003 servers. We only have about 30, and yes BITS 2.5 is installed. These were managed by SCCM 2012 RTM before we went to SP1 and (as I'm sure you know) BITS 2.5 is a required prerequisite just to install the SCCM client on Windows 2003.  
    • Edited by ZeusABJ Tuesday, October 08, 2013 6:45 PM
    Tuesday, October 08, 2013 6:43 PM
  • Wow...that's odd. I've never heard of all 2003 servers having busted WMI. Test blowing it away on one and see if that fixes the issue. I do it all the time even though it's not suggested. :-)

    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Tuesday, October 08, 2013 8:14 PM
  • I've managed to tie the issue to the following error (via InventoryAgent.log):


    That "error" is expected if there is no AppV client installed. Just ignore that message; it does not indicate a problem.

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, October 08, 2013 8:40 PM
    Moderator
  • I've managed to tie the issue to the following error (via InventoryAgent.log):


    That "error" is expected if there is no AppV client installed. Just ignore that message; it does not indicate a problem.

    Torsten Meringer | http://www.mssccmfaq.de

    I cannot ignore the message as it generates multiple instances of the above WMI error popup every time someone logs into the server. It is highly annoying.
    Tuesday, October 08, 2013 9:07 PM
  • Wow...that's odd. I've never heard of all 2003 servers having busted WMI. Test blowing it away on one and see if that fixes the issue. I do it all the time even though it's not suggested. :-)

    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Here are a couple of others who have reported the popup (but for issues different from mine):

    http://social.technet.microsoft.com/Forums/en-US/7311a576-b5dd-471b-9f9d-e93d714335ca/sccm-2012-sp1-and-windows-server-2003-weekly-wmi-crashes?forum=configmanagergeneral

    http://larsnorman.wordpress.com/2013/04/29/wmi-crashes-on-windows-server-2003/

    Tuesday, October 08, 2013 9:11 PM
  • Maybe I should simplify my questions:

    1. What is the safest way to repair  a corrupt WMI repository?
    2. If I re-install the SCCM client will it repair WMI automatically?
    Tuesday, October 08, 2013 9:12 PM
  • Download the SCCM Client Center and run a WMI repair and client install from there.

    http://sourceforge.net/projects/smsclictr/


    Cheers

    Paul | sccmentor.wordpress.com

    Tuesday, October 08, 2013 9:59 PM
  • Maybe I should simplify my questions:

    1. What is the safest way to repair  a corrupt WMI repository?
    2. If I re-install the SCCM client will it repair WMI automatically?

    As I said earlier... Do it exactly how you stated except I'd rename the repository instead of deleting it. I do that all the time.

    2. No it will not. The CM client would likely not even install if WMI is toast.


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    • Marked as answer by ZeusABJ Wednesday, October 09, 2013 1:31 AM
    Tuesday, October 08, 2013 11:16 PM
  • Maybe I should simplify my questions:

    1. What is the safest way to repair  a corrupt WMI repository?
    2. If I re-install the SCCM client will it repair WMI automatically?

    As I said earlier... Do it exactly how you stated except I'd rename the repository instead of deleting it. I do that all the time.

    2. No it will not. The CM client would likely not even install if WMI is toast.


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Okay thanks John,

    I can't remember where I heard it, but I could have sworn that (somewhere) somebody told me or I read that a new feature of the CM 2012 Client was WMI repair on install. You're an MVP and an Author so I have to assume that if you say its safe to just rename the WMI repository then it must be safe. 

    Thanks again!
    Wednesday, October 09, 2013 1:31 AM
  • Download the SCCM Client Center and run a WMI repair and client install from there.

    http://sourceforge.net/projects/smsclictr/


    Cheers

    Paul | sccmentor.wordpress.com

    Paul,

    I actually have the SCCM Client Center installed, I've only just begun to play around with it. I was unaware that it had WMI repair capability. I'll look into it.
    Wednesday, October 09, 2013 1:35 AM
  • Client center does have a WMI repair but I prefer to do it manually. I have "borrowed" some scripts from here and there (and maybe even from Roger) and create a script that I use to do mass WMI repairs on lists of machines. :-)

    In all honesty I haven't researched a lot about whether or not the client will repair WMI. In my mind it just stands to reason that the client requires WMI to be functioning so it doesn't seem like the client could repair it. It's that whole chicken and egg thing.

    BTW... I am not an author. :-)


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Wednesday, October 09, 2013 1:45 AM
  • Yep you can't beat the manual method.

    Cheers

    Paul | sccmentor.wordpress.com

    Wednesday, October 09, 2013 9:12 AM
  • Client center does have a WMI repair but I prefer to do it manually. I have "borrowed" some scripts from here and there (and maybe even from Roger) and create a script that I use to do mass WMI repairs on lists of machines. :-)

    In all honesty I haven't researched a lot about whether or not the client will repair WMI. In my mind it just stands to reason that the client requires WMI to be functioning so it doesn't seem like the client could repair it. It's that whole chicken and egg thing.

    BTW... I am not an author. :-)


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

    Yeah I actually have a pretty decent WMI repair script that I have written myself that stops all the services and renames the repository (just as you described), I just stopped using it because I read somewhere that doing that was a big no-no. I just wanted to confirm that I wasn't going to make things worse by going that route.

    As for the author thing, sure you are! At least MyITForum seems to think you are:

    ;)


    • Edited by ZeusABJ Wednesday, October 09, 2013 5:55 PM
    Wednesday, October 09, 2013 5:54 PM
  • I'd use the script if I were you. :-)


    That just means I have a blog there. I don't write books or anything real. LOL


    John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/


    Wednesday, October 09, 2013 6:44 PM