wmi error in ccmexec.log
Hi,
We found a systems in non client and below errors were found in ccmexec.log
The 'Certificate Store' is empty in the registry, using default store name 'MY'.
Failed to open to WMI namespace '\\.\root\CCM\Events' (8004100a)
Failed to open to WMI namespace '\\.\root\ccm' (8004100a)
CCMDoCertificateMaintenance() failed (0x8004100a).
Failed to open to WMI namespace '\\.\root\CCM\Events' (8004100a)
CCMDoCertificateMaintenance() raised CCM_ServiceHost_CertificateOperationsFailure status event.
Loading service settings.
Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8004100a)
Error loading service settings. Code 0x8004100a
Phase 0 initialization failed (0x8004100a).
Service initialization failed (0x8004100a).
Shutting down CCMEXEC..
UninitCommandExec failed (0x800401fb).
Please provide a solution.
Regards,
Boopathi S
June 7th, 2012 5:29am
try running this WMI fix batch file :-
open notepad and save the file as wmifix.bat
=====================
net stop winmgmt /y
c:
cd %systemroot%\system32\wbem
if exist %systemroot%\system32\wbem\repository.old rmdir /s /q repository.old
rename %systemroot%\system32\wbem\repository repository.old
for /f %%s in ('dir /b *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s
net start winmgmt
wmiprvse /regserver
net stop winmgmt /y
c:
cd %systemroot%\system32\wbem
if exist %systemroot%\system32\wbem\repository.old rmdir /s /q repository.old
rename %systemroot%\system32\wbem\repository repository.old
regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll
mofcomp cimwin32.mof
mofcomp cimwin32.mfl
mofcomp rsop.mof
mofcomp rsop.mfl
for /f %%s in ('dir /b *.dll') do regsvr32 /s %%s
for /f %%s in ('dir /b *.mof') do mofcomp %%s
for /f %%s in ('dir /b *.mfl') do mofcomp %%s
%systemroot%\system32\wbem\winmgmt /clearadap
%systemroot%\system32\wbem\winmgmt /kill
%systemroot%\system32\wbem\winmgmt /unregserver
%systemroot%\system32\wbem\winmgmt /regserver
%systemroot%\system32\wbem\winmgmt /resyncperf
=====================
restart the sms host service, the client will try a repair automatically.
Let me know how it went.
Free Windows Admin Tool Kit Click here and download it now
June 7th, 2012 5:36am
This exactly was the error in our environment and the below link is exactly what i did to get it back.
http://trevorsullivan.net/2009/11/06/wmi-repository-corruption-sccm-client-fix/
Check this and let me know.
Thanks
Arvind
June 7th, 2012 9:33am
What about to repair the WMI?
WMI Troubleshooting TipsSabrina
TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
June 7th, 2012 11:46pm
This will give you enough info abt WMI and its issue and the fixes for it.
http://technet.microsoft.com/en-us/library/ee692772.aspx
Let me know if this worked.
Thanks
Arvind
June 7th, 2012 11:52pm
Error 8004100A translates to:
WBEM_E_CRITICAL_ERROR
2147749898
0x8004100A Internal, critical, and unexpected error occurred. Report
theerror to Microsoft Technical Support.
I would try a wbemtest to see if the problem is with WMI as a whole or just CCM related classes (as the log above only shows errors with CCM related classes).
To do this, run an elevated "wbemtest.exe" on the affected machineClick on ConnectUnder namespace, ensure you have "root\cimv2" and click on Connect.This should take you back to the previous screen. Click on Enum Classes and OK on the Superclass Info windowOn the new window that appears, locate and double click Win32_USBDevice.Finally, on the new window that appears, click on instances.
If you managed to do all of the steps above without getting any errors, the "main part of WMI" seems fine and I would say the problem was that the SCCM client installation did not complete successfully and didn't register the WMI classes.
If that's the case, I would first try to uninstall the SCCM client and try reinstalling it again.
If you had errors whilst doing the wbemtest or reinstalling the SCCM client did not work, then I would say it looks more like the whole WMI might be corrupt you need to repair the WMI repository using the instructions provided by ArvindBS
Hope this helps!
Free Windows Admin Tool Kit Click here and download it now
June 8th, 2012 7:04am
This exactly was the error in our environment and the below link is exactly what i did to get it back.
http://trevorsullivan.net/2009/11/06/wmi-repository-corruption-sccm-client-fix/
Check this and let me know.
Thanks
Arvind
At least three other threads with Client issues and you quote the WMI repair link and mark as answer.
Wouldn't a test to see if root\CIMV2 is accessible using wbemtest be more appropriate? followed by a connection attempt to the root\CCM namespace? Surely if CIMV2 is accessible a Client Repair would be a more beneficial first step?
If you told someone to blow away their WMI repository and they ommited to say the Client was on their Site server, then you'd most likely be looking at a site repair, or maybe the Clients is on a member server running an app that does store data in WMI or
leans on it heavily, other products will lose a chunk of their world.
WMI repository is a very last step not the first.
June 8th, 2012 3:33pm
Do you know how to use wbemtest?
http://technet.microsoft.com/en-us/library/cc781653(v=ws.10).aspx
If you get results back from wbemtest connecting to root\cimv2 (select enum classes, select recursive, select ok), then most likely its not corrupted, if this is the case try initiating a ConfigMgr Client repair and see if root\ccm becomes accessible again
using the log you got the paste above from or wbemtest
Free Windows Admin Tool Kit Click here and download it now
June 8th, 2012 3:37pm