This Computer has not reported status yet

Discussion in 'Windows Update' started by bzumwalt99, Jun 26, 2008.

  1. bzumwalt99

    bzumwalt99 Guest

    Hello, I am having problems with a few clients running XP Pro SP 2 that are
    not reporting in into WSUS.

    They show up as clients in WSUS but are not showing their Status Report. I
    have tried all the following: disjoining the computer from the domain.
    Renaming the computer, using the wsuaclt /resetauthorization /detectnow
    commands (which do work) after removing the client and readding it.

    I am running WSUS 3.0 SP1. This is only happening to a handful of clients.
    All computers are receiving their group policy correctly etc. I have also run
    the WSUS client diagnostic tool and every thing passes.

    I am truly stumped on these machines. I can see other people out there have
    had this problem but there seems no remedy to the issue.

    Any ideas or help is greatly appreciated!

    Regards,
    Brandon

    Does anyone know where to start troublshooting this issue? I have also done a
     
    bzumwalt99, Jun 26, 2008
    #1
    1. Advertisements

  2. PA Bear [MS MVP], Jun 26, 2008
    #2
    1. Advertisements

  3. bzumwalt99

    Thomas Guest

    Thomas, Jun 26, 2008
    #3
  4. bzumwalt99

    mackdaddy315 Guest

    First make sure your policy says it is pointing to the correct wsus
    box by running a rsop.
    Try the following at the client end:

    cd c:\windows\system32\
    ipconfig /flushdns
    ipconfig /registerdns
    nbtstat -R
    net stop "Automatic Updates"
    net stop "BITS"
    net start "Automatic Updates"
    net start "BITS"
    wuauclt /detectnow
    wuauclt /reportnow

    btw you can use psexec to run this from the server to the clients as a
    batch process. handy script that solves alot of wsus related issues.
     
    mackdaddy315, Jun 29, 2008
    #4
  5. Or using the Client Diagnostic Tool, which is the *correct* Step 1 in any
    client-side diagnostic process..

    Or inspecting the WindowsUpdate.log which logs the configured server about
    every tenth line one way or another.

    But we already know the server URL is correct, or they would not have even
    =registered= with the WSUS Server, -- which they already did.
    As for this script, I'm not sure where it came from, but it's pretty much
    trash.
    Flushing the DNS cache is pointless -- the clients have already registered
    with the WSUS Server. DNS is correct.
    Refreshing the DHCP lease and re-registering the client's hostname in DNS
    does nothing to address this issue.
    Reloading the NetBios name cache is pointless. This is a TCP/IP application.
    Restarting BITS is useless.
    Restarting Automatic Updates only has benefit if the registry has been
    edited and has new configuration values.
    /reportnow is an invalid switch,

    and the O.P. already stated that 'wuauclt /resetauthorization /detectnow'
    was successfully executed.
    Throw this script away. It does nothing of substance except initiate a
    detection event.

    The *CORRECT* next step based on the description provided is:
    Inspect the %windir%\WindowsUpdate.log to determine why the client has
    registered but is not reporting.

    --
    Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
    Senior Data Architect, APQC, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2008)

    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, Jun 30, 2008
    #5
  6. bzumwalt99

    Rolf Lidvall Guest

    Rolf Lidvall, Jul 7, 2008
    #6
  7. wuauclt /detectnow

    will also send the events to the server.

    There really seems to be no point to the /reportnow switch, assuming it even
    actually does anything.

    To my knowledge, it's still undocumented, either way



    --
    Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
    Senior Data Architect, APQC, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2008)

    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, Jul 9, 2008
    #7
  8. bzumwalt99

    jeps Guest

    I have the same problem "has not reported status yet". I have search all the
    froums and no one has an answer. IS there an answer from Microsoft?

    Thanks Jeremy

     
    jeps, Jul 30, 2008
    #8
  9. "Has not reported status yet" generally means that something is broken on
    the client side.

    Next step is to inspect the WindowsUpdate.log for error messages that
    provide additional details.


    --
    Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
    Senior Data Architect, APQC, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2008)

    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, Jul 30, 2008
    #9
  10. bzumwalt99

    jwchoo Guest


    HEreis the log

    2008-07-31 10:28:21+0100 1176 4a8 PT: Using serverID {3DA21691-
    E39D-4DA6-8A4B-B43877BCB1B7}
    2008-07-31 10:28:21+0100 1176 4a8 Failed to obtain cached cookie with
    hr = 80248008.
    2008-07-31 10:28:21+0100 1176 4a8 Failed to upload events with hr =
    80248008.
    2008-07-31 10:33:21+0100 3252 63c Out of proc datastore is shutting
    down
    2008-07-31 10:33:22+0100 3252 63c Out of proc datastore is now
    inactive
    2008-07-31 10:38:21+0100 1176 bf4 Successfully opened event cache file
    at C:\WINDOWS\SoftwareDistribution\EventCache\{FF08E068-2F58-4EE1-8D01-
    DA9354B01DE5}.bin for reading.
    2008-07-31 10:38:21+0100 132 404 Trying to make out of proc datastore
    active
    2008-07-31 10:38:22+0100 132 404 Out of proc datastore is now active
    2008-07-31 10:38:22+0100 1176 bf4 PT: Using serverID {3DA21691-
    E39D-4DA6-8A4B-B43877BCB1B7}
    2008-07-31 10:38:22+0100 1176 bf4 Failed to obtain cached cookie with
    hr = 80248008.
    2008-07-31 10:38:22+0100 1176 bf4 Failed to upload events with hr =
    80248008.
    2008-07-31 10:40:10+0100 1176 49c Service received connect
    notification
    2008-07-31 10:40:10+0100 1176 cc8 AU received event of 3
    2008-07-31 10:40:18+0100 1176 49c Service received disconnect
    notification
    2008-07-31 10:40:18+0100 1176 cc8 AU received event of 3
    2008-07-31 10:40:18+0100 1176 49c Service received connect
    notification
    2008-07-31 10:40:18+0100 1176 cc8 AU received event of 3
    2008-07-31 10:40:19+0100 1176 49c Service received logon notification
    2008-07-31 10:40:19+0100 1176 cc8 AU received event of 3
    2008-07-31 10:40:53+0100 3376 808 CreateObject for
    Microsoft.Update.AgentInfo failed: error 0x800401f3
    2008-07-31 10:40:53+0100 1176 544 WU client succeeds
    CClientCallRecorder::EnumerateService
    2008-07-31 10:45:53+0100 132 404 Out of proc datastore is shutting
    down
    2008-07-31 10:45:54+0100 132 404 Out of proc datastore is now
    inactive
    2008-07-31 10:48:22+0100 1176 77c Successfully opened event cache file
    at C:\WINDOWS\SoftwareDistribution\EventCache\{FF08E068-2F58-4EE1-8D01-
    DA9354B01DE5}.bin for reading.
    2008-07-31 10:48:22+0100 2096 4ac Trying to make out of proc datastore
    active
    2008-07-31 10:48:22+0100 2096 4ac Out of proc datastore is now active
    2008-07-31 10:48:22+0100 1176 77c PT: Using serverID {3DA21691-
    E39D-4DA6-8A4B-B43877BCB1B7}
    2008-07-31 10:48:22+0100 1176 77c Failed to obtain cached cookie with
    hr = 80248008.
    2008-07-31 10:48:22+0100 1176 77c Failed to upload events with hr =
    80248008.
    2008-07-31 10:53:22+0100 2096 4ac Out of proc datastore is shutting
    down
    2008-07-31 10:53:24+0100 2096 4ac Out of proc datastore is now
    inactive
    2008-07-31 10:58:22+0100 1176 77c Successfully opened event cache file
    at C:\WINDOWS\SoftwareDistribution\EventCache\{FF08E068-2F58-4EE1-8D01-
    DA9354B01DE5}.bin for reading.
    2008-07-31 10:58:23+0100 3688 ddc Trying to make out of proc datastore
    active
    2008-07-31 10:58:23+0100 3688 ddc Out of proc datastore is now active
    2008-07-31 10:58:23+0100 1176 77c PT: Using serverID {3DA21691-
    E39D-4DA6-8A4B-B43877BCB1B7}
    2008-07-31 10:58:23+0100 1176 77c Failed to obtain cached cookie with
    hr = 80248008.
    2008-07-31 10:58:23+0100 1176 77c Failed to upload events with hr =
    80248008.
    2008-07-31 11:03:23+0100 3688 ddc Out of proc datastore is shutting
    down
    2008-07-31 11:03:24+0100 3688 ddc Out of proc datastore is now
    inactive
    2008-07-31 11:08:23+0100 1176 da4 Successfully opened event cache file
    at C:\WINDOWS\SoftwareDistribution\EventCache\{FF08E068-2F58-4EE1-8D01-
    DA9354B01DE5}.bin for reading.
    2008-07-31 11:08:23+0100 4060 ab4 Trying to make out of proc datastore
    active
    2008-07-31 11:08:24+0100 4060 ab4 Out of proc datastore is now active
    2008-07-31 11:08:24+0100 1176 da4 PT: Using serverID {3DA21691-
    E39D-4DA6-8A4B-B43877BCB1B7}
    2008-07-31 11:08:24+0100 1176 da4 Failed to obtain cached cookie with
    hr = 80248008.
    2008-07-31 11:08:24+0100 1176 da4 Failed to upload events with hr =
    80248008.

    here is Client Diag
    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 running. . . PASS
    Wuaueng.dll version 5.4.3790.5512 . . . . . . . . . . . PASS
    This version is WSUS 2.0

    Checking AU Settings
    AU Option is 3 : Notify Prior to Install. . . . . . . . PASS
    Option is from Policy settings

    Checking Proxy Configuration
    Checking for winhttp local machine Proxy settings . . . PASS
    Winhttp local machine access type
    <Using Proxy>
    Winhttp local machine Proxy
    xxxxxxxx
    Winhttp local machine ProxyBypass
    :8080
    Checking User IE Proxy settings . . . . . . . . . . . . PASS
    User IE Proxy
    http=192.xxx.x.xx:8080;https=192.xxx.x..xx:
    8080;ftp=192.xxx.x.
    8080;gopher=192.xxx.x.xx:8080
    User IE ProxyByPass
    192.168.0.*;<local>
    User IE AutoConfig URL Proxy . . . . . . . . . NONE
    User IE AutoDetect
    AutoDetect not in use

    Checking Connection to WSUS/SUS Server
    WUServer = http://xxxxxxx
    WUStatusServer = http://xxxxxx
    UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
    Connection to server. . . . . . . . . . . . . . . . . . PASS
    SelfUpdate folder is present. . . . . . . . . . . . . . PASS
     
    jwchoo, Jul 31, 2008
    #10
  11. bzumwalt99

    jwchoo Guest

    The Client Diag show Wuaueng.dll version
    5.4.3790.5512 . . . . . . . . . . . PASS
    This version is WSUS 2.0

    IS this coreect but I am using WSUS3.0

    Jeremy
     
    jwchoo, Jul 31, 2008
    #11
  12. bzumwalt99

    DaveMills Guest

     
    DaveMills, Jul 31, 2008
    #12
  13. bzumwalt99

    DaveMills Guest

    Looks to me like the client is not talking to the server at all. Since you have
    editing all the server name and ip addresses you may have edited out the cause
    of the problem. Quite often the problem is because of an incorrect server
    specification in the GPO, an extra dot or some other simple error like a
    trailing \
    It also looks like the WSUS client is trying to use a proxy. Is the bypass IP
    mask correct.

    The client has not updated to WSUS 3
     
    DaveMills, Jul 31, 2008
    #13
  14. Given these settings, the WUA will be trying to access the WSUS server via the
    proxy. Might the proxy be blocking access?

    Harry.
     
    Harry Johnston [MVP], Jul 31, 2008
    #14
  15. bzumwalt99

    jwchoo Guest

    Hi Harry
    The Wsus is also the proxy server. But isn't the proxy being by passed
    for local networks. All the clients are showing up with the orange
    triangle except for 2 showing the red round symbol with a cross when
    hightlighted it says not reported status for 289 or more days and 189
    or more days respectively. So they must be able to contact the wsus. I
    do not understand why the proxy is blocking access.

    Jeremy
     
    jwchoo, Aug 1, 2008
    #15
  16. bzumwalt99

    jwchoo Guest

    Dear Dave

    You can see they are all passes. The clients are showing up in the
    WSUS as orange traiagles and red circles. SO they must be touching
    base with WSUS.
    The setup is WSUS 3 is runnig on a Windows 2003 Server Sp2. The Proxy
    server is on the same server.

    Thansk
    Jeremy
     
    jwchoo, Aug 1, 2008
    #16
  17. The ProxyBypass setting has nothing in it but :8080. I'm no expert in Winhttp
    proxy settings, but that certainly doesn't look right if you're expecting it to
    bypass the local network.

    It would help if you could post the actual output. But perhaps if you look at
    these settings, particularly if you compare them to one on a machine that is
    working, the problem may be obvious.

    ... you realise the Winhttp settings are distinct from the user settings? For
    everything to work properly, both have to be set correctly, but the Winhttp
    settings are the ones relevant to the errors appearing in the log.

    Harry.
     
    Harry Johnston [MVP], Aug 1, 2008
    #17
  18. bzumwalt99

    DaveMills Guest

    Will the Proxy server know that it should not forward HTTP requests to itself to
    the Internet?
     
    DaveMills, Aug 1, 2008
    #18
  19. bzumwalt99

    DaveMills Guest

    If you are thinking of the IE setting "Bypass Proxy Server for local addresses"
    then you need to be aware that "local" means addresses without a ".", i.e.
    192.168.1.2 is NOT local because it has a dot.
     
    DaveMills, Aug 1, 2008
    #19
  20. bzumwalt99

    jwchoo Guest

    I have run test below and passed test. There is conectivity to WSUS.

    To check network connectivity on the WSUS client computer

    1. Click Start, and then click Run.

    2. In the Open box, type iexplore and then press ENTER

    3. In the Internet Explorer Address bar, type:

    http://WSUSServerName/iuident.cab

    where WSUS server name is the name of your WSUS server. Ensure that
    you are prompted to download or open Iuident.cab. This verifies
    network connectivity from the WSUS client and the availability of the
    Iuident.cab file on the WSUS server.

    Jeremy
     
    jwchoo, Aug 2, 2008
    #20
    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.