in my case I hade some Problems with the WSUS-Updates on a customer, that is what I get to solve it:
I found in the WUAHandler.log and the same error code in the UpdatetStore.log on the client
Scan results will include all superseded updates. WUAHandler 23.07.2014 11:20:07 6848 (0x1AC0)
Search Criteria is (DeploymentAction=* AND Type=’Software’) OR (DeploymentAction=* AND Type=’Driver’) WUAHandler 23.07.2014 11:20:07 6848 (0x1AC0)
Async searching of updates using WUAgent started. WUAHandler 23.07.2014 11:20:07 6848 (0x1AC0)
Async searching completed. WUAHandler 23.07.2014 11:20:10 1604 (0x0644)
OnSearchComplete-Failed to end search job. Error=0x80244018. WUAHandler 6848 (0x1AC0)
Scan failed with error = 0x80244018. WUAHandler 23.07.2014 11:20:10 6848 (0x1AC0)
on the same time in the WindowsUpdate.log are the same error:
2014-07-23 11:20:10:317 928 1f04 PT WARNING: GetAuthorizationCookie failure, error = 0x80244018, soap client error = 10, soap error code = 0, HTTP status code = 403
2014-07-23 11:20:10:317 928 1f04 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244018
2014-07-23 11:20:10:317 928 1f04 PT WARNING: PopulateAuthCookies failed: 0x80244018
2014-07-23 11:20:10:317 928 1f04 PT WARNING: RefreshCookie failed: 0x80244018
2014-07-23 11:20:10:317 928 1f04 PT WARNING: RefreshPTState failed: 0x80244018
2014-07-23 11:20:10:317 928 1f04 PT WARNING: Sync of Updates: 0x80244018
2014-07-23 11:20:10:317 928 1f04 PT WARNING: SyncServerUpdatesInternal failed: 0x80244018
2014-07-23 11:20:10:317 928 1f04 Agent * WARNING: Failed to synchronize, error = 0x80244018
2014-07-23 11:20:10:317 928 1f04 Agent * WARNING: Exit code = 0x80244018
after a search on my favorite search engine I found that link here: http://social.technet.microsoft.com/Forums/en-US/f5a273fe-2e23-475e-a778-e379689658b4/updatesstorelog-show-error-0x87d00310 he talked about the Error codes with a hint to this Link here, it is for SCCM 2007 but the most error codes still the same: http://technet.microsoft.com/en-us/library/bb632794.aspx
After this I was looking for that Proxy “Problem”;
netsh winhttp show proxy
there are some settings, customer says they are never used this settings, they configured the Proxy with GPO. OK in this case we clean those settings:
Here is also a good description about this Settings: http://support.microsoft.com/kb/900935/de
netsh winhttp reset proxy
after reset the Proxy settings on the Client we started the client scan again and now it’s working fine…
Hope it helps, have fun and be careful in your Production, test it first “it is as it”
Mirko
Leave a Reply