locked
failed to initialize all required wmi classes on Primary server RRS feed

  • Question

  • Hi,

    I am getting 'failed to initialize all required wmi classes' when i open WMImgmt console on my Primary server.

    I am not able to connect any Namespace using WBEMTEST. It throws error 0x80041002 - WMI- Not found.

    As it is Primary server , how can I proceed for WMItroubleshooting or repair? Permissions are checked..

    I am getting Event 10 in eventviewer -

    The description for Event ID 10 from source Microsoft-Windows-WMI cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.


    SiddheshM MCTS
    Wednesday, June 1, 2011 6:31 PM

Answers

  • Hi,

    Run below commands and problem resolved-

    1. winmgmt /verifyrepository

     - Got error Repository inconsistent

    2. winmgmt /salvagerepository
     - Once successful everything started working fine

    /verifyrepository [<path>]
            Performs a consistency check on the WMI repository. When you add the
            /verifyrepository switch without the <path> argument, then the live
            repository currently used by WMI is verified. When you specify the path
            argument, you can verify any saved copy of the repository. In this
            case, the path argument should contain the full path to the saved
            repository copy. The saved repository should be a copy of the entire
            repository folder.

    /salvagerepository
            Performs a consistency check on the WMI repository, and if an
            inconsistency is detected, rebuilds the repository.  The content of the
            inconsistent repository is merged into the rebuilt repository, if it
            can be read. The salvage operation always works with the repository
            that the WMI service is currently using. MOF files that contain the
            #pragma autorecover preprocessor statement are restored to the
            repository.


    SiddheshM MCTS
    Saturday, June 4, 2011 1:49 AM
  • Hi,

     

    Please check if the following KB article helps:

     

    "0x80041002 (WBEM_E_NOT_FOUND)" error code occurs when you try to open a WMI namespace on a computer that is running Windows Server 2003 SP2

     

    Also, you may refer to the following steps to check:

     

    Restart the WMI service

     

    Run the command: winmgmt /salvagerepository

     

    Next:

     

    winmgmt /resetrepository

    for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s

     

    Regards,

     

    Sabrina


    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |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.
    • Marked as answer by Sabrina Shen Monday, June 6, 2011 2:06 AM
    Friday, June 3, 2011 7:37 AM

All replies

  • I would not mess with WMI on a primary site server. I'd call CSS.

     

     


    John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|
    Wednesday, June 1, 2011 6:34 PM
  • Hello - Try to use WMIDIAG to get more details about the error.

    See, http://msdn.microsoft.com/en-us/library/aa394603(v=vs.85).aspx (WMI Troubleshooting)


    Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |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.
    Wednesday, June 1, 2011 6:35 PM
  • Hi,

     

    Please check if the following KB article helps:

     

    "0x80041002 (WBEM_E_NOT_FOUND)" error code occurs when you try to open a WMI namespace on a computer that is running Windows Server 2003 SP2

     

    Also, you may refer to the following steps to check:

     

    Restart the WMI service

     

    Run the command: winmgmt /salvagerepository

     

    Next:

     

    winmgmt /resetrepository

    for /f %s in ('dir /b *.mof *.mfl') do mofcomp %s

     

    Regards,

     

    Sabrina


    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |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.
    • Marked as answer by Sabrina Shen Monday, June 6, 2011 2:06 AM
    Friday, June 3, 2011 7:37 AM
  • Hi,

    Run below commands and problem resolved-

    1. winmgmt /verifyrepository

     - Got error Repository inconsistent

    2. winmgmt /salvagerepository
     - Once successful everything started working fine

    /verifyrepository [<path>]
            Performs a consistency check on the WMI repository. When you add the
            /verifyrepository switch without the <path> argument, then the live
            repository currently used by WMI is verified. When you specify the path
            argument, you can verify any saved copy of the repository. In this
            case, the path argument should contain the full path to the saved
            repository copy. The saved repository should be a copy of the entire
            repository folder.

    /salvagerepository
            Performs a consistency check on the WMI repository, and if an
            inconsistency is detected, rebuilds the repository.  The content of the
            inconsistent repository is merged into the rebuilt repository, if it
            can be read. The salvage operation always works with the repository
            that the WMI service is currently using. MOF files that contain the
            #pragma autorecover preprocessor statement are restored to the
            repository.


    SiddheshM MCTS
    Saturday, June 4, 2011 1:49 AM