False WSUS errors in Application Event Log

Discussion in 'Update Services' started by Paul Hons, Oct 31, 2007.

  1. Paul Hons

    Paul Hons Guest

    I installed WSUS 3.0 back in April 2007. Since our web server runs several
    different sites (all on separate IPs), we installed to a site other than the
    default. Everything seems to working fine, updates are synchronizing,
    clients receiving updates, etc.

    However, since installation, we get constant errors in the Application Event
    log about all the services not working (although they are). Looking at the
    httperr.log I find the following error

    Date Time Server IP 2317 Server IP 80 HTTP/1.1 GET
    /selfupdate/iuident.cab 400 - Hostname -


    It seems the server itself is trying to contact the WSUS site (on the wrong
    IP) and getting an error. I have gone through all the configuration settings
    and cannot find why the server is trying to contact itself on the wrong IP.

    Server is Windows 2003 R2 Standard

    Any ideas?

    Thanks

    Paul Hons
    Director, Office of Technology
    College of Education
    University of North Texas
    Denton, TX US
     
    Paul Hons, Oct 31, 2007
    #1
    1. Advertisements

  2. Paul Hons

    Tom S Guest

    You checked the servers WSUS settings too? It may be trying to update
    itself on the default port and failing.
    there are several places to look but start with the registry.

    Tom S
     
    Tom S, Oct 31, 2007
    #2
    1. Advertisements

  3. Augusto Alvarez, Nov 1, 2007
    #3
  4. This most likely is occuring because the WSUS virtual server and the Default
    Web Site must be configured to listen on the same IP Addresses and the same
    URL(s), or because those two resources are not configured to listen on the
    localhost address 127.0.0.1.

    Failing to do so will cause the diagnostic tools to be unable to access the
    resources installed on port 80, which is what is causing the indications of
    services not working.
    There it is....: a GET to the port 80 site... failing with a '400' error.
    Actually, the server itself is trying to contact the WSUS site on the
    'localhost' address (127.0.0.1). It *assumes* (because it's a deployment
    requirement) that there is a port 80 server at the localhost address that
    contains the requisite installed resources (namely: SELFUPDATE for legacy AU
    clients). Not finding that resource triggers the noted errors.

    --
    Lawrence Garvin, M.S., MCTS, MCP
    MVP - Software Distribution (2005-2007)
    MS WSUS Website: http://www.microsoft.com/wsus
    My Websites: http://www.onsitechsolutions.com;
    http://wsusinfo.onsitechsolutions.com
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
     
    Lawrence Garvin [MVP], Nov 1, 2007
    #4
  5. Paul Hons

    Paul Hons Guest

    Actually, I don't think that was the problem. I bound 127.0.0.1:80 to the
    website that WSUS is on. Still got the error.

    The only fix that worked was binding the base Windows server IP:80 to the
    WSUS website. That got rid of the errors in the event log.

    Thanks for all of the suggestions.
     
    Paul Hons, Nov 2, 2007
    #5
    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.