GetAuthorizationCookie failure, error = 0x8024400E, soap client er
eFeCe
WSUS reinstallation went OK no errors.
Client computers receive this message, recorded on "WindowsUpdate.log".
This is the complete message (PRIORIZ is my WSUS server):
2007-04-23 08:43:13 1852 3e0 PT Initializing simple targeting cookie,
clientId = 26535d42-a4b3-4eed-9bb8-3ccf799fd712, target group = , DNS name =
yyy.xxxx.com
2007-04-23 08:43:13 1852 3e0 PT Server URL =
http://PRIORIZ/SimpleAuthWebService/SimpleAuth.asmx
2007-04-23 08:43:14 1852 3e0 PT WARNING: GetAuthorizationCookie failure,
error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status
code = 200
2007-04-23 08:43:14 1852 3e0 PT WARNING: SOAP Fault: 0x000190
2007-04-23 08:43:14 1852 3e0 PT WARNING: faultstring:Fault occurred
2007-04-23 08:43:14 1852 3e0 PT WARNING: ErrorCode:InternalServerError(5)
2007-04-23 08:43:14 1852 3e0 PT WARNING: Message:
2007-04-23 08:43:14 1852 3e0 PT WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/Server/SimpleAuthWebService/GetAuthorizationCookie"
2007-04-23 08:43:14 1852 3e0 PT WARNING:
ID:b20fe2af-96e4-4fac-ae68-52da0d19803e
2007-04-23 08:43:14 1852 3e0 Report WARNING: Reporter failed to upload
events with hr = 8024400e.
Lawrence Garvin (MVP)
news:7A1D2563-3CA5-42D2...@microsoft.com...
> Searching this error elsewhere gives me no clue.
> WSUS reinstallation went OK no errors.
> Client computers receive this message, recorded on "WindowsUpdate.log".
> This is the complete message (PRIORIZ is my WSUS server):
> 2007-04-23 08:43:13 1852 3e0 PT Server URL =
> http://PRIORIZ/SimpleAuthWebService/SimpleAuth.asmx
> 2007-04-23 08:43:14 1852 3e0 PT WARNING: GetAuthorizationCookie failure,
> error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP
> status
> code = 200
The 0x8024400E error has typically been associated with a known XML
corruption problem in the WSUS RTM version. The only 'fix' was to
uninstall/reinstall WSUS. The 'bug' was fixed in WSUS SP1; unfortunately,
applying SP1 will not fix any pre-existing XML corruption caused prior to
the SP install. So, either way, the only 'fix' is to uninstall WSUS and
reinstall WSUS SP1.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
....
eFeCe
Thanks for your help. I unistalled and the remove/delete all, I think,
everything (I didn't check the registry nor A/Directory), even the content!!
(a few gigs).
Reinstalled the last version (WSUS2-KB919004-x86.exe), and on the client I
still receive the same "0x8024400E".
I do not want to giveup...
Lawrence Garvin (MVP)
[a] Reboot the client.
[b] Run 'wuauclt /resetauthorization /detectnow' to flush out the old
cookie.
eFeCe
I changed the WSUS server to another available box, client show the same
problem, however, after applying your advice: wuauclt /resetauthorization
/detectnow , now is working as intended.
Is there any method to do this automatically to all my clients? group policy?
Thanks,
Lawrence Garvin (MVP)
The cookie is supposed to have a 60 minute timeout, but I don't have all of
the specifics on this, and I've seen scenarios where the cookie does appear
to timeout like it should have.
My best suggestion is to put 'wuauclt /resetauthorization /detectnow/ in a
logon script for a couple of days. There will be a small extra load on the
clients and servers for executing this extra detection, but it'll be a lot
less significant than if you have to walk around to clients.
You could also use the psexec utility of SysInternals to remotely execute
the command.
eFeCe
Thanks for your help.
intended and my blood pressure is stable again.