I have SCCM 2007 SP2 on a windows 2008 R2 server. The server is the primary site as well as the DP, FSP, MP, and SUP.

I have successfully deployed one single update. Ever since then I have been seeing this in my windowsupdate.log right after the deadline for the updates:

2011-08-19 11:41:12:708  836 ef8 AU Triggering AU detection through DetectNow API
2011-08-19 11:41:12:708  836 ef8 AU Triggering Online detection (non-interactive)
2011-08-19 11:41:12:708  836 dfc AU #############
2011-08-19 11:41:12:708  836 dfc AU ## START ##  AU: Search for updates
2011-08-19 11:41:12:708  836 dfc AU #########
2011-08-19 11:41:12:709  836 dfc AU <<## SUBMITTED ## AU: Search for updates [CallId = {1E1BF5B8-0236-4441-907A-4BDF8D80635F}]
2011-08-19 11:41:12:710  836 420 Agent *************
2011-08-19 11:41:12:710  836 420 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2011-08-19 11:41:12:710  836 420 Agent *********
2011-08-19 11:41:12:710  836 420 Agent   * Online = Yes; Ignore download priority = No
2011-08-19 11:41:12:710  836 420 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2011-08-19 11:41:12:710  836 420 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2011-08-19 11:41:12:710  836 420 Agent   * Search Scope = {Machine}
2011-08-19 11:41:12:710  836 420 Setup Checking for agent SelfUpdate
2011-08-19 11:41:12:710  836 420 Setup Client version: Core: 7.5.7601.17514  Aux: 7.5.7601.17514
2011-08-19 11:41:12:710  836 420 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2011-08-19 11:41:12:715  836 420 Misc  Microsoft signed: Yes
2011-08-19 11:41:12:718  836 420 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2011-08-19 11:41:12:721  836 420 Misc  Microsoft signed: Yes
2011-08-19 11:41:12:722  836 420 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2011-08-19 11:41:12:725  836 420 Misc  Microsoft signed: Yes
2011-08-19 11:41:12:727  836 420 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2011-08-19 11:41:12:729  836 420 Misc  Microsoft signed: Yes
2011-08-19 11:41:12:742  836 420 Setup Determining whether a new setup handler needs to be downloaded
2011-08-19 11:41:12:743  836 420 Setup SelfUpdate handler is not found.  It will be downloaded
2011-08-19 11:41:12:743  836 420 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7600.226"
2011-08-19 11:41:12:745  836 420 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7600.226" is not applicable
2011-08-19 11:41:12:746  836 420 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226"
2011-08-19 11:41:12:768  836 420 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226" is not applicable
2011-08-19 11:41:12:768  836 420 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226"
2011-08-19 11:41:12:801  836 420 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7600.226" is not applicable
2011-08-19 11:41:12:801  836 420 Setup SelfUpdate check completed.  SelfUpdate is NOT required.
2011-08-19 11:41:13:022  836 420 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
2011-08-19 11:41:13:022  836 420 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://site.domain.com/ClientWebService/client.asmx
2011-08-19 11:41:13:084  836 420 PT WARNING: Cached cookie has expired or new PID is available
2011-08-19 11:41:13:085  836 420 PT Initializing simple targeting cookie, clientId = e61e59ee-7164-4cc0-9af6-b1c8469dca59, target group = , DNS name = site.domain.com
2011-08-19 11:41:13:085  836 420 PT   Server URL = http://ssite.domain.com/SimpleAuthWebService/SimpleAuth.asmx
2011-08-19 11:41:13:088  836 420 PT WARNING: GetAuthorizationCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
2011-08-19 11:41:13:088  836 420 PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80244019
2011-08-19 11:41:13:088  836 420 PT WARNING: PopulateAuthCookies failed: 0x80244019
2011-08-19 11:41:13:088  836 420 PT WARNING: RefreshCookie failed: 0x80244019
2011-08-19 11:41:13:088  836 420 PT WARNING: RefreshPTState failed: 0x80244019
2011-08-19 11:41:13:088  836 420 PT WARNING: Sync of Updates: 0x80244019
2011-08-19 11:41:13:088  836 420 PT WARNING: SyncServerUpdatesInternal failed: 0x80244019
2011-08-19 11:41:13:088  836 420 Agent   * WARNING: Failed to synchronize, error = 0x80244019
2011-08-19 11:41:13:089  836 420 Agent   * WARNING: Exit code = 0x80244019
2011-08-19 11:41:13:089  836 420 Agent *********
2011-08-19 11:41:13:089  836 420 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2011-08-19 11:41:13:089  836 420 Agent *************
2011-08-19 11:41:13:089  836 420 Agent WARNING: WU client failed Searching for update with error 0x80244019
2011-08-19 11:41:13:095  836 e08 AU >>##  RESUMED  ## AU: Search for updates [CallId = {1E1BF5B8-0236-4441-907A-4BDF8D80635F}]
2011-08-19 11:41:13:095  836 e08 AU   # WARNING: Search callback failed, result = 0x80244019
2011-08-19 11:41:13:095  836 e08 AU   # WARNING: Failed to find updates with error code 80244019
2011-08-19 11:41:13:095  836 e08 AU #########
2011-08-19 11:41:13:095  836 e08 AU ##  END  ##  AU: Search for updates [CallId = {1E1BF5B8-0236-4441-907A-4BDF8D80635F}]
2011-08-19 11:41:13:095  836 e08 AU #############
2011-08-19 11:41:13:095  836 e08 AU Successfully wrote event for AU health state:0
2011-08-19 11:41:13:096  836 e08 AU AU setting next detection timeout to 2011-08-19 20:41:13
2011-08-19 11:41:13:096  836 e08 AU Setting AU scheduled install time to 2011-08-20 07:00:00
2011-08-19 11:41:13:096  836 e08 AU Successfully wrote event for AU health state:0
2011-08-19 11:41:13:096  836 e08 AU Successfully wrote event for AU health state:0
2011-08-19 11:41:18:089  836 420 Report REPORT EVENT: {5E7F3D02-C243-49E4-B92A-CB84FC2C5F1B} 2011-08-19 11:41:13:089-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244019 AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x80244019.
2011-08-19 11:41:18:109  836 420 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2011-08-19 11:41:18:109  836 420 Report WER Report sent: 7.5.7601.17514 0x80244019 00000000-0000-0000-0000-000000000000 Scan 101 Managed
2011-08-19 11:41:18:110  836 420 Report CWERReporter finishing event handling. (00000000)

I am even getting the error code 0x80244019 when I go on a client and try to run a Windows Update check for updates.

I have gone through every technet article on here about 0x80244019 and my problem remains unsolved.

In my GPO I have set the 'Specify intranet Microsoft update service location' to point to my SUP.

What can I do to resolve this problem?

 

• Edited by Sam Edson Friday, August 19, 2011 7:38 PM

"I have gone through every technet article on here about 0x80244019 and my problem remains unsolved."

I suggest you open a call with Microsoft.  If you've already done a ton of research on 0x80244019, and none of the fixes you've found address your issue, I suggest you open a call.

Hmm do you really think that will be necessary? I am thinking about removing the SUP role and reinstalling WSUS then adding the SUP role again. If I still get this problem after that I could consider calling.

Oh it is also worth mentioning - after I first noticed these warnings/errors, I tried to deploy two separate update lists to one server. Over night, despite the warnings/errors, the server installed about half the updates from each package. This was weird to me because I had it set to install the updates immediatly at the deadline which was right after the deployment. Since then, however, no updates have been installed.

I now have a much better understanding of the problem. We can see here in the log:

2011-08-19 11:41:13:022  836 420 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://site.domain.com/ClientWebService/client.asmx
2011-08-19 11:41:13:084  836 420 PT WARNING: Cached cookie has expired or new PID is available
2011-08-19 11:41:13:085  836 420 PT Initializing simple targeting cookie, clientId = e61e59ee-7164-4cc0-9af6-b1c8469dca59, target group = , DNS name = site.domain.com
2011-08-19 11:41:13:085  836 420 PT   Server URL =  http://site.domain.com/SimpleAuthWebService/SimpleAuth.asmx

2011-08-19 11:41:13:088  836 420 PT WARNING: GetAuthorizationCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404

That the errors are occuring because it is trying to connect to an invalid URL (hence the 404). Both of those URLs are under the Default Web Site in IIS using port 80. The SimpleAuth.asmx and the client.asmx both live in the same directory on the WSUS Administration site (port 8530). If we just simply add the WSUS Administration port at the end so it is http://site.domain.com:8530/SimpleAuthWebService/SimpleAuth.asmx this link will work on the client.

For some reason, it is trying to use SCCM's port 80 rather than WSUS's port 8530. My question now is how do I point it in the right direction and get it to use 8530?

 

 

 

Further research shows the exact problem as seen in wuahandler.log on a client:

<![LOG[Enabling WUA Managed server policy to use server: http://site.domain.com:8530]LOG]!><time="13:27:25.298+240" date="08-19-2011" component="WUAHandler" context="" type="1" thread="3624" file="sourcemanager.cpp:1054">
<![LOG[Waiting for 2 mins for Group Policy to notify of WUA policy change...]LOG]!><time="13:27:25.309+240" date="08-19-2011" component="WUAHandler" context="" type="1" thread="3624" file="sourcemanager.cpp:1060">
<![LOG[Group policy settings were overwritten by a higher authority (Domain Controller) to: Server http://site.domain.com and Policy ENABLED]LOG]!><time="13:27:26.634+240" date="08-19-2011" component="WUAHandler" context="" type="3" thread="3624" file="sourcemanager.cpp:1116">
<![LOG[Failed to Add Update Source for WUAgent of type (2) and id ({83D2BC47-986C-41F7-AFEA-5743B4782BDF}). Error = 0x80040692.]LOG]!><time="13:27:26.635+240" date="08-19-2011" component="WUAHandler" context="" type="3" thread="3624" file="cwuahandler.cpp:2358">

So the domain controller is setting it back to the default site on port 80. Now I need to know how I get around this!

And the problem has been solved by changing the domain controller's GPO intranet settings to point to site.domain.com:8530 rather than the local system's GPO.

• Marked as answer by Sam Edson Friday, August 19, 2011 9:33 PM

Hi,

I want to confirm that in my environment with SCCM 2007 in place  0x80244019  was found to be caused by missing SelfUpdate Virtual Directory in the WSUS and Default(80) website. This was successfully resolved by recreating the selfupdate website by following http://technet.microsoft.com/en-us/library/ff646934(v=ws.10).aspx

I had the same problem, literally weeks of off and on trying to fix this in my lab and finally it was fixed by adding the port to the WSUS server.  Example:"http://TL-WSUS:8530", instead of "http://TL-WSUS", as suggested by Sam Edson.  It should also be noted that if you disconnect your WSUS from the internet after a sync, as I was, that it takes several hours in some cases to get all of the updates.