Sign in
Microsoft.com
 
System Center Essentials TechCenter
 
 
 
System Center Essentials TechCenter > System Center Essentials Forums > System Center Essentials - Updates > WSUS Client Sync
Ask a questionAsk a question
Search Forums:
 

AnswerWSUS Client Sync

  • Wednesday, October 07, 2009 10:36 PMsrb23dj Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I'm currently working on a WSUS issue where the client is Windows Server 2003 SP2. The WSUS SP2 is installed on a Windows Server 2008 SP1 machine.
    When I run wuauclt.exe /detectnow command on the client I receive the below error in windowsupdate.log:

    2009-10-02 14:38:13:318  840 18ec Perf, CClientWebService::SyncUpdates, time, 61427
    2009-10-02 14:38:13:318  840 18ec PT WARNING: SyncUpdates failure, error = 0x8024400A, soap client error = 10, soap error code = 0, HTTP status code = 200
    2009-10-02 14:38:13:318  840 18ec PT PT: Cannot recover from fault, origin=SyncUpdates, hr=0x8024400a
    2009-10-02 14:38:13:318  840 18ec PT WARNING: PTError: 0x8024400a
    2009-10-02 14:38:13:318  840 18ec PT WARNING: SyncUpdates_WithRecovery failed.: 0x8024400a
    2009-10-02 14:38:13:318  840 18ec PT WARNING: Sync of Updates: 0x8024400a
    2009-10-02 14:38:13:318  840 18ec PT WARNING: SyncServerUpdatesInternal failed: 0x8024400a
    2009-10-02 14:38:13:318  840 18ec Perf, SyncServerUpdates, time, 68578
    2009-10-02 14:38:13:318  840 18ec Agent   * WARNING: Failed to synchronize, error = 0x8024400A
    2009-10-02 14:38:13:318  840 18ec Perf, PrepareSearchCallbackInfo, time, 0
    2009-10-02 14:38:13:318  840 18ec Report *****Dumping event {C9BC9197-E1F8-495F-AB11-8D69E2EA7E1D}:
    2009-10-02 14:38:13:318  840 18ec Report  EventId 148, Source Id 101, Caller AutomaticUpdates:
    2009-10-02 14:38:13:318  840 18ec Report  Targetserver {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}:
    2009-10-02 14:38:13:318  840 18ec Report  Replacement strings: 1
    2009-10-02 14:38:13:318  840 18ec Report  Misc data strings: 14
    2009-10-02 14:38:13:318  840 18ec Report   D=0
    2009-10-02 14:38:13:318  840 18ec Report   O=69
    2009-10-02 14:38:13:318  840 18ec Report   B=138
    2009-10-02 14:38:13:318  840 18ec Report   k=1
    2009-10-02 14:38:13:318  840 18ec Report   C=1
    2009-10-02 14:38:13:318  840 18ec Report   f=413
    2009-10-02 14:38:13:318  840 18ec Report   Q=1
    2009-10-02 14:38:13:318  840 18ec Report   m=3
    2009-10-02 14:38:13:318  840 18ec Report   n=0
    2009-10-02 14:38:13:318  840 18ec Report   G=7.4.7600.226
    2009-10-02 14:38:13:318  840 18ec Report   A=4478
    2009-10-02 14:38:13:318  840 18ec Report   J=550
    2009-10-02 14:38:13:318  840 18ec Report   K=Phoenix ROM BIOS PLUS Version 1.10 1.5.1
    2009-10-02 14:38:13:318  840 18ec Report   L=2007-08-10T00:00:00
    2009-10-02 14:38:13:318  840 18ec Agent   * WARNING: Exit code = 0x8024400A
    2009-10-02 14:38:13:318  840 18ec Agent *********
    2009-10-02 14:38:13:318  840 18ec Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-10-02 14:38:13:318  840 18ec Agent *************
    2009-10-02 14:38:13:318  840 18ec Agent WARNING: WU client failed Searching for update with error 0x8024400a
    2009-10-02 14:38:13:318  840 18ec Perf, CSearchCall::Execute, time, 69621
    2009-10-02 14:38:13:318  840 1560 AU >>##  RESUMED  ## AU: Search for updates [CallId = {9BC9AED0-69E5-4C39-A59B-983244259737}]
    2009-10-02 14:38:13:318  840 1560 AU   # WARNING: Search callback failed, result = 0x8024400A
    2009-10-02 14:38:13:318  840 1560 AU   # WARNING: Failed to find updates with error code 8024400A
    2009-10-02 14:38:13:318  840 1560 AU #########
    2009-10-02 14:38:13:318  840 1560 AU ##  END  ##  AU: Search for updates [CallId = {9BC9AED0-69E5-4C39-A59B-983244259737}]

    I know that there is a hotfix(KB 923507/ KB 898708) for this kind of issue however these are applicable for Windows Server 2003 RTM/SP1 machines.
    The client I'm working on is a Windows Server 2003 SP2 client. In the KB its mentioned that the issue is resolved in Windows Server 2003 SP2 machines.

    On the client I've tried all basic troubleshooting like
    >stopping AU service and removing the Software Distribution Folder and restarting AU service
    >Recreated new SUS client ID and ran wuauclt /resetauthorization /detectnow.

    Still did not work for me.
    Is there any hotfix to resolve this issue in Windows 2003 SP2 ? Any ideas ?
     

Answers

All Replies