none
Clients Will not connect to WSUS

    Question

  • I just installed WSUS 3 and none of the clients will communicate with it. This is whats in the windowsupdate error log:

    2009-02-25    11:35:56:602     612    e0c    PT    WARNING: Cached cookie has expired or new PID is available
    2009-02-25    11:35:56:602     612    e0c    PT    Initializing simple targeting cookie, clientId = f541c336-ae14-4a38-832d-5ff03c670c32, target group = , DNS name = is-manager.co.matagorda.tx.us
    2009-02-25    11:35:56:602     612    e0c    PT      Server URL = http://avg/SimpleAuthWebService/SimpleAuth.asmx
    2009-02-25    11:35:56:665     612    e0c    PT    WARNING: GetAuthorizationCookie failure, error = 0x80244016, soap client error = 10, soap error code = 0, HTTP status code = 400
    2009-02-25    11:35:56:665     612    e0c    PT    WARNING: Failed to initialize Simple Targeting Cookie: 0x80244016
    2009-02-25    11:35:56:665     612    e0c    PT    WARNING: PopulateAuthCookies failed: 0x80244016
    2009-02-25    11:35:56:665     612    e0c    PT    WARNING: RefreshCookie failed: 0x80244016
    2009-02-25    11:35:56:665     612    e0c    PT    WARNING: RefreshPTState failed: 0x80244016
    2009-02-25    11:35:56:665     612    e0c    PT    WARNING: PTError: 0x80244016
    2009-02-25    11:35:56:665     612    e0c    Report    WARNING: Reporter failed to upload events with hr = 80244016.
    2009-02-25    11:39:48:887     612    bb0    DnldMgr    Error 0x80072af9 occurred while downloading update; notifying dependent calls.
    2009-02-25    11:39:51:219     612    3e4    DnldMgr    Error 0x80072af9 occurred while downloading update; notifying dependent calls.
    2009-02-25    11:39:53:551     612    3e4    DnldMgr    Error 0x80072af9 occurred while downloading update; notifying dependent calls.
    Wednesday, February 25, 2009 5:50 PM

Answers

  • First off I know ZERO about IIS and it doesnt help that IIS isnt included in any of their current training curriculem.

    Whats happening is when I tried to go to the site that is listed in the error log of http://avg I get something different. I think the server I am using has some sort of hardware diagnostics software that is web accessible which is blocking the WSUS information. I went back into the WSUS installation and found that it installed on some other port so I went and reconfigured the policy to include this port number and now its picking up the computers. Now if Microsoft would include a group policy that would force computers to restart at certain times I would be all set.
    Wednesday, March 04, 2009 5:40 PM

All replies

  • 2009-02-25    11:35:56:602     612    e0c    PT      Server URL = http://avg/SimpleAuthWebService/SimpleAuth.asmx

    2009-02-25    11:35:56:665     612    e0c    PT    WARNING: Failed to initialize Simple Targeting Cookie: 0x80244016

    Error code 0x80244016 = HTTP 400  -- in short, the URL provided is invalid.

    This would be the http://avg part of the URL. Can you provide additional details about your WSUS installation, please?
    Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Wednesday, February 25, 2009 8:04 PM
    Moderator
  • I dont know what answers you would want. The server that the WSUS is on is called AVG. I admit I have no clue what I am doing and cant seem to find much information that helps. All I did was follow the step by step installation guide based on the 2003 server install. Its up and running on the server but no clients will talk to it. They all show the same error message.
    Friday, February 27, 2009 3:20 PM
  • That error seems familiar but it's been so long I've forgotten what caused it or its solution. However, I wouldn't post without giving you some feedback. Here are two ways I usually fix any errors with pcs having problems updating:

    1) On pc with error stop the automatic updates service

    2) Clear the log so you won't have to scroll through many errors

    3) Delete the "c:\windows\softwaredistribution" folder

    4) Start the AU service again.

    5) Go to a CMD prompt and type "wuauclt.exe /resetauthorization /detectnow"

    6) Check the log in about 5 minutes and see what happens

    If you are still getting the same error repeat steps 1-4 then go to the windows update site and let it download the necessary files to view the site properly. Afterwards restart the pc and do steps 5-6.

    Friday, February 27, 2009 4:21 PM
  • Matagorda said:

    I dont know what answers you would want. The server that the WSUS is on is called AVG. I admit I have no clue what I am doing and cant seem to find much information that helps. All I did was follow the step by step installation guide based on the 2003 server install. Its up and running on the server but no clients will talk to it. They all show the same error message.


    To that end, I would direct you to the WSUS Deployment Guide (125pp) and the WSUS Operations Guide (151pp) -- which covers just about everything you could ever want to know about WSUS, and then some.

    Also, you'll likely want to acquire the Client Diagnostic Tool which should help us to diagnose your connectivity issues -- most likely, as noted, an incorrect URL to the WSUS Server -- run the tool and post the results.
    Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Saturday, February 28, 2009 3:31 PM
    Moderator
  • drivenbywhat said:

    That error seems familiar but it's been so long I've forgotten what caused it or its solution. However, I wouldn't post without giving you some feedback. Here are two ways I usually fix any errors with pcs having problems updating:

    1) On pc with error stop the automatic updates service

    2) Clear the log so you won't have to scroll through many errors

    3) Delete the "c:\windows\softwaredistribution" folder

    4) Start the AU service again.

    5) Go to a CMD prompt and type "wuauclt.exe /resetauthorization /detectnow"

    6) Check the log in about 5 minutes and see what happens

    If you are still getting the same error repeat steps 1-4 then go to the windows update site and let it download the necessary files to view the site properly. Afterwards restart the pc and do steps 5-6.




    DO NOT DELETE THIS FOLDER -- unless you have a SPECIFIC REASON to do so that is only repairable by deleting this folder tree -- so far, in the past four years, I've counted on only one hand the number of scenarios that actually required the removal of this folder tree.

    Furthermore, since we've already diagnosed an HTTP 400 error, none of the above will really make any difference at all until the correct URL is identified and configured -- except to generate more HTTP 400 errors.


    Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Saturday, February 28, 2009 3:34 PM
    Moderator
  • It may be an issue with your IIS configuration.
    Review your IIS logs to determine which return codes are being posted when connections are being made to the /SimpleAuthWebService/ URL.

    To get the location of your log files:
    1) Open IIS, Right-Click the Default Web Site and select Properties.
    2) Under the Web Site tab, Enable logging shoudl be checked, click the Properties button.
    3) In the Logging Properties dialog, in the bottom box, the path to your IIS log files will be displayed. Nortmally C:\Windows\System32\LogFiles.
    4) Go the above path %path%\W3SVC\ and open the most recent log file.

    Each line should reference a date, time, action, site accessed and then a return code:

    Example:
    2009-02-27 16:01:48 W3SVC1 192.168.123.18 POST /SimpleAuthWebService/SimpleAuth.asmx - 80 - 192.168.123.18 Windows-Update-Agent 403 2 0

    The return code in the above line is a 403.2 error code.
    What codes are you seeing? A list of IIS error codes is described in this article: http://support.microsoft.com/kb/318380


    One other thing: When you open up IIS, do you see a SelfUpdate virtual directory?
    Monday, March 02, 2009 8:39 PM
  • First off I know ZERO about IIS and it doesnt help that IIS isnt included in any of their current training curriculem.

    Whats happening is when I tried to go to the site that is listed in the error log of http://avg I get something different. I think the server I am using has some sort of hardware diagnostics software that is web accessible which is blocking the WSUS information. I went back into the WSUS installation and found that it installed on some other port so I went and reconfigured the policy to include this port number and now its picking up the computers. Now if Microsoft would include a group policy that would force computers to restart at certain times I would be all set.
    Wednesday, March 04, 2009 5:40 PM