EditWiki Resources
EditExternal Resources
Problem: SMS client does not install, error in client.msi that reads
Failed to connect to server. Error: 0x80070424
Solution: Reinstall Windows Installer.
Problem: The
SMS Agent Host service will not start. Error in CCMExec.log that states:
ERROR!! WBEM not found in the system path.
Failed to open to WMI namespace
Solution: This error may occur because the WBEM path is not listed in the system path, or because the type of the
Path registry entry is not of type
REG_EXPAND_SZ -
http://support.microsoft.com/kb/922362Problem: When launching a "Download and Execute" installation, you receive the following error:
The program for advertisement "AdvertisementID has failed because content download for the package "PackageID" - "ProgramName" has failed.
The download failed because the content downloaded to the client does not match the content specified in the package source.
You may also see the following in the Execmgr.log:
OnContentAvailable program ProgramName NOT available, 0x80091007 Fatal error 0x80008602 encountered for program ProgramName. This program will not retry.
And in Cas.log:
Download completed for content package ID.version under context System Hash does not match expected storedHash, actual calculatedHash
Download failed for content package ID.version under context System, error 0x80091007 Successfully raised SoftDistHashMismatchEvent event.
Solution: You may have a package hash mismatch:
http://support.microsoft.com/kb/907979Alternative Solution: In one particular environment I work in we frequently see hash errors that are not related to the content on the DP not matching the content on the primary server as noted above. The frequency we see it is approx 10 in 6,000 installs. We have worked on finding the root cause of the issue for quite a while. both Microsot and Dell Professional service have been on site and could not find a solution, much less identify the root cause. As a workaround we have a script that monitors the SMS DB for HASH error messages and when it finds them it tells the client to re-run the failed program. This has mitigated the affects of the hash errors; however we are still interested in finding the root cause. I will be posting the script to look for and rerun the ads on selected client soon. If you are experienceing this issue feel free to contact me for a copy. Perhaps we can work together to find a solution. hemsell AT gmail DOT com.