Trevor Sullivan's Tech Room - Minding the gap between administration and development

WMI Repository Corruption / SCCM Client Fix

You may have come across the following messages in the execmgr.log file on your SCCM clients:

Failed to open to WMI namespace '.rootccmPolicyMachine' (8007045b)
Failed to ConnectSettings for ICcmPolicyAgent in CSoftDistPolicyNamespace::ConnectToNamespace
Failed to ConnectToNamespace in CSoftDistPolicyNamespace::GetMachinePolicy
Failed to connect to machine policy name space. 0x8007045b
Failed to connect to user policy name space
CSoftwareDistPolicyMgr::GetSWDistSiteSettings failed to connect to machine namespace
Failed to instantiate UI Server {C2F23AE4-82D8-456F-A4AF-A2655D8CA726} with error 8000401a
Failed to instantiate UI Server 2 {E8425D59-451B-4978-A2AB-641470EB7C02} with error 8000401a
Failed to instantiate Updates UI Server {2D023958-73D0-4542-8AD6-9A507364F70E} with error 8000401a
Failed to instantiate VApp UI Server {00AAB372-0D6D-4976-B5F5-9BC7605E30BB} with error 0x8000401A

These messages are the result of WMI repository corruption. Other sources online have suggested:

1. Stopping the SMS Agent Host service (net stop ccmexec)
2. Stopping the WMI service (net stop winmgmt)
3. Deleting the WMI repository (rmdir /s /q %WINDIR%System32wbemrepository)
4. Starting the WMI service (net start winmgmt)
5. Starting the SMS Agent Host service (net start ccmexec)

Advertisement: Please take a moment to check out Arvixe PersonalClassASP web hosting!

This may work, however I have noticed other people in the past suggest that deleting the WMI repository is not ideal, even though it may work. Why exactly that is, I can’t necessarily explain off the top of my head. Either way, I recently encountered a client that was experiencing these errors, and instead of doing the usual WMI repository deletion, I instsead simply ran “winmgmt /resetrepository”. From the description of the command in the help, it would seem that it does more or less the same thing as deleting the repository, although this seems like a “cleaner” way of handling it. After all, the command was written and distributed by Microsoft, so I’m more apt to trust this method. The command help reads:

/resetrepository
The repository is reset to the initial state when the operating system
is first installed. MOF files that contain the #pragma autorecover
preprocessor statement are restored to the repository.

From what I can tell, running this command on the problem client has resolved whatever issues were present. Manually firing off an advertisement worked just fine, and the execmgr.log did not reproduce these messages (yet).





Comments

  1. By Brian

    Reply

    • By pcgeek86

      Reply

  2. By Dave

    Reply

  3. Reply

    • By theclarks1

      Reply

    • By Trevor Sullivan

      Reply

  4. Reply

    • By Trevor Sullivan

      Reply

  5. By Adam Stephens

    Reply

    • By Trevor Sullivan

      Reply

  6. By Vishwajeet Ranchi

    Reply

  7. By Stratodyne

    Reply

  8. By Stratodyne

    Reply

  9. By Asotelo6

    Reply

    • Reply

  10. By Jake C.

    Reply

  11. By steelie

    Reply

    • By Vikram

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>