SCCM 2007 Troubleshooting Software Updates Client Issues

Troubleshooting Software Updates Client Issues


Client Scan Fails with Error 0x80040693


In the Microsoft System Center Configuration Manager 2007 console, view any reports in the category Software Updates - E. Troubleshooting. If a Configuration Manager 2007 client reports the error code 0x80040693, it means the client is running the wrong version of Windows Update Agent (WUA). Configuration Manager 2007 clients require version 7.0.6000.374 or higher. 


Possible Solution
If client computers are configured for Automatic Update, they should automatically update their Windows Update Agent from their Automatic Update source. If clients are not configured for Automatic Update, you can locate the WUA redistributable file wuredist.cab on MSDN and deploy it using Configuration Manager 2007 software distribution.


Software Update Installation Fails with Error 0x80091007
Before a Configuration Manager 2007 client can install software updates, it verifies the hash on the content containing the software update. If the hash does not match, the client fails to install the software update and logs error 0x80091007 to the updatesdeployment.log on the client. The error is also sent to the management point and is visible in the reports under the category Software Updates - E. Troubleshooting.
This issue is often caused by having the wrong version of the package on the distribution point. Frequently this issue occurs when content has not been replicated to a child site or when the package version has changed but the client has not received new policy yet.


Possible Solution
In the Configuration Manager 2007 console, navigate to System Center Configuration Manager / Site Database / Computer Management / Software Updates / Deployment Packages / / Package Status / Package Status / , and look at the source version for the package. Verify that all distribution points are using the same source version, including any distribution points at the child site. You can also look at distmgr.log for any errors that reference the package ID.


Software Update Installation Fails with Error = 0x80004002
A client computer fails to install a software update with the 0x80004002 error message reported in the client log files, such as the following sample log entries:
UpdatesHandler.log 


WSUS update (689c410a-44d7-45c7-ae51-9806fcb177f5) installation result = 0x80004002, Reboot State = NoReboot 
Update execution failed. 


WUAHandler.log 


Failed to get final installation result of updates. Error = 0x80004002. 
Update 1 () finished installing (0x80004002). 
Update 2 () finished installing (0x80004002). 
Installation of updates completed. 


WindowsUpdate.log 


WARNING: WU client failed installing updates with error 0x80004002 
The UpdatesHandler.log and WUAHandler.log files are located in \Logs, and the WindowsUpdate.log is located in %windir%.


Possible Solution


The WUA installation on the client might be missing files or be corrupt. Reinstall WUA 3.0 on the client computer. For more information about installing WUA 3.0, 












Comments

  1. ColtonSeptember 25, 2023 at 5:40 AM

    Software in SCCM 2007 demands it. This involves identifying and addressing deployment, installation. Create A Compitition A systematic diagnosis and resolution process ensures smooth software. This blog is helpful.

    ReplyDelete

Post a Comment

Popular posts from this blog

ConfigMgr 2012+ Version Numbers

Release Version Build Baseline D/L Link Our Guides SCCM 2012 RTM 5.00.7711.0000 7711 N/A N/A N/A SCCM 2012 RTM - CU1 5.00.7711.0200 7711 N/A KB2717295 N/A SCCM 2012 RTM - CU2 5.00.7711.0301 7711 N/A KB2780664 N/A SCCM 2012 SP1 5.00.7804.1000 7804 N/A N/A N/A SCCM 2012 SP1 - CU1 5.00.7804.1202 7804 N/A KB2817245 N/A SCCM 2012 SP1 - CU2 5.00.7804.1300 7804 N/A KB2854009 N/A SCCM 2012 SP1 - CU3 5.00.7804.1400 7804 N/A KB2882125 N/A SCCM 2012 SP1 - CU4 5.00.7804.1500 7804 N/A KB2922875 N/A SCCM 2012 SP1 - CU5 5.00.7804.1600 7804 N/A KB2978017 N/A SCCM 2012 R2 5.00.7958.1000 7958 N/A N/A Installation guide SCCM 2012 R2 - CU1 5.00.7958.1203 7958 N/A KB2938441 N/A SCCM 2012 R2 - CU2 5.00.7958.1303 7958 N/A KB2970177 Upgrade guide SCCM 2012 R2 - CU3 5.00.7958.1401 7958 N/A KB2994331 Upgrade guide SCCM 2012 R2 - CU4 5.00.7958.1501 7958 N/A KB3026739 Upgrade guide SCCM 2012 R2 - CU5 5.00.7958.1604 7958 N/A KB3054451 Upgrade guide SCCM 2012 R2 SP1 5.00.8239.1000 8239 N/A N/A Up
Read more

Steps to recreate WMI and Repair Corrupt WMI Services

WMI Error messages in execmgr.log file on 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
Read more

SCCM Software updates error WUAHandler.log errors

If you find errors in the WUAHandler.log as below "OnSearchComplete - Failed to end Search job. Error = 0x80072efd Scan failed with error = 0x80072efd" Error 0x80072efd means: 'The attempt to connect to the server failed. Can you check the following logs for more information "%Windir%\WindowsUpdate.log and ScanAgent.log Server not being able to talk to the WSUS server because port 8530 might be blocked lack of  communication  between the client and the SCCM sup if you are working with custom WSUS ports. Do not forget to open the used ports in the Windows Firewall Create a rule for inbound TCP (WSUS ports). In my case it was for 8530 and 8531. 
Read more