Windows Server - WARNING: GetAuthorizationCookie failure, error = 0x80244019, soap

Asked By Anatol on 31-Aug-07 10:16 PM
Hi,

None of my client PCs, nor even my WSUS server can connect to WSUS 3.0. The
logs are below... Is there anyone that can help me out... I'm running WSUS on
a Windows 2003 server...

--------------------------------------------------------------------------------------------

2007-09-01	13:54:41:019	 544	d1c	AU	Triggering AU detection through
DetectNow API
2007-09-01	13:54:41:019	 544	d1c	AU	Triggering Online detection
(non-interactive)
2007-09-01	13:54:41:019	 544	13b8	AU	#############
2007-09-01	13:54:41:019	 544	13b8	AU	## START ##  AU: Search for updates
2007-09-01	13:54:41:019	 544	13b8	AU	#########
2007-09-01	13:54:41:021	 544	13b8	AU	<<## SUBMITTED ## AU: Search for
updates [CallId = {6770E6AC-AAE2-410E-9C3B-4C6C2E566F9C}]
2007-09-01	13:54:41:021	 544	1128	Agent	*************
2007-09-01	13:54:41:021	 544	1128	Agent	** START **  Agent: Finding updates
[CallerId = AutomaticUpdates]
2007-09-01	13:54:41:021	 544	1128	Agent	*********
2007-09-01	13:54:41:021	 544	1128	Agent	  * Online = Yes; Ignore download
priority = No
2007-09-01	13:54:41:021	 544	1128	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"
2007-09-01	13:54:41:021	 544	1128	Agent	  * ServiceID =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2007-09-01	13:54:41:021	 544	1128	Setup	Checking for agent SelfUpdate
2007-09-01	13:54:41:022	 544	1128	Setup	Client version: Core: 7.0.6000.381
Aux: 7.0.6000.381
2007-09-01	13:54:41:022	 544	1128	Misc	Validating signature for
C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2007-09-01	13:54:41:028	 544	1128	Misc	 Microsoft signed: Yes
2007-09-01	13:54:41:033	 544	1128	Misc	Validating signature for
C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2007-09-01	13:54:41:037	 544	1128	Misc	 Microsoft signed: Yes
2007-09-01	13:54:41:041	 544	1128	Misc	Validating signature for
C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2007-09-01	13:54:41:046	 544	1128	Misc	 Microsoft signed: Yes
2007-09-01	13:54:41:049	 544	1128	Misc	Validating signature for
C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2007-09-01	13:54:41:054	 544	1128	Misc	 Microsoft signed: Yes
2007-09-01	13:54:41:079	 544	1128	Setup	Determining whether a new setup
handler needs to be downloaded
2007-09-01	13:54:41:080	 544	1128	Setup	SelfUpdate handler update required:
Current version: 7.0.6000.381, required version: 7.0.6000.374
2007-09-01	13:54:41:080	 544	1128	Setup	Evaluating applicability of setup
package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.0.6000.374"
2007-09-01	13:54:41:278	 544	1128	Setup	Setup package
applicable
2007-09-01	13:54:41:278	 544	1128	Setup	Evaluating applicability of setup
package
2007-09-01	13:54:41:433	 544	1128	Setup	Setup package
not applicable
2007-09-01	13:54:41:434	 544	1128	Setup	Evaluating applicability of setup
package
2007-09-01	13:54:41:647	 544	1128	Setup	Setup package
not applicable
2007-09-01	13:54:41:648	 544	1128	Setup	SelfUpdate check completed.
SelfUpdate is NOT required.
2007-09-01	13:54:43:865	 544	1128	PT	+++++++++++  PT: Synchronizing server
updates  +++++++++++
2007-09-01	13:54:43:865	 544	1128	PT	  + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://w2k3dc2/ClientWebService/client.asmx
2007-09-01	13:54:44:017	 544	1128	PT	WARNING: Cached cookie has expired or
new PID is available
2007-09-01	13:54:44:018	 544	1128	PT	Initializing simple targeting cookie,
clientId = 66bf811d-a50b-4ad0-8e35-9a1829e9a623, target group = , DNS name =
parents1.yefimov.org
2007-09-01	13:54:44:018	 544	1128	PT	  Server URL =
http://w2k3dc2/SimpleAuthWebService/SimpleAuth.asmx
2007-09-01	13:54:44:021	 544	1128	PT	WARNING: GetAuthorizationCookie
failure, error = 0x80244019, soap client error = 10, soap error code = 0,
HTTP status code = 404
2007-09-01	13:54:44:022	 544	1128	PT	WARNING: Failed to initialize Simple
Targeting Cookie: 0x80244019
2007-09-01	13:54:44:022	 544	1128	PT	WARNING: PopulateAuthCookies failed:
0x80244019
2007-09-01	13:54:44:022	 544	1128	PT	WARNING: RefreshCookie failed: 0x80244019
2007-09-01	13:54:44:022	 544	1128	PT	WARNING: RefreshPTState failed:
0x80244019
2007-09-01	13:54:44:022	 544	1128	PT	WARNING: Sync of Updates: 0x80244019
2007-09-01	13:54:44:022	 544	1128	PT	WARNING: SyncServerUpdatesInternal
failed: 0x80244019
2007-09-01	13:54:44:022	 544	1128	Agent	  * WARNING: Failed to synchronize,
error = 0x80244019
2007-09-01	13:54:44:049	 544	1128	Agent	  * WARNING: Exit code = 0x80244019
2007-09-01	13:54:44:049	 544	1128	Agent	*********
2007-09-01	13:54:44:049	 544	1128	Agent	**  END  **  Agent: Finding updates
[CallerId = AutomaticUpdates]
2007-09-01	13:54:44:049	 544	1128	Agent	*************
2007-09-01	13:54:44:049	 544	1128	Agent	WARNING: WU client failed Searching
for update with error 0x80244019
2007-09-01	13:54:44:050	 544	6d4	AU	>>##  RESUMED  ## AU: Search for updates
[CallId = {6770E6AC-AAE2-410E-9C3B-4C6C2E566F9C}]
2007-09-01	13:54:44:051	 544	6d4	AU	  # WARNING: Search callback failed,
result = 0x80244019
2007-09-01	13:54:44:051	 544	6d4	AU	  # WARNING: Failed to find updates with
error code 80244019
2007-09-01	13:54:44:051	 544	6d4	AU	#########
2007-09-01	13:54:44:051	 544	6d4	AU	##  END  ##  AU: Search for updates
[CallId = {6770E6AC-AAE2-410E-9C3B-4C6C2E566F9C}]
2007-09-01	13:54:44:051	 544	6d4	AU	#############
2007-09-01	13:54:44:052	 544	6d4	AU	AU setting next detection timeout to
2007-09-01 06:54:44
2007-09-01	13:54:44:053	 544	6d4	AU	Setting AU scheduled install time to
2007-09-01 21:00:00
2007-09-01	13:54:49:048	 544	1128	Report	REPORT EVENT:
{E2C6B499-1F4C-409F-B159-FA810964EC97}	2007-09-01
13:54:44:048+1200	1	148	101	{00000000-0000-0000-0000-000000000000}	0	80244019	AutomaticUpdates	Failure	Software
Synchronization	Windows Update Client failed to detect with error 0x80244019.




Anatol replied on 01-Sep-07 01:50 AM
To answer my own question, this turned out to be the fact that I didn't do a
default installation, but allowed the installation to create it's on web
site.. All I needed to do was to point the GPO to the port it was running
on... in this case, port 8530.