[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5264
  • Last Modified:

Software Updates Scan Agent failed on clients

Scan component (type=Microsoft Update) failed. A failure code of 16409 was returned.

The above Error recived .
0
Arabsoft-ACS
Asked:
Arabsoft-ACS
1 Solution
 
FayazCommented:
Have look at below KB and additionally post the log file from C:\Windows\WindowsUpdate.log
http://support.microsoft.com/kb/938440
0
 
Arabsoft-ACSAuthor Commented:
Actually we are using SCCM 2007 R2 and for your concern i attach the log:
hope you asking the client windowsupdate.log.

client windows update log.
2010-01-05      13:25:11:807      1392      5b3c      PT      WARNING: RefreshPTState failed: 0x80244019
2010-01-05      13:25:11:807      1392      5b3c      PT      WARNING: PTError: 0x80244019
2010-01-05      13:25:11:807      1392      5b3c      Report      WARNING: Reporter failed to upload events with hr = 80244019.
2010-01-05      13:49:37:064      1392      6354      PT      WARNING: GetConfig failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2010-01-05      13:49:37:064      1392      6354      PT      WARNING: PTError: 0x80244019
2010-01-05      13:49:37:064      1392      6354      PT      WARNING: GetConfig_WithRecovery failed: 0x80244019
2010-01-05      13:49:37:064      1392      6354      PT      WARNING: RefreshConfig failed: 0x80244019
2010-01-05      13:49:37:064      1392      6354      PT      WARNING: RefreshPTState failed: 0x80244019
2010-01-05      13:49:37:064      1392      6354      PT      WARNING: PTError: 0x80244019
2010-01-05      13:49:37:064      1392      6354      Report      WARNING: Reporter failed to upload events with hr = 80244019.
2010-01-05      14:15:51:573      1392      6884      PT      WARNING: GetConfig failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2010-01-05      14:15:51:573      1392      6884      PT      WARNING: PTError: 0x80244019
2010-01-05      14:15:51:573      1392      6884      PT      WARNING: GetConfig_WithRecovery failed: 0x80244019
2010-01-05      14:15:51:573      1392      6884      PT      WARNING: RefreshConfig failed: 0x80244019
2010-01-05      14:15:51:573      1392      6884      PT      WARNING: RefreshPTState failed: 0x80244019
2010-01-05      14:15:51:573      1392      6884      PT      WARNING: PTError: 0x80244019
2010-01-05      14:15:51:573      1392      6884      Report      WARNING: Reporter failed to upload events with hr = 80244019.


0
 
anubhavsharma18Commented:
If you have any group policy configured for the client to point to WSUS then remove it as SCCM software update agent takes care of that
0
Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

 
Arabsoft-ACSAuthor Commented:
No we don't have any GPO set specially for WSUS but one GPO set for configuer automatic updates :
auto download and schedule the install.
one more thing i notice that this problem can appear mostly on windows xp sp3 clients:
for your concern i will past more logs:

its wuAHandler.log
OnSearchComplete - Failed to end search job. Error = 0x80244019.      
Scan failed with error = 0x80244019.

and one more thing the one more Group policy are set on over SCCM 2007 server that windows Update\specify intranet Microsoft update service location :

enbaled : ( mention in URL \\ sccm server name :80)
0
 
Donald StewartNetwork AdministratorCommented:
Under both options in your GPO for "Specify intranet Microsoft update service" you should have...
 
Http://sccm server name  <<<without ":80"
 
Error = 0x80244019 usually means that the virtual selfupdate folder is missing in IIS under port 80
 
You can run this command
 C:%ProgramFiles%/Update Services/Setup/InstallSelfupdateOnPort80.vbs
0
 
Donald StewartNetwork AdministratorCommented:
A little more reading suggests that with sccm you should remove the group policy settings for windows updates and that configmgr will handle this
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now