We help IT Professionals succeed at work.

Windows Update Scan failed x80244019

Eneboer
Eneboer asked
on
Hi all,

all clients in our enterprise failed to scan for updates with following error:

GetAuthorizationCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404

WUAHandler.log

WindowsUpdate.log

Environement:

1 x Windows Server 2008 (SCCM 2007 R3, FEP, WSUS3.0 SP2)
1 x Windows Server 2008 (SQL Server 2008)

Please help in attachment you find WUAHandler.log and WindowsUpdate.log
Comment
Watch Question

Commented:
Appears server related what does your WSUSCtrl.log look like?

Author

Commented:
look's like everything is fine in WSUSCtrl.log
WSUSCtrl.log

Commented:
the root error there is 404. have you confirmed WSUS is configured on http://MCHSV011.SIPLACEWORLD.NET:8530?

Are there any events in the application log in relation to WSUS?

Author

Commented:
when I'm searching directly for WSUS events, i got only "WSUS is working correctly"

the only error event in application log is following:

"Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: A required certificate is not within its validity period when verifying against the current system clock or the timestamp in the signed file."

Commented:
That event in the application log can be ignored.

Lets track this backwards. Enable logging on the IIS instance that WSUS is using. From an SCCM client initiate the "Software updates scan cycle" action review the windowsupdate.log file to ensure it ran a discovery then check the IIS log server side

Author

Commented:
in IIS log i found this entry for the test client's ip address

2012-03-12 15:47:02 10.70.1.11 CCM_POST /ccm_system/request - 8080 - 10.70.6.27 ccmhttp 200 0 0 0
Commented:
That appears unrelated to WSUS/SUP ensure your looking at the correct log directory

In all honesty unless your using SCUP you loose nothing by removing the SUP role then uninstalling WSUS rebooting and re-installing WSUS and the SUP role. Ensure when you install WSUS to not configure it (hit cancel on second wizard) SCCM only uses WSUS to sync the catalog and determine updates to deploy

Author

Commented:
after new installation of WSUS and SUP, i get following messages in WSUSCtrl.log

Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111      SMS_WSUS_CONTROL_MANAGER      13.03.2012 09:49:59      8908 (0x22CC)
Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001      SMS_WSUS_CONTROL_MANAGER      13.03.2012 09:49:59      8908 (0x22CC)
The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226)      SMS_WSUS_CONTROL_MANAGER      13.03.2012 09:49:59      8908 (0x22CC)
STATMSG: ID=7000 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONTROL_MANAGER" SYS=MCHSV011 SITE=E01 PID=2548 TID=8908 GMTDATE=Di Mrz 13 08:49:59.723 2012 ISTR0="MCHSV011" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0      SMS_WSUS_CONTROL_MANAGER      13.03.2012 09:49:59      8908 (0x22CC)
Failed to set WSUS Local Configuration. Will retry configuration in 1 minutes      SMS_WSUS_CONTROL_MANAGER      13.03.2012 09:49:59      8908 (0x22CC)
STATMSG: ID=7003 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONTROL_MANAGER" SYS=MCHSV011 SITE=E01 PID=2548 TID=8908 GMTDATE=Di Mrz 13 08:49:59.738 2012 ISTR0="MCHSV011" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0      SMS_WSUS_CONTROL_MANAGER      13.03.2012 09:49:59      8908 (0x22CC)
Failures reported during periodic health check by the WSUS Server MCHSV011. Will retry check in 1 minutes      SMS_WSUS_CONTROL_MANAGER      13.03.2012 09:49:59      8908 (0x22CC)

Commented:
What does you WCM.log show? i suspect we'll see errors

very likely something along these lines,

http://social.technet.microsoft.com/Forums/en-US/configmgrsum/thread/0d79184d-4bd4-42ff-b887-b48d75768230/

Author

Commented:
after 2nd new installation, it works fine