Computer has not reported status yet

Discussion in 'Update Services' started by SchoolTech, Mar 6, 2006.

  1. SchoolTech

    SchoolTech Guest

    I have a new computer that I just set up and hooked into WSUS on our
    server. When I bring up the WSUS admin page, it always tells me that it
    doesn't know this computer's status because it has not reported status yet.
     
    SchoolTech, Mar 6, 2006
    #1
    1. Advertisements

  2. Then the next step would be to troubleshoot why this client is not properly
    reporting status.

    (1) Run the Client Diagnostic Tool and post the results.

    (2) Inspect the %windir%\WindowsUpdate.log and post the results from the
    most recent detection and reporting event.
     
    Lawrence Garvin \(MVP\), Mar 6, 2006
    #2
    1. Advertisements

  3. SchoolTech

    SchoolTech Guest

    Oh by the way the homepage tells me the Selfupdate service is not
    running."One or more Update Service components could not be contacted.
    Check your server status and ensure that the Windows Server Update
    Service is running. Non-running services: SelfUpdate"

    The only change of config I was aware of was to change the web site
    authentication for the WSUS Admin site from anonymous to IWA. It's
    possible there could be an authentication issue. However no other
    computers seem to be having trouble updating their status. Every other
    PC is continuing to update its status to WSUS.

    Here is part of the log for today for the affected machine.

    C:\WINDOWS\SoftwareDistribution\ReportingEvents.log.
    2006-03-07 08:35:39+1300 1064 c8 Successfully initialized NT event logger.
    2006-03-07 08:35:39+1300 1064 c8 Successfully initialized event uploader 0.
    2006-03-07 08:35:39+1300 1064 c8 Successfully initialized event uploader 1.
    2006-03-07 08:35:39+1300 1064 c8 WU client with version 5.4.3790.2180
    successfully initialized
    2006-03-07 08:35:39+1300 1064 c8 Service status is now SERVICE_RUNNING
    2006-03-07 08:35:39+1300 1064 530 Successfully opened event cache file
    at
    C:\WINDOWS\SoftwareDistribution\EventCache\{5D3CBC74-6425-4079-BD15-45BA8CF3A8E9}.bin
    for reading.
    2006-03-07 08:35:39+1300 444 1c0 Trying to make out of proc datastore
    active
    2006-03-07 08:35:41+1300 444 1c0 Out of proc datastore is now active
    2006-03-07 08:35:41+1300 1064 530 PT: Using serverID
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2006-03-07 08:35:41+1300 1064 530 Failed to obtain cached cookie with hr
    = 80248008.
    2006-03-07 08:35:41+1300 1064 530 Failed to upload events with hr =
    80248008.
    2006-03-07 08:36:24+1300 1064 c8 start delayed initialization of WU client
    2006-03-07 08:36:24+1300 1064 c8 Client Call Recorder finished delayed
    initialization
    2006-03-07 08:36:24+1300 1064 c8 Setting next AU detection timeout to
    2006-03-06 19:36:24
    2006-03-07 08:36:24+1300 1064 c8 AU finished delayed initialization
    2006-03-07 08:36:24+1300 1064 c8 AU received event of 1
    2006-03-07 08:36:24+1300 1064 c8 WU client succeeds
    CClientCallRecorder::BeginFindUpdates from AutomaticUpdates with call id
    {4C67D305-6ADC-4AE8-8FA2-73E5024FDFC1}
    2006-03-07 08:36:24+1300 1064 4ac WU client executing call
    {4C67D305-6ADC-4AE8-8FA2-73E5024FDFC1} of type Search Call
    2006-03-07 08:36:36+1300 1064 4ac DownloadFileInternal failed for
    http://hcsserver:8530/SelfUpdate/wuident.cab: error 0x80190191
    2006-03-07 08:36:36+1300 1064 4ac IsUpdateRequired failed with error
    0x80244017
    2006-03-07 08:36:36+1300 1064 4ac OS Version = 5.1.2600.2.0.65792
    2006-03-07 08:36:36+1300 1064 4ac Computer Brand = ASUS
    2006-03-07 08:36:36+1300 1064 4ac Computer Model = A7V8X-MX SE
    2006-03-07 08:36:36+1300 1064 4ac Bios Revision = ASUS A7V8X-MX SE ACPI
    BIOS Revision 1003
    2006-03-07 08:36:36+1300 1064 4ac Bios Name = Phoenix - Award BIOS v6.00PG
    2006-03-07 08:36:36+1300 1064 4ac Bios Release Date = 2004-03-12T00:00:00
    2006-03-07 08:36:36+1300 1064 4ac Locale ID = 1033
    2006-03-07 08:36:36+1300 1064 4ac ClientVersion: iuengine.dll =
    5.4.3790.2180
    2006-03-07 08:36:36+1300 1064 4ac ClientVersion: wuapi.dll = 5.4.3790.2180
    2006-03-07 08:36:36+1300 1064 4ac ClientVersion: wuauclt.exe = 5.4.3790.2180
    2006-03-07 08:36:36+1300 1064 4ac ClientVersion: wuauclt1.exe =
    5.4.3790.2180
    2006-03-07 08:36:36+1300 1064 4ac ClientVersion: wuaucpl.cpl = 5.4.3790.2180
    2006-03-07 08:36:36+1300 1064 4ac ClientVersion: wuaueng.dll = 5.4.3790.2180
    2006-03-07 08:36:36+1300 1064 4ac ClientVersion: wuaueng1.dll =
    5.4.3790.2180
    2006-03-07 08:36:36+1300 1064 4ac ClientVersion: wuauserv.dll =
    5.4.3790.2180
    2006-03-07 08:36:36+1300 1064 4ac ClientVersion: wucltui.dll = 5.4.3790.2180
    2006-03-07 08:36:36+1300 1064 4ac PT: Using serverID
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2006-03-07 08:36:36+1300 1064 4ac WU client failed Searching for update
    with error 0x80248008
    2006-03-07 08:36:36+1300 1064 4ac Search Callback Failed, hr is 0x80248008
    2006-03-07 08:36:36+1300 1064 4ac Setting next AU detection timeout to
    2006-03-07 00:36:36
    2006-03-07 08:36:36+1300 1064 4ac WU client calls back to search call
    AutomaticUpdates with code Call failed and error 0x80248008
    2006-03-07 08:36:36+1300 1064 4ac WU client completed and deleted call
    {4C67D305-6ADC-4AE8-8FA2-73E5024FDFC1}
    2006-03-07 08:36:38+1300 1064 42c Service received connect notification
    2006-03-07 08:36:38+1300 1064 c8 AU received event of 3
    2006-03-07 08:36:41+1300 1064 4ac REPORT EVENT:
    {279291A6-ED6F-481D-9233-8096F41F22FC} 80 2006-03-07
    08:36:36+1300 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 0
    80244017 SelfUpdate Failure Software Synchronization Error: Agent failed
    detecting with reason: 0x80244017
    2006-03-07 08:36:41+1300 1064 4ac REPORT EVENT:
    {1FC62A66-F296-49B5-91F9-0D32169CA4AE} 81 2006-03-07
    08:36:36+1300 1 148 101 {00000000-0000-0000-0000-000000000000} 0
    80248008 AutomaticUpdates Failure Software Synchronization Error: Agent
    failed detecting with reason: 0x80248008
    2006-03-07 08:36:41+1300 1064 4ac Created new event cache file at
    C:\WINDOWS\SoftwareDistribution\EventCache\{694CFE06-8EAD-430C-9B96-6D2EDD432BC7}.bin
    for writing.
    2006-03-07 08:36:41+1300 1064 4ac Reopened existing event cache file at
    C:\WINDOWS\SoftwareDistribution\EventCache\{8D5147EF-CFBE-46BA-B795-BC1EE6412143}.bin
    for writing.
    2006-03-07 08:36:47+1300 1064 c8 AU received event of 1
    2006-03-07 08:36:47+1300 1064 c8 Forced install timer expired for
    scheduled install
    2006-03-07 08:36:49+1300 1064 c8 Setting AU scheduled install time to
    2006-03-07 14:00:00
    2006-03-07 08:37:07+1300 1064 42c Service received logon notification
    2006-03-07 08:37:07+1300 1064 c8 AU received event of 3
    2006-03-07 08:41:20+1300 444 1c0 Out of proc datastore is shutting down
    2006-03-07 08:41:21+1300 444 1c0 Out of proc datastore is now inactive

    The rest of today's log is essentially the above information repeated in
    various cycles.
     
    SchoolTech, Mar 7, 2006
    #3
  4. SchoolTech

    SchoolTech Guest


    WSUS Client Diagnostics Tool

    Checking Machine State
    Checking for admin rights to run tool . . . . . . . . . PASS
    Automatic Updates Service is running. . . . . . . . . . PASS
    Background Intelligent Transfer Service is not running. PASS
    Wuaueng.dll version 5.4.3790.2180 . . . . . . . . . . . PASS
    This version is SUS 1.0

    Checking AU Settings
    AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
    Option is from Policy settings

    Checking Proxy Configuration
    Checking for winhttp local machine Proxy settings . . . PASS
    Winhttp local machine access type
    <Direct Connection>
    Winhttp local machine Proxy. . . . . . . . . . NONE
    Winhttp local machine ProxyBypass. . . . . . . NONE
    Checking User IE Proxy settings . . . . . . . . . . . . PASS
    User IE Proxy. . . . . . . . . . . . . . . . . NONE
    User IE ProxyByPass. . . . . . . . . . . . . . NONE
    User IE AutoConfig URL Proxy . . . . . . . . . NONE
    User IE AutoDetect
    AutoDetect not in use

    Checking Connection to WSUS/SUS Server
    WUServer = http://myserver:8530
    WUStatusServer = http://myserver:8530
    UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
    Connection to server. . . . . . . . . . . . . . . . . . PASS
    SelfUpdate folder is present. . . . . . . . . . . . . . PASS

    Press Enter to Complete
     
    SchoolTech, Mar 7, 2006
    #4
  5. The answer for this is at
    What does WSUS mean by "Selfupdate service not running"?
    http://wsusinfo.onsitechsolutions.com/articles/020.htm

    This is probably what is causing all of your other errors, so I'll defer my
    reply to the logfiles posted until you make these changes and report the
    results of the changes.
    There should be no legit reason to change /any/ permissions from "anonymous"
    to IWA.... that may well be what's causing the Selfupdate failure.

    See this article for the /correct/ IIS and NTFS permissions for WSUS:
    What are the correct IIS and NTFS permissions for WSUS?
    http://wsusinfo.onsitechsolutions.com/articles/016.htm
     
    Lawrence Garvin, Mar 8, 2006
    #5
  6. SchoolTech

    SchoolTech Guest

    Both Anonymous and IWA are ticked in the authentication settings.
    Still have to check NTFS permissions on the directory.

    However at the same time I would like to point out that only the one
    machine out of about 20 so far hooked to the server has any problems.

    I'm setting up a brand new machine tomorrow so it will be useful for
    comparison.

    The problem machine is also running Internet tracking software which may
    be causing a problem as well.
     
    SchoolTech, Mar 8, 2006
    #6
  7. SchoolTech

    SchoolTech Guest

    In addition to WSUS running on port 8530 there is also a web site
    running on the default port 80 which is for other purposes
    (http://myserver/). This web site has IWA turned on and anonymous access
    turned off, because it is for a specific group of users and access needs
    to be controlled.

    As this is in a completely different file path (C:\inetpub etc) it
    shouldn't be affected by ACL permissions with respect to C:\program
    files\Update services.
     
    SchoolTech, Mar 8, 2006
    #7
  8. SchoolTech

    SchoolTech Guest

    This is an unsatisfactory answer. It tells me that despite the fact that
    WSUS does not use the default web server on port 80 at all, it can't be
    used for anything else because the configuration of that default site
    can't be changed.

    Quote:
    "Selfupdate" is not a service listed in services, it is a virtual
    directory contained in the WSUS virtual servers. When using a port 8530
    server there are two instances of the selfupdate. The first is in the
    port 8530 virtual server, and rarely is the cause of this problem. The
    other is in the port 80 virtual server (normally the Default Web
    Server), and almost always is traced to the absence of anonymous access
    permissions on the virtual server or that specific virtual
    directory.


    But I removed anonymous access permissions on the default web server
    (port 80 virtual server) because I want to restrict access to it AND
    WSUS is using the port 8530 virtual server and it doesn't need to use
    the port 80 server.

    Every client machine goes to port 8530 not port 80.
     
    SchoolTech, Mar 12, 2006
    #8
  9. Well, there's your first erroneous assumption, because the WSUS server
    /DOES/ use the port 80 server, on every installation, even if the WSUS
    server is actually installed on an alternate virtual server at port 8530.
    Is this a belief you have about the "Default Web Site", or do you have a
    specific application running on the WSUS machine that has specific
    requirements that conflict with WSUS?
    Doh.... WHY do you want to restrict access to it? The act of removing
    anonymous access BREAKS WSUS. You have a choice. Restore anonymous access,
    or put WSUS on a different system.
    An incorrect statement.
    An incorrect statement.

    Reading the messages in this newsgroup will provide a plethra of evidence
    demonstrating how WSUS uses both virtual servers, both ports and why. The
    short and simple answer is that LEGACY AU clients cannot communicate on
    non-standard ports, they must use port 80. If you've blocked access to port
    80, then the LEGAC AU clients will /never/ update.

    btw... reading the Deployment Guide would be a good idea, also.

    And, as noted, this /one/ problem /is/ causing all of your others.
     
    Lawrence Garvin \(MVP\), Mar 12, 2006
    #9
  10. SchoolTech

    SchoolTech Guest

    We shouldn't have to buy another server because WSUS dictates that it
    must take over the one we are using.

    That IIS server is being used to run several web sites, and they don't
    have conflicts with WSUS... only because WSUS doesn't demand that every
    site on the server must be configured a certain way.
    The registry settings for every computer on the network for AU are for
    this path:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
    "WUServer"="http://hcsserver:8530"
    "WUStatusServer"="http://hcsserver:8530"

    It clearly shows port 8530 to be used. The machines should therefore be
    communicating on that port because that's the one they are told to
    communicate on.
    Is there any way of deploying WSUS on the web server so that I can use
    the port 80 server default web site and configure it independently
    without blocking Selfupdate or any other WSUS service.
     
    SchoolTech, Mar 16, 2006
    #10
  11. It doesn't dictate anything, But if you expect to have multiple web
    sites/services running in the SAME virtual server, then you'll need to work
    out the necessary co-existence requirements.

    Frankly, if you have web sites/services that you do NOT want to have
    anonymous access enabled for, you need to get them OUT of the Default Web
    Site virtual server, and into their own virtual server, where you /can/
    control the appropriate access permissions appropriately.
    WSUS doesn't demand any such thing.
    =YOU= need to spend some time reading the documentation.

    Frankly, you've got a bit too much attitude, and a bit too little
    awareness/knowledge of the product.

    I've given you the correct answers to your questions.

    Do with them what you wish.

    The limitation is NOT caused by WSUS, it's caused by the legacy Automatic
    Updates clients that can ONLY communicate via port 80.

    Once you've upgraded ALL of your client systems to the latest Windows Update
    Agent (which is capable of communicating with WSUS exclusively on port
    8530), then you can remove the WSUS components from the Default Web Site.

    Of course, the WSUS server will complain that the "Selfupdate service is not
    running" (a correct statement, since it will have been completely removed),
    but you can safely ignore that error in that scenario.
     
    Lawrence Garvin \(MVP\), Mar 19, 2006
    #11
  12. SchoolTech

    SchoolTech Guest

    Is that this update:
    Windows Installer 3.1 v2 (3.1.4000.2435)

    Or is it another update, if so, which?

    Can I slipstream this into the SP2 slipstreamed install files that I have?

    Thanks for your help.
     
    SchoolTech, Mar 26, 2006
    #12
  13. The Windows Update Agent standalone install download locations:

    For x86-based computers (WindowsUpdateAgent20-x86.exe)
    http://go.microsoft.com/fwlink/?LinkId=43264

    (above file will work for Win2k SP3 and SP4, WinXP RTM/SP1/SP2, and
    Win2k3 RTM/SP1)

    For x64-based computers (WindowsUpdateAgent20-x64.exe):
    http://go.microsoft.com/fwlink/?LinkId=43265

    For Itanium-based computers (WindowsUpdateAgent20-ia64.exe):
    http://go.microsoft.com/fwlink/?LinkId=42538

    Even if it is not listed in the help screen, it looks like
    WindowsUpdateAgent20-x86.exe supports the /Integrate command line
    switch...
     
    Torgeir Bakken \(MVP\), Mar 27, 2006
    #13
    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.