In this tutorial we will tech how to fix WMI namespace errors due to wbem repository Corrupted. WMI namespace errors displayed usually when Setup was unable to create the WMI namespace CIMV2\SMS.
Identification of WMI namespace errors.
SMS client systems CcmSetup.Log file in the CcmSetup directory you may see any one of the following errors or warnings:
MSI: Setup was unable to create the WMI namespace CCM
Error code is 80041001 or 80070003
MSI: Warning 25101. Setup was unable to delete WMI namespace CIMV2\SMS
Client installation has failed too many times. Ccmsetup will now abort
Installation failed with error code 1603
Solution for WMI namespace errors.
All errors and warning above appear due to repository Corrupted. To resolve these log file issues you must delete or rename the machines WMI Repository and allow it to recreate itself.
Steps:
- Open cmd
- Stop the “Windows Management Instrumentation” service. (net stop winmgmt)
- Rename the Windows\System32\Wbem\Repository folder to ”Oldrepository”.
- Restart the “Windows Management Instrumentation service”. (net start winmgmt)
- Verify that the Windows \System32\Wbem\Repository folder has been recreated.
- Reinstall the SMS client software.
The Client software will be installed successfully.
WMI namespace.
ConfigMgr uses WMI extensively for both client and server operations. The ConfigMgr client uses WMI for internal control of its own operations and for gathering hardware inventory. ConfigMgr also uses WMI as an interface to the site database. ConfigMgr 2012 creates and uses several namespaces in addition to adding classes to theRoot\CIMV2 namespace.
The ConfigMgr client agent gathers hardware inventory data by querying WMI. The Client Agent settings determine which object classes are reported as part of the client inventory.
Check more on : WMI
———————————————————————————–
