error when installing client for certain computers
Hi All, I have a interesting issue with a number of computers that I'm trying to install the client onto. to give background, these computers have been migrated from an old domain into our new domain. The caveat is that they had a SCCM environment in this old domain and thus has a previous sccm client installed. for the majority of these clients, the simple act of uninstalling the client and then reinstalling is good enough to get the clients into the new SCCM environment in the new domain, however, there are a number of machines that are sticking on the same issue, whatever that might be. I am adding a few significant lines from the ccmsetup.log file. There doesn't seem to be much at all about this on the internet and thus would think this has not occurred that much for anyone. the error seems to be trying to access the ccm namespace in WMI. the error code it suggests relates to an access denied event. The strange thing is that it is not occuring for all computers. it seems to be only a handful of machines that this happens too. any help would be greatly appreciated.... sample txt ( I have bolded the relevant parts): Updated security on object C:\WINDOWS\system32\ccmsetup\. ccmsetup 20-1-2011 8:28:49 3552 (0x0DE0) Sending Fallback Status Point message, STATEID='100'. ccmsetup 20-1-2011 8:28:49 3552 (0x0DE0) Failed to open to WMI namespace '\\.\root\ccm' (80070005) ccmsetup 20-1-2011 8:28:49 3552 (0x0DE0) Failed to open to WMI namespace '\\.\root\ccm' (80070005) FSPStateMessage 20-1-2011 8:28:49 3552 (0x0DE0) State message with TopicType 800 and TopicId {9B32CAC0-402A-4403-904C-2F61A448B705} has been sent to the FSP FSPStateMessage 20-1-2011 8:28:50 3552 (0x0DE0) Running as user "SYSTEM" ccmsetup 20-1-2011 8:28:50 2308 (0x0904) Detected 112967 MB free disk space on system drive. ccmsetup 20-1-2011 8:28:50 2308 (0x0904) DetectWindowsEmbeddedFBWF() Detecting OS Version ccmsetup 20-1-2011 8:28:50 2308 (0x0904) Client OS Version is 5.1, Service Pack Version 3 ccmsetup 20-1-2011 8:28:50 2308 (0x0904) Client OS is not a supported Windows Embedded Platform ccmsetup 20-1-2011 8:28:50 2308 (0x0904) The 'Certificate Store' is empty in the registry, using default store name 'MY'. ccmsetup 20-1-2011 8:28:51 2308 (0x0904) The 'Certificate Selection Criteria' was not specified, counting number of certificates present in 'MY' store of 'Local Computer'. ccmsetup 20-1-2011 8:28:51 2308 (0x0904) 1 certificate(s) found in the 'MY' certificate store. ccmsetup 20-1-2011 8:28:51 2308 (0x0904) Only one certificate present in the certificate store. ccmsetup 20-1-2011 8:28:51 2308 (0x0904) SSL Registry key Software\Microsoft\CCM not found, assuming Client SSL is disabled. ccmsetup 20-1-2011 8:28:51 2308 (0x0904) The certificate issued to 'MADING10127.corp.com' has 'Client Authentication' capability. ccmsetup 20-1-2011 8:28:52 2308 (0x0904) Using the certificate issued to 'MADING10127.corp.com'. ccmsetup 20-1-2011 8:28:52 2308 (0x0904) IsFileMicrosoftTrusted Verified file 'C:\WINDOWS\system32\ccmsetup\WindowsXP-KB923845-x86-ESN.exe' is MS signed. ccmsetup 20-1-2011 8:28:54 2308 (0x0904) Installing file 'C:\WINDOWS\system32\ccmsetup\WindowsXP-KB923845-x86-ESN.exe' with options '/norestart /quiet /log:C:\WINDOWS\system32\ccmsetup\WindowsXP-KB923845-x86-ESN.exe.log'. ccmsetup 20-1-2011 8:28:54 2308 (0x0904) File 'C:\WINDOWS\system32\ccmsetup\WindowsXP-KB923845-x86-ESN.exe' returned exit code 1603. ccmsetup 20-1-2011 8:29:04 2308 (0x0904) Finished installing file 'C:\WINDOWS\system32\ccmsetup\WindowsXP-KB923845-x86-ESN.exe'. ccmsetup 20-1-2011 8:29:04 2308 (0x0904) Successfully ran BITS check. ccmsetup 20-1-2011 8:29:04 2308 (0x0904) The site is in Native Mode. A client reboot is required to continue installation. ccmsetup 20-1-2011 8:29:04 2308 (0x0904) Sending Fallback Status Point message, STATEID='317'. ccmsetup 20-1-2011 8:29:04 2308 (0x0904) Failed to open to WMI namespace '\\.\root\ccm' (80070005) ccmsetup 20-1-2011 8:29:04 2308 (0x0904) Failed to open to WMI namespace '\\.\root\ccm' (80070005) FSPStateMessage 20-1-2011 8:29:04 2308 (0x0904) State message with TopicType 800 and TopicId {8CBA058D-6A01-43A8-A784-C896C97C05C9} has been sent to the FSP FSPStateMessage 20-1-2011 8:29:04 2308 (0x0904) Deleted file C:\WINDOWS\system32\ccmsetup\WindowsXP-KB923845-x86-ESN.exe ccmsetup 20-1-2011 8:29:11 3552 (0x0DE0)
January 20th, 2011 8:41am

It's most likely caused by a corrupt WMI repository. Have you already tried repairing it?
Free Windows Admin Tool Kit Click here and download it now
January 20th, 2011 8:55am

unfortunately, yes.... didn't seem to make any difference. I'm assuming it must be something to do with the WMI but it is not one I have come across before. I have come across client failures due to WMI before and as you say, repairing it normally works. the only difference from normal wmi failures is the fact that these machines are coming in from a previous different SCCM environment and the errors seem to be different to the usual ones that point to wmi. It's a weird one ...
January 20th, 2011 3:31pm

I have same issue , tried to rebuild repository or register again but didnt help. MSI: Action 15:06:54: CcmCreateWmiNamespaces. Creating WMI namespaces MSI: Setup was unable to create the WMI namespace CCM The error code is 80070005 MSI: Warning 25101. Setup was unable to delete WMI namespace ccm\dcm The error code is 80070005 Installation failed with error code 1603
Free Windows Admin Tool Kit Click here and download it now
February 18th, 2011 2:30pm

80070005 means "Access Denied". Considering the SCCM agent setup process/service is undering Local System Permission, it may cause by the Local System failed to open the CCM client namespace, or it may relate to the DCOM permission. My suggestions would be as following. 1. Check whether you can open the above namespace (or at least \root ) on the problematic machine through Local System Permssion(launch through at or psexec, then use wbemtest.exe to do the test) 2. Process Monitor trace woul help for the troubleshooting.
February 19th, 2011 9:46am

I found it ! OS temp directory should be "%systemroot%/temp" and "%systemroot%/tmp" But it was "%USERPROFILE%\Local Settings\Temp" I fixed it and now everything great !
Free Windows Admin Tool Kit Click here and download it now
February 24th, 2011 8:01pm

I ve added LOCAL SERVICE, NETWORK SERVICE, and SYSTEM accounts to Local administrators group and now there is no 80070005 error , but ; MSI: Setup was unable to compile the file ccmclasses.mof The error code is 8004402F MSI: Warning 25002. Failed to delete CCM_Service_ErrorHandlerRegistration.Clsid="{0F95BCE5-2209-488a-B4BC-4396AD233C8D}" from CCM The error code is 80041010
February 24th, 2011 8:19pm

MSI: Setup was unable to compile the file ccmclasses.mof The error code is 8004402F That error translates to "Error creating temporary file. Source: Windows Management (WMI)". That might give a hint (any GPOs in place? Security settings? Hardening?)Torsten Meringer | http://www.mssccmfaq.de
Free Windows Admin Tool Kit Click here and download it now
February 24th, 2011 8:31pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics