Error number: 0x8DDD0004

Discussion in 'Windows Update' started by Daniel Cottam, Sep 6, 2004.

  1. I too am getting this error message but my symptoms seem to be slightly
    different to other people.. I have been through all the previous posts and
    none of them have helped me to resolve my problem.

    When I go to windows update either by using the link on the start menu, the
    link in internet explorer or by typing the address
    (http://v5.windowsupdate.microsoft.com/v5consumer/default.aspx?ln=en-us)
    myself I am presented with the "Checking for the latest version of Windows
    Update software" screen and then after a couple of minutes get a "We're
    sorry" page with "Error number: 0x8DDD0004" as my only clue as to what may be
    wrong.

    Thinking that it might have been a problem that would be fixed in SP2 I then
    installed SP2 manually (as I couldn't get to it via Windows Update). Still no
    luck.

    I am not getting any yellow bar along the top of the page (and I do now what
    to look for as I have got the yellow bar on pages when I needed to install
    other components such as macromedia) but it does not appear to be succesfully
    loading and installing the Windows Update control.
     
    Daniel Cottam, Sep 6, 2004
    #1
    1. Advertisements

  2. Hi

    Please check this log file for any clues or other error messages:

    %windir%\WindowsUpdate.log

    (%windir% is typically C:\Windows)


    You could also post the last 20-30 lines here.
     
    Torgeir Bakken \(MVP\), Sep 6, 2004
    #2
    1. Advertisements

  3. Thanks.. I can't really work out much from the following..

    2004-09-06 05:13:44+1000 1136 554 Successfully opened event cache file at
    C:\WINDOWS\SoftwareDistribution\EventCache\{938846BC-6CED-4CA3-B588-12106DEF44D2}.bin for reading.
    2004-09-06 05:13:44+1000 704 b2c Trying to make out of proc datastore active
    2004-09-06 05:13:44+1000 704 b2c Out of proc datastore is now active
    2004-09-06 05:13:44+1000 1136 554 PT: Using serverID
    {9482F4B4-E343-43B6-B170-9A65BC822C77}
    2004-09-06 05:13:44+1000 1136 554 PT: Using server URL
    https://v5.windowsupdate.microsoft.com/ClientWebService/client.asmx
    2004-09-06 05:13:44+1000 1136 554 PT: Using serverID
    {9482F4B4-E343-43B6-B170-9A65BC822C77}
    2004-09-06 05:13:44+1000 1136 554 PT: Using server URL
    https://v5.windowsupdate.microsoft.com/ClientWebService/client.asmx
    2004-09-06 05:13:44+1000 1136 554 URL for server is
    http://v5stats.windowsupdate.microsoft.com/ReportingWebService/ReportingWebService.asmx
    2004-09-06 05:13:44+1000 1136 554 Trying to upload 1 events using cached
    cookie.
    2004-09-06 05:13:48+1000 1136 554 DetectCompressionType returning type 0,
    hr=0x1
    2004-09-06 05:13:48+1000 1136 554 Successfully uploaded 1 events.
    2004-09-06 05:13:48+1000 1136 554 Deleted event cache file at
    C:\WINDOWS\SoftwareDistribution\EventCache\{938846BC-6CED-4CA3-B588-12106DEF44D2}.bin.
    2004-09-06 05:18:45+1000 704 b2c Out of proc datastore is shutting down
    2004-09-06 05:18:46+1000 704 b2c Out of proc datastore is now inactive
    2004-09-06 09:20:07+1000 1136 474 Service received logon notification
    2004-09-06 09:20:07+1000 1136 f8 AU received event of 3
    2004-09-06 10:28:01+1000 1136 f8 AU received event of 3
    2004-09-06 12:33:55+1000 3936 714 Trying to make out of proc datastore active
    2004-09-06 12:33:56+1000 3936 714 Out of proc datastore is now active
    2004-09-06 12:38:56+1000 3936 714 Out of proc datastore is shutting down
    2004-09-06 12:38:57+1000 3936 714 Out of proc datastore is now inactive
     
    Daniel Cottam, Sep 6, 2004
    #3
  4. Further to my post of the other events in the event log I booted in safe mode
    and renamed the existing log file so I could make sure I was only getting
    fressh messages..

    I then rebooted and tried running windows update again.. (still with the
    same result) the only messages in the log file were as follows:

    2004-09-06 16:12:25+1000 284 120 WUCheckForUpdatesAtShutdown failed,
    hr=8024000C
    2004-09-06 16:12:28+1000 284 3b4 WUAutoUpdateAtShutdown failed, hr=8024000C
    2004-09-06 16:13:15+1000 1136 1c0 Service Main starts
    2004-09-06 16:13:15+1000 1136 1c0 Using BatchFlushAge = 8049.
    2004-09-06 16:13:15+1000 1136 1c0 Using SamplingValue = 331.
    2004-09-06 16:13:15+1000 1136 1c0 Successfully loaded event namespace
    dictionary.
    2004-09-06 16:13:15+1000 1136 1c0 Successfully loaded client event namespace
    descriptor.
    2004-09-06 16:13:15+1000 1136 1c0 Successfully initialized local event
    logger. Events will be logged at
    C:\WINDOWS\SoftwareDistribution\ReportingEvents.log.
    2004-09-06 16:13:15+1000 1136 1c0 Successfully initialized NT event logger.
    2004-09-06 16:13:15+1000 1136 1c0 Successfully initialized event uploader 0.
    2004-09-06 16:13:15+1000 1136 1c0 Successfully initialized event uploader 1.
    2004-09-06 16:13:15+1000 1136 1c0 WU client with version 5.4.3790.2182
    successfully initialized
    2004-09-06 16:13:15+1000 1136 1c0 Service status is now SERVICE_RUNNING
    2004-09-06 16:13:16+1000 1136 474 Service received connect notification
    2004-09-06 16:14:01+1000 1136 1c0 start delayed initialization of WU client
    2004-09-06 16:14:02+1000 3220 c98 Trying to make out of proc datastore active
    2004-09-06 16:14:02+1000 3220 c98 Out of proc datastore is now active
    2004-09-06 16:14:02+1000 1136 1c0 Client Call Recorder finished delayed
    initialization
    2004-09-06 16:14:02+1000 1136 1c0 Setting AU scheduled install time to
    2004-09-06 17:00:00
    2004-09-06 16:14:02+1000 1136 1c0 AU finished delayed initialization
     
    Daniel Cottam, Sep 6, 2004
    #4
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.