Error 0x8024400e, while clients report back to WSUS
Martin Johansen
I have a Windows 2003 SP1 server running WSUS.
On the 24.8.2005 some of the clients stopped reporting back to our WSUS
server. Others a few keeps reporting back.
From the Clients Windowsupdate.log file I can find this:
2005-09-14 19:26:11 1540 1314 AU Triggering AU detection through DetectNow API
2005-09-14 19:26:11 1540 610 AU #############
2005-09-14 19:26:11 1540 610 AU ## START ## AU: Search for updates
2005-09-14 19:26:11 1540 610 AU #########
2005-09-14 19:26:11 1540 610 AU <<## SUBMITTED ## AU: Search for updates
[CallId = {A987B752-CE4E-4B6F-9D1F-716A681EA4BF}]
2005-09-14 19:26:11 1540 1534 Agent *************
2005-09-14 19:26:11 1540 1534 Agent ** START ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-09-14 19:26:11 1540 1534 Agent *********
2005-09-14 19:26:22 1540 1534 Setup *********** Setup: Checking whether
self-update is required ***********
2005-09-14 19:26:22 1540 1534 Setup * Inf file:
C:\WINNT\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2005-09-14 19:26:22 1540 1534 Setup Update NOT required for
C:\WINNT\system32\cdm.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-09-14 19:26:22 1540 1534 Setup Update NOT required for
C:\WINNT\system32\iuengine.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-09-14 19:26:22 1540 1534 Setup Update NOT required for
C:\WINNT\system32\wuapi.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-09-14 19:26:22 1540 1534 Setup Update NOT required for
C:\WINNT\system32\wuauclt.exe: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-09-14 19:26:22 1540 1534 Setup Update NOT required for
C:\WINNT\system32\wuauclt1.exe: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-09-14 19:26:22 1540 1534 Setup Update NOT required for
C:\WINNT\system32\wuaucpl.cpl: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-09-14 19:26:22 1540 1534 Setup Update NOT required for
C:\WINNT\system32\wuaueng.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-09-14 19:26:22 1540 1534 Setup Update NOT required for
C:\WINNT\system32\wuaueng1.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-09-14 19:26:22 1540 1534 Setup Update NOT required for
C:\WINNT\system32\wucltui.dll: target version = 5.8.0.2469, required version
= 5.8.0.2469
2005-09-14 19:26:22 1540 1534 Setup Update NOT required for
C:\WINNT\system32\wups.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-09-14 19:26:22 1540 1534 Setup Update NOT required for
C:\WINNT\system32\wups2.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-09-14 19:26:22 1540 1534 Setup Update NOT required for
C:\WINNT\system32\wuweb.dll: target version = 5.8.0.2469, required version =
5.8.0.2469
2005-09-14 19:26:22 1540 1534 Setup * IsUpdateRequired = No
2005-09-14 19:26:25 1540 1534 PT +++++++++++ PT: Synchronizing server
updates +++++++++++
2005-09-14 19:26:25 1540 1534 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
HTTP://SRVBW08/ClientWebService/client.asmx
2005-09-14 19:26:25 1540 1534 PT Initializing simple targeting cookie,
clientId = 1b33c91d-8358-43a8-98fd-18829fd950da, target group = Servers, DNS
name = srvbw03.bwdm.com
2005-09-14 19:26:25 1540 1534 PT Server URL =
HTTP://SRVBW08/SimpleAuthWebService/SimpleAuth.asmx
2005-09-14 19:26:42 1540 1534 PT WARNING: SyncUpdates failure, error =
0x8024400E, soap client error = 7, soap error code = 400, HTTP status code =
200
2005-09-14 19:26:42 1540 1534 PT WARNING: SOAP Fault: 0x000190
2005-09-14 19:26:42 1540 1534 PT WARNING: faultstring:Fault occurred
2005-09-14 19:26:42 1540 1534 PT WARNING: ErrorCode:InternalServerError(5)
2005-09-14 19:26:42 1540 1534 PT WARNING: Message:
2005-09-14 19:26:42 1540 1534 PT WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2005-09-14 19:26:42 1540 1534 PT WARNING:
ID:2e96a45a-acc4-4aa7-b74a-8c31fa39e857
2005-09-14 19:26:42 1540 1534 PT WARNING: Sync of Updates: 0x8024400e
2005-09-14 19:26:42 1540 1534 Agent * WARNING: Failed to synchronize,
error = 0x8024400E
2005-09-14 19:26:42 1540 1534 Agent * WARNING: Exit code = 0x8024400E
2005-09-14 19:26:42 1540 1534 Agent *********
2005-09-14 19:26:42 1540 1534 Agent ** END ** Agent: Finding updates
[CallerId = AutomaticUpdates]
2005-09-14 19:26:42 1540 1534 Agent *************
2005-09-14 19:26:42 1540 1534 Agent WARNING: WU client failed Searching for
update with error 0x8024400e
2005-09-14 19:26:42 1540 1534 AU >>## RESUMED ## AU: Search for updates
[CallId = {A987B752-CE4E-4B6F-9D1F-716A681EA4BF}]
2005-09-14 19:26:42 1540 1534 AU # WARNING: Search callback failed, result
= 0x8024400E
2005-09-14 19:26:42 1540 1534 AU #########
2005-09-14 19:26:42 1540 1534 AU ## END ## AU: Search for updates [CallId
= {A987B752-CE4E-4B6F-9D1F-716A681EA4BF}]
2005-09-14 19:26:42 1540 1534 AU #############
2005-09-14 19:26:42 1540 1534 AU AU setting next detection timeout to
2005-09-14 22:26:42
2005-09-14 19:26:47 1540 1534 Report REPORT EVENT:
{70AAD4F1-F690-4204-AE7C-8BBFB5BACFFA} 2005-09-14
19:26:42+0200 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400e AutomaticUpdates Failure Software
Synchronization Error: Agent failed detecting with reason: 0x8024400e
2005-09-14 19:36:16 1540 1534 PT Initializing simple targeting cookie,
clientId = 1b33c91d-8358-43a8-98fd-18829fd950da, target group = Servers, DNS
name = srvbw03.bwdm.com
2005-09-14 19:36:16 1540 1534 PT Server URL =
HTTP://SRVBW08/SimpleAuthWebService/SimpleAuth.asmx
2005-09-14 19:36:16 1540 1534 Report Uploading 1 events using cached cookie,
reporting URL = HTTP://SRVBW08/ReportingWebService/ReportingWebService.asmx
2005-09-14 19:36:18 1540 1534 Report Reporter successfully uploaded 1 events.
In this file I find this error: SyncUpdates failure, error = 0x8024400E,
soap client error = 7, soap error code = 400, HTTP status code = 200.
Do anyone know how to fix this problem?
The Clients are primary Windows XP SP2.
Regards, Martin
Lawrence Garvin
The message was OK but server couldn't process at the moment
This is an indication of a server-side issue, either performance related, or
perhaps APS.NET or the database is timing out trying to serve the requests.
What do you find in the IIS Logs and Event Logs on the server?
"Martin Johansen" <MartinJ...@discussions.microsoft.com> wrote in
message news:0CEEC92D-094D-4590...@microsoft.com...
Martin Johansen
to be logged. Both the System and Application log shows only
"information"-status.
The IIS log from that time shows this:
2005-09-14 20:14:25 192.168.2.10 HEAD /selfupdate/wuident.cab 0509142014 80
- 192.168.2.73 Windows-Update-Agent 200 0 0
2005-09-14 20:14:25 192.168.2.10 HEAD /selfupdate/AU/x86/XP/da/wusetup.cab
0509142014 80 - 192.168.2.73 Windows-Update-Agent 200 0 0
2005-09-14 20:14:25 192.168.2.10 GET /selfupdate/AU/x86/XP/da/wusetup.cab
0509142014 80 - 192.168.2.73 Windows-Update-Agent 200 0 0
2005-09-14 20:14:41 192.168.2.10 POST /SimpleAuthWebService/SimpleAuth.asmx
- 80 - 192.168.2.73 Windows-Update-Agent 200 0 0
2005-09-14 20:14:48 192.168.2.10 POST /ClientWebService/client.asmx - 80 -
192.168.2.73 Windows-Update-Agent 200 0 0
2005-09-14 20:14:53 192.168.2.10 POST /ClientWebService/client.asmx - 80 -
192.168.2.73 Windows-Update-Agent 500 0 0
2005-09-14 20:22:14 192.168.2.10 HEAD /selfupdate/wuident.cab 0509142021 80
- 192.168.2.75 Windows-Update-Agent 200 0 0
2005-09-14 20:22:14 192.168.2.10 HEAD /selfupdate/AU/x86/XP/da/wusetup.cab
0509142022 80 - 192.168.2.75 Windows-Update-Agent 200 0 0
2005-09-14 20:22:14 192.168.2.10 GET /selfupdate/AU/x86/XP/da/wusetup.cab
0509142022 80 - 192.168.2.75 Windows-Update-Agent 200 0 0
2005-09-14 20:22:19 192.168.2.10 POST /SimpleAuthWebService/SimpleAuth.asmx
- 80 - 192.168.2.75 Windows-Update-Agent 200 0 0
2005-09-14 20:22:19 192.168.2.10 POST /ClientWebService/client.asmx - 80 -
192.168.2.75 Windows-Update-Agent 200 0 0
2005-09-14 20:22:22 192.168.2.10 POST /ClientWebService/client.asmx - 80 -
192.168.2.75 Windows-Update-Agent 500 0 0
2005-09-14 20:24:16 192.168.2.10 POST /SimpleAuthWebService/SimpleAuth.asmx
- 80 - 192.168.2.73 Windows-Update-Agent 200 0 0
2005-09-14 20:24:16 192.168.2.10 POST /ClientWebService/client.asmx - 80 -
192.168.2.73 Windows-Update-Agent 200 0 0
2005-09-14 20:24:20 192.168.2.10 POST
/ReportingWebService/ReportingWebService.asmx - 80 - 192.168.2.73
Windows-Update-Agent 200 0 0
2005-09-14 20:30:13 192.168.2.10 POST /SimpleAuthWebService/SimpleAuth.asmx
- 80 - 192.168.2.75 Windows-Update-Agent 200 0 0
2005-09-14 20:30:13 192.168.2.10 POST /ClientWebService/client.asmx - 80 -
192.168.2.75 Windows-Update-Agent 200 0 0
2005-09-14 20:30:13 192.168.2.10 POST
/ReportingWebService/ReportingWebService.asmx - 80 - 192.168.2.75
Windows-Update-Agent 200 0 0
There is a few lines refereing to error 500(HTTP server error), but does not
tell me anything else. Any ideas?
Regards, Martin
Martin Johansen
So I uninstalled the WSUS, removed all, and reinstalled it again.
Clients are signing in now.
Thank you for your time.
Regards, Martin
Bill K
I have spent time with a DBA in our company working on the WSUS DB (susdb)
and the
DBA can find nothing wrong with the database. She believes that the problem
is related
to the WSUS application and not with the DB. I also ran the CHECKDB against
the susdb
and it comes back clean. Here is that excerpt from the EV.
DBCC CHECKDB (SUSDB) executed by xxx\yyy found 0 errors and repaired 0
errors. Elapsed time: 0 hours 0 minutes 9 seconds.
Apparently something is wrong with the SQL Web Assistant or how WSUS uses
this feature.
If you have any other ideas that would be great. Otherwise my next step is
to leave the SQL
install alone and remove and re-install WSUS. If that works then that would
indicate the SQL
database was not the issue and would point to a problem with WSUS. I have
seen others in this
newsgroup report the exact same entries in the windowsupdate.log file on
their clients. It appears
that in those cases they just reinstalled WSUS and that Microsoft was not
really able to help them.
BTW - This is not a production server but a test server that after
additional testing would be moved
into production. It has 70 client machines, is running W2K3/SP1 server, with
a 2.8 GHz processor,
and 1 GB of RAM. I don't think that one client connecting in should result
in a timeout.
Any help that you can provide will be greatly appreciated, and I do thank
you for the quick response.
Bill K.
"Martin Johansen" <MartinJ...@discussions.microsoft.com> wrote in
message news:873174BF-2B39-41D9...@microsoft.com...
Bill K
"Bill K" <bill....@ugs.com> wrote in message
news:u%23RhI0hu...@TK2MSFTNGP09.phx.gbl...