Automatic updates stopped working after SP3 has been installed

Discussion in 'Windows Update' started by Alexander, Jun 3, 2008.

  1. Alexander

    groovyf Guest

    The WSUS server is running the internal DB that shipped with WSUS3 and my
    clients are XP.
    All the PCs running XP/Vista that are already listed and functioning in WSUS
    are checking-in correctly. I'm finding it's only new PCs that I'm building
    and adding to the domain that are causing the issue.

    Has there been some essential update to WSUS that may have installed
    automatically?
    It can't be the client, as the image I'm working from was working fine 2
    weeks ago (not added any new windows updates nor re-imaged.) And these new
    PCs I'm trying to get working aren't updated as they don't check-in to WSUS.
    It all points to the WSUS db, but what's happened? How has this suddenly
    occurred?

     
    groovyf, Jun 18, 2008
    #21
    1. Advertisements

  2. Alexander

    Chris Guest

    Yes it has 'suddenly' ocurred for me too. This is probably the first time I
    have added a new client since I installed SP1 onto the WSUS server but the
    existing clients are working fine. It seems as though there is an issue with
    the keys in the database. Mine runs on SQL 2005 but the problem ocurrs with
    the internal one too so it must be the code which is run when a new client is
    created. But when has this code changed? I'd have said in SP1 but your's
    isn't on SP1 so that's not it.

    Are there any Microsoft employees reading this? Can you tell us if this is
    a known issue or should I log it?


     
    Chris, Jun 18, 2008
    #22
    1. Advertisements

  3. Alexander

    groovyf Guest

    Actually, I should have mentioned my WSUS3 server is on SP1, and has been for
    a while now, and I've certainly added new clients since upgrading to SP1.
    I had a thought that maybe the internal DB had reached its limits somehow,
    but it's only 1.6GB in size with around 240 clients. And now you've said
    you're using SQL 2005 and getting same problems so I doubt the internal DB is
    at fault.

     
    groovyf, Jun 18, 2008
    #23
  4. Alexander

    Ray Chan Guest

    I just ran into the same issue. Have about 70 clients all running XP SP2
    connecting to a 2003 server. All of them are working fine, however, I just
    started building a couple of new machines and noticed they don't report with
    the same error. After some further investigating, I realized it's Office
    2003 that's causing the problem. When I uninstall Office, it reports
    normally and grab updates. But once I reinstall it, it can't connect. I've
    even tried manually removing each part of Office to pinpoint the issue but it
    appears once any part of it is installed it breaks the service. I've also
    tried all the fixes mentioned here to no avail.

    Please help...
     
    Ray Chan, Jun 18, 2008
    #24
  5. Alexander

    Chris Guest

    Thinking about when this problem started, yesterday when I was first setting
    up this machine on the network, it appeared to have frozen so I hit the power
    switch to force it to power down. I expect it was in the middle of creating
    something in the database and because that didn't fully complete it has
    caused problems, but then any stored procedures etc would have been run on
    the server not the client so it shouldn't matter that the client was shut
    down!!

    I can still run the updates from the Microsoft website so it is the WSUS
    server at fault not the client. It's just finding how to remove the
    duplicated item that is causing the problem...


     
    Chris, Jun 18, 2008
    #25
  6. Alexander

    Ray Chan Guest

    Hi Chris, does your image have Office pre-installed?
     
    Ray Chan, Jun 18, 2008
    #26
  7. Alexander

    Chris Guest

    Hi Ray,

    Yes the laptop factory installed image has Office 2007 OEM which I haven't
    activated yet.

    Why do you ask?

    Regards

    Chris
     
    Chris, Jun 18, 2008
    #27
  8. Alexander

    Williamt Guest

    I have exactly the same problem on a new PC, just added to the domain (SBS
    2003). The PC has Windows XP and I updated it to SP2 before adding it to the
    domain.
    It also has MS Office 2007 on the PC (Not 2003 as others seem to mention
    might be involved).

    The Windows Update via the WWW still functions correctly, so I too would
    assume it's a server side problem...

    Any help appreciated.

     
    Williamt, Jun 18, 2008
    #28
  9. Alexander

    Ray Chan Guest

    Can you try uninstalling it and see if it'll register with WSUS? That's the
    only way it works for me and I just wanted to see if others are having the
    same issue.
     
    Ray Chan, Jun 18, 2008
    #29
  10. Alexander

    Chris Guest

    Unbelievable! I can't understand why Office is stopping it working. I
    uninstalled the Office 2007 Small Business edition (and all the components
    that come with it) and it now connects to the local WSUS. I am just waiting
    for it to provide a status report and then will see if I can reintroduce
    Office to it...

    The last time we bought some PC's we had Office pre-installed and no
    problems but that was probably before we upgraded to WSUS3 SP1.

    Ah, it's just finished the status report. Now for Office.

    Thanks Ray,

    Chris
     
    Chris, Jun 18, 2008
    #30
  11. Alexander

    Ray Chan Guest

    Reinstalling Office afterwards breaks it again for me. Hopefully it works
    for you.
     
    Ray Chan, Jun 18, 2008
    #31
  12. Alexander

    Chris Guest

    So far so good, I have got the default installation of Word, Excel, Outlook
    etc installed from disk 1 and WSUS still works. I don't want Business
    Contact Manager etc so don't need to install any more of office. From
    memory, Dell had installed PowerPoint Viewer, Office 2003 Web Components and
    something else which just wasn't necessary. Also I've removed the SQL stuff
    for BCM.

    This was very weird, perhaps something affected the way the client was
    posting the SOAP request to the WSUS server which made it look like a server
    issue, but thankfully it is a problem with the client.

    Thanks for posting your help Ray, I hope you can find the solution too, it
    must be around Office for sure.

    Regards

    Chris
     
    Chris, Jun 18, 2008
    #32
  13. Alexander

    APlus Guest

    My problem is addressed at:
    http://blogs.technet.com/wsus/archive/2008/06/18/client-server-synchronization-issues.aspx.

    Thx 2 Harry and Wilfried.

    A+


     
    APlus, Jun 18, 2008
    #33
  14. Alexander

    groovyf Guest

    Someone (mendocinosunrise) has posted something rather interesting over at
    www.wsus.info forums. I've yet to try this, but shall do so in the morning.
    I'll paste it here:

    I fought with the same error, then gave up & emailed MS.
    NOTE: the workaround below didn't work at first because the problem update
    was expired. However, I ran through the steps a couple of times & then
    manually resynchronized the WSUS server. After that, clients started
    synchronizing correctly.

    Here's their workaround from the MS tech:
    Thank you for the log. The error you see repeated in the log, 0x8024400E, is
    consistent with an issue that has been appearing recently. I've posted some
    root cause information and steps to resolve below. Please review the
    information and apply the workaround. This is a new problem, so a KB article
    has not yet been released.

    <snip>

    " Root Cause:
    A recent revision to the 'Office 2003 Service Pack 1' update has resulted in
    some WSUS 3.0 servers syncing that revision to enter an inconsistent state
    with respect to the update's approvals. When computers with products related
    to Office 2003 talk to such a server, the web service is unable to process
    the approvals resulting in the detection failure.

    Workaround:
    In order to reset the approvals to a consistent state on the WSUS server,
    follow these steps from the WSUS Administration Console
    1. Find the 'Office 2003 Service Pack 1' update in the updates list. This
    may involve changing the Approval and Status filters in the update UI (set
    the Status to "Any" and the Approval to "Declined" - if you don't see it then
    set the Approval to "Any except Declined"
    2. Perform the following steps:
    a. First make sure the update is declined.
    i. If the update is not yet declined, right click on the update and decline
    it.
    b. Next, approve the update.
    i. Right click on the update and select the 'Approve...' option in the
    context menu.
    ii. In the 'Approve Updates' dialog that opens, just click 'OK'. Dismiss the
    'Approval Progress' dialog that appears.
    c. Next, decline the update.
    i. Right click on the update and select the 'Approve...' option in the
    context menu.
    ii. In the 'Approve Updates' dialog that opens, just click 'OK'. Dismiss the
    'Approval Progress' dialog that appears.

    The computers that were failing detection will now successfully complete
    detection against the server and receive any applicable updates.

    Note: If you have a hierarchy of WSUS servers, these steps must be performed
    on each server, starting with the top-level server. If one of the servers is
    a replica child, one must first change it to be autonomous, then perform the
    steps above, then change it back to being a replica. This can be done from
    the Options/Update Source and Proxy Server Dialog."
     
    groovyf, Jun 18, 2008
    #34
  15. Alexander

    groovyf Guest

    Have just performed the above (thanks to mendocinosunrise), and all is back
    to normal.
     
    groovyf, Jun 19, 2008
    #35
  16. Alexander

    Alexander Guest

    This definetely works!! Thanks to everybody!

    (Mention the misspelling in step "c": I guess the author meant to select
    Decline, not Approve)
     
    Alexander, Jun 19, 2008
    #36
  17. Hi Eddie,

    i tried to load down your tool, but it is offline at the moment.
    Is there a chance to get your tool soon.
    We do need it urgently.
    We have some clients who show the described difficulties in connecting to
    the server succesfully.

    here is an line from our lofgiles.
    SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error
    code = 400, HTTP status code = 200

    Any help qould be greatly appreciated.

    Regards,
    Robin
     
    Robin Seeländer, Jun 27, 2008
    #37
  18. Eddie's utility has been withdrawn for review.

    Are your problems only on machines where WinXP SP3 has been installed (which
    is the subject of this thread)?

    Do the clients update via WSUS or Windows Update?
    --
    ~Robear Dyer (PA Bear)
    MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
    AumHa VSOP & Admin http://aumha.net
    DTS-L http://dts-l.net/
     
    PA Bear [MS MVP], Jun 27, 2008
    #38
  19. Christopher Hill, Jun 27, 2008
    #39
  20. PA Bear [MS MVP], Jun 27, 2008
    #40
    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.