Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
WMI corrupt - how to reinstall/repair?

Answered WMI corrupt - how to reinstall/repair?

  • Wednesday, September 10, 2008 9:55 AM
     
     
    Sign In to Vote
    1

    Hi,

    WMI Control\General reports "Failed to connect to <local computer> because of "WMI: Generic failure". The same also displayed in services.msc and Service\Dependencies attribute.

    Executing a restore from last backup file does not change a thing. WMI service is running. Running winmgmt /verifyrepository (or salvagerepository) completes with success as long as WMI is stopped. If started the same error is displayed.

    The WMidiag is too old for Windows Server 2008 (I haven't found a 2008 version), and is incorrectly reporting missing files.

    I have not found any means to remedy this, nor reinstalling WMI. Do I have to run OS installation+repair?

     Regards

    Morten Ross

    MR
     

All Replies

  • Friday, September 12, 2008 12:38 PM
     
     Answered
    Sign In to Vote
    6
    Hello,

     

    This error message usually indicates that the WMI repository is corrupted, but sometimes may also indicate that some other system files are corrupted.

     

    If you have any previous backup, I would highly suggest that you try restoring to that backup to see if the problem remains.

     

    Or, would you please try the following steps to see if they can be of any help?

     

    1. Disable and stop the WMI service.

         sc config winmgmt start= disabled

         net stop winmgmt

     

    2. Run the following commands.

         Winmgmt /salvagerepository %windir%\System32\wbem      (I noticed that you have run this command, but I would suggest that you try it again)

         Winmgmt /resetrepository %windir%\System32\wbem

     

    4. Re-enable the WMI service and then reboot the server to see how it goes.

         sc config winmgmt start= auto

     

    If the problem remains, then try the following steps to rebuild the repository:

     

    1. Disable and stop the WMI service.

         sc config winmgmt start= disabled     (note that there is a blank between '=' and 'disabled')

         net stop winmgmt

     

    2. Rename the repository folder (located at %windir%\System32\wbem\repository) to repository.old.

     

    3. Re-enable the WMI service.

         sc config winmgmt start= auto

     

    4. Reboot the server to see if the problem remains.

     

    If the above steps cannot help, you may also need to check if some disk sectors or system files are corrupted. You may try "chkdsk" and "sfc /scannow" commands to see if they can help. Otherwise, you may need to reinstall the whole server.

     

    Best regards,

    Chang Yin
    • Marked As Answer by Chang Yin Friday, September 19, 2008 9:11 AM
    •  
     
  • Wednesday, June 22, 2011 12:06 PM
     
     
    Sign In to Vote
    0

    We had similar problems and the procedure above worked, however in addition we had to rejoin the computer account to the domain.

     

     
  • Wednesday, November 09, 2011 12:28 AM
     
     
    Sign In to Vote
    0

    This worked.. Thanks!

     

     
  • Monday, December 10, 2012 7:19 AM
     
     
    Sign In to Vote
    0

    Thanks for the great post.

    it worked for me without restart.

    Kind Regards,

    Ali

     
  • Tuesday, January 08, 2013 7:00 AM
     
     Proposed
    Sign In to Vote
    0

    This procedure worked for me on an SBS 2011 server which has had SBS console crashing and other applications crashing.

    I've been looking everywhere for a solution to this problem and was going to rebuild the server.

    I know you posted this a very long time ago but thank you Chang Yin you rock !

    • Proposed As Answer by MarkInTheMiddle Tuesday, January 08, 2013 7:00 AM
    •  
     
  • Friday, May 10, 2013 11:43 AM
     
     
    Sign In to Vote
    0
    Thank you so much Chang. It worked like a miracle.