Results 1 to 6 of 6

Thread: Some WSUS-Clients report 0x8024400E

  1. #1
    Join Date
    Aug 2006
    Posts
    173

    Some WSUS-Clients report 0x8024400E

    I have got 4 Windows 2000 Server and out of those 2 are reporting error 0x8024400E in the UpdateService.log. When checked in WSUS admin then it says that these computers dont report yet for serveral days. Even after reinstalling the automatic update service, there was no success because the issue is still there. The different computers and servers in the domain work properly. Does anyone know how to solve this? Thanks

  2. #2
    Join Date
    Jan 2006
    Posts
    605

    Re: Some WSUS-Clients report 0x8024400E

    This error is faced by many people and therefore you can try to do the below on the problematic Windows 2000 server and post the results back on your next reply:
    1. First of all stop the Automaitc Updates service.
    2. After that you need to rename the %windir%\SoftwareUpdate folder to something like SoftwareNonUpdate.
    3. After that try to rename the %windir%\WindowsUpdate.log file to something like WindowsNonUpdate.log as well.
    4. Now you have to restart the Automatic Updates service and wait 10 minutes.
    5. After that try to open a command prompt and issue 'wuauclt /detectnow' without the quotes and wait 20 minutes.
    6. Lastly, you will need to post the entire contents of the %windir%\WindowsUpdate.log to this thread.

  3. #3
    Join Date
    Aug 2006
    Posts
    173

    Re: Some WSUS-Clients report 0x8024400E

    Thanks for the reply, I did what you asked but still am getting the error. Check out the below log-file that you have asked me:

    2006-03-16 23:48:51 2272 870 Misc =========== Logging initialized (build:
    5.8.0.2469, tz: +0100) ===========
    2006-03-16 23:48:51 2272 870 Misc = Process: C:\WINNT\system32\svchost.exe
    2006-03-16 23:48:51 2272 870 Misc = Module: C:\WINNT\system32\wuaueng.dll
    2006-03-16 23:48:51 2272 870 Service *************
    2006-03-16 23:48:51 2272 870 Service ** START ** Service: Service startup
    2006-03-16 23:48:51 2272 870 Service *********
    2006-03-16 23:48:51 2272 870 Agent * WU client version 5.8.0.2469
    2006-03-16 23:48:51 2272 870 Agent * SusClientId =
    '4ab271c6-f419-48dd-9ca7-837c4329d6b3'
    2006-03-16 23:48:51 2272 870 Agent * Base directory:
    C:\WINNT\SoftwareDistribution
    2006-03-16 23:48:51 2272 870 Agent * Access type: No proxy
    2006-03-16 23:48:51 2272 870 Agent * Network state: Connected
    2006-03-16 23:49:20 2272 358 Agent *********** Agent: Initializing Windows
    Update Agent ***********
    2006-03-16 23:49:20 2272 358 Agent *********** Agent: Initializing global
    settings cache ***********
    2006-03-16 23:49:20 2272 358 Agent * WSUS server: http://ts1.domsg.local
    2006-03-16 23:49:20 2272 358 Agent * WSUS status server:
    http://ts1.domsg.local
    2006-03-16 23:49:20 2272 358 Agent * Target group: Memberserver
    2006-03-16 23:49:20 2272 358 Agent * Windows Update access disabled: No
    2006-03-16 23:49:23 2272 358 DtaStor Default service for AU is
    {00000000-0000-0000-0000-000000000000}
    2006-03-16 23:49:23 2272 358 DtaStor Default service for AU is
    {9482F4B4-E343-43B6-B170-9A65BC822C77}
    2006-03-16 23:49:23 2272 358 DnldMgr Download manager restoring 0 downloads
    2006-03-16 23:49:23 2272 358 AU ########### AU: Initializing Automatic
    Updates ###########
    2006-03-16 23:49:23 2272 358 AU # WSUS server: http://ts1.domsg.local
    2006-03-16 23:49:23 2272 358 AU # Detection frequency: 22
    2006-03-16 23:49:23 2272 358 AU # Target group: Memberserver
    2006-03-16 23:49:23 2272 358 AU # Approval type: Scheduled (Policy)
    2006-03-16 23:49:23 2272 358 AU # Scheduled install day/time: Sunday at
    5:00
    2006-03-16 23:49:23 2272 358 AU # Auto-install minor updates: Yes (Policy)
    2006-03-16 23:49:23 2272 358 AU Triggering AU detection through DetectNow
    API
    2006-03-16 23:49:23 2272 870 AU #############
    2006-03-16 23:49:23 2272 870 AU ## START ## AU: Search for updates
    2006-03-16 23:49:23 2272 870 AU #########
    2006-03-16 23:49:23 2272 870 AU <<## SUBMITTED ## AU: Search for updates
    [CallId = {7DFAA841-FDB4-4FDC-AF51-0778E3CA9CEE}]
    2006-03-16 23:49:23 2272 874 Agent *************
    2006-03-16 23:49:23 2272 874 Agent ** START ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2006-03-16 23:49:23 2272 874 Agent *********
    2006-03-16 23:49:23 2272 874 Setup *********** Setup: Checking whether
    self-update is required ***********
    2006-03-16 23:49:23 2272 874 Setup * Inf file:
    C:\WINNT\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
    2006-03-16 23:49:23 2272 874 Setup Update NOT required for
    C:\WINNT\system32\cdm.dll: target version = 5.8.0.2469, required version =
    5.8.0.2469

  4. #4
    Join Date
    Oct 2005
    Posts
    2,358

    Re: Some WSUS-Clients report 0x8024400E

    It seems to be a server-side issue so even if you try to repair the client then it wont do anything useful. Unfortuanately, there is no fix for this issue because its caused by a server side database corruption problem and also cause by a malfunction in an XML import proc. You may need to reinstall the WSUS with the database and logs.

  5. #5
    Join Date
    Jul 2008
    Posts
    1

    Fix

    I had a similar problem with most XP clients reporting this error and not giving status reports. I eventually traced it to a problem with the AU client trying to go through our proxy server. Even though our proxy settings are set to bypass local addresses. I had to do the following to cure:

    1. In group policy use FQDN for WSUS intranet server name i.e. http://WSUSserver.mydomain.com instead of http://WSUSserver

    2. Ensure browser proxy settings includes *.mydomain.com in the "do not use proxy for addresses begining with" box. I used group policy to set the proxy settings globally.

  6. #6
    Join Date
    Jan 2006
    Posts
    4,221

    RE: Some WSUS-Clients report 0x8024400E

    You use Microsoft Windows Server Update Services (WSUS) 3.0 to deploy software updates and hotfixes to computers that are in your organization. However, some computers do not receive updates from the WSUS server. This problem occurs if the computers have Microsoft Office 2003 or components of Office 2003 installed. For more information visit this website - http://support.microsoft.com/kb/954960

Similar Threads

  1. WSUS 3.0 Clients are not showing in wsus admin console
    By Rock41 in forum Windows Update
    Replies: 7
    Last Post: 25-09-2009, 12:28 AM
  2. wsus clients not contact wsus server error = 0x80244023 and 0x8019
    By Dilbert in forum Server Update Service
    Replies: 3
    Last Post: 06-03-2009, 11:47 PM
  3. Replies: 3
    Last Post: 07-01-2009, 10:45 AM
  4. clients not reporting status after updating WSUS 2 to WSUS 3.0
    By Dhananjay in forum Server Update Service
    Replies: 4
    Last Post: 17-07-2007, 09:37 PM
  5. WSUS 3.0 - Clients not responding, error = 0x8024400E
    By Debbie Rowe in forum Server Update Service
    Replies: 1
    Last Post: 25-05-2007, 03:39 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,871,942.78951 seconds with 18 queries