|
|
i have one server in a domain, it's not a dc, that won't sync. status shows not yet reported. tried deleting software distribution folder, installing wsus 3 client, no luck. here are some of the last windowsupdate log messages.
2007-05-25 18:35:13:341 1704 3dc Setup * IsUpdateRequired = No 2007-05-25 18:35:15:372 1704 3dc PT +++++++++++ PT: Synchronizing server updates +++++++++++ 2007-05-25 18:35:15:372 1704 3dc PT + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://reccu1/ClientWebService/client.asmx 2007-05-25 18:35:15:497 1704 3dc PT WARNING: Cached cookie has expired or new PID is available 2007-05-25 18:35:15:497 1704 3dc PT Initializing simple targeting cookie, clientId = 3ae4eb97-19bf-4fd0-be40-abc37b0d82ae, target group = , DNS name = mail1.mi01.com 2007-05-25 18:35:15:497 1704 3dc PT Server URL = http://reccu1/SimpleAuthWebService/SimpleAuth.asmx 2007-05-25 18:35:15:497 1704 3dc PT WARNING: SyncUpdates failure, error = 0x8024400A, soap client error = 10, soap error code = 0, HTTP status code = 200 2007-05-25 18:35:15:497 1704 3dc PT WARNING: PTError: 0x8024400a 2007-05-25 18:35:15:497 1704 3dc PT WARNING: SyncUpdates_WithRecovery failed.: 0x8024400a 2007-05-25 18:35:15:497 1704 3dc PT WARNING: Sync of Updates: 0x8024400a 2007-05-25 18:35:15:497 1704 3dc PT WARNING: SyncServerUpdatesInternal failed: 0x8024400a 2007-05-25 18:35:15:497 1704 3dc Agent * WARNING: Failed to synchronize, error = 0x8024400A 2007-05-25 18:35:15:513 1704 3dc Agent * WARNING: Exit code = 0x8024400A 2007-05-25 18:35:15:513 1704 3dc Agent ********* 2007-05-25 18:35:15:513 1704 3dc Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] 2007-05-25 18:35:15:513 1704 3dc Agent ************* 2007-05-25 18:35:15:513 1704 3dc Agent WARNING: WU client failed Searching for update with error 0x8024400a 2007-05-25 18:35:15:513 1704 95c AU >>## RESUMED ## AU: Search for updates [CallId = {45C12F40-BC22-4949-AC6C-6D410BBCEF8C}] 2007-05-25 18:35:15:513 1704 95c AU # WARNING: Search callback failed, result = 0x8024400A 2007-05-25 18:35:15:513 1704 95c AU # WARNING: Failed to find updates with error code 8024400A 2007-05-25 18:35:15:513 1704 95c AU ######### 2007-05-25 18:35:15:513 1704 95c AU ## END ## AU: Search for updates [CallId = {45C12F40-BC22-4949-AC6C-6D410BBCEF8C}] 2007-05-25 18:35:15:513 1704 95c AU ############# 2007-05-25 18:35:15:513 1704 95c AU AU setting next detection timeout to 2007-05-26 03:35:15 2007-05-25 18:35:15:513 1704 95c AU Setting AU scheduled install time to 2007-05-26 19:00:00 2007-05-25 18:35:20:513 1704 3dc Report REPORT EVENT: {361F2D12-5004-47A5-9C7F-E2B35396A5F2} 2007-05-25 18:35:15:513-0400 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400a AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x8024400a.
--
Gary
|
|
"Gary Keramidas" <GKeramidasATmsn.com> wrote in message news:OzXvE2xnHHA.3548[ at ]TK2MSFTNGP06.phx.gbl...
[Quoted Text] > > i have one server in a domain, it's not a dc, that won't sync. status > shows not yet reported. tried deleting software distribution folder, > installing wsus 3 client, no luck.
What version is the WSUS Server?
> 2007-05-25 18:35:15:497 1704 3dc PT WARNING: SyncUpdates failure, error = > 0x8024400A, soap client error = 10, soap error code = 0, HTTP status code > = 200 > 2007-05-25 18:35:15:497 1704 3dc PT WARNING: PTError: 0x8024400a > 2007-05-25 18:35:15:497 1704 3dc PT WARNING: SyncUpdates_WithRecovery > failed.: 0x8024400a > 2007-05-25 18:35:15:497 1704 3dc PT WARNING: Sync of Updates: 0x8024400a > 2007-05-25 18:35:15:497 1704 3dc PT WARNING: SyncServerUpdatesInternal > failed: 0x8024400a > 2007-05-25 18:35:15:497 1704 3dc Agent * WARNING: Failed to synchronize, > error = 0x8024400A > 2007-05-25 18:35:15:513 1704 3dc Agent * WARNING: Exit code = 0x8024400A
If WSUS3, this may be related to an SSL issue documented in the WSUS3 Readme:
If WSUS 3.0 is deployed using SSL, client computers may fail with a 0x8024400a error code Client computers can sometimes fail with a "0x8024400a" error code when communicating with a WSUS 3.0 server using SSL. For an update that addresses this issue, see KB 905422 (http://go.microsoft.com/fwlink/?LinkId=70593).
If WSUS2 on Win2003, this error is typically associated with a known, but sporadically occuring, conflict between IIS and HTTP.SYS on Windows Server 2003 systems.
The hotfix is documented at http://support.microsoft.com/?id=898708
-- 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 .....
|
|
|