locked
Wsus issues... RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi everyone, i have a problem with my WSUS Server, all my windows 7 and vista cant find the updates from Wsus, but in the screen of my Wsus Software they appear like they already updated, even with the actual date.....i have Wsus 3.0 SP2 installed on a W2k3 32 Bits. So whats is wrong with my WSUS ? The XP machines works fine...thanks for the help.
    Wednesday, June 27, 2012 2:17 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    If the diagnostic tool reports that there is a proxy error, then that means your client systems

    • ARE being routed through a proxy and that proxy is blocking access, or
    • they're configured to use a proxy server and that proxy server doesn't exist, or
    • they're not being routed through a proxy and they NEED to be routed through that proxy correctly.

    The first thing to determine is whether the client is configured to use a proxy server (and maybe should not be).

    On Windows Vista and Windows 7 systems, run the command netsh winhttp show proxy and post the results here.

    [Added 7/17] -or-, if the diagnostic tool reports the proxy error ONLY on the Content resource, then that would indicate that the Directory Browsing role service of the Web Server role on the WSUS server has been enabled. The Directory Browsing role service is not required for a WSUS server, and it should be disabled. If you cannot disable it due to other applications, then you'll have to make accomodations for this proxy error, which is normal in that case, as the /Content v-dir is returning an HTTP 403.14 (Directory Browsing not permitted) error when the Diagnostic Tool tests for the existence of that v-dir.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin


    • Marked as answer by Clarence Zhang Tuesday, July 10, 2012 2:25 AM
    • Edited by Lawrence Garvin Tuesday, July 17, 2012 5:51 PM Added exception concerning Directory Browsing role service
    Sunday, July 1, 2012 8:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    ==OR==

    2012-07-06    13:19:07:531    1204    13d4    Misc    ===========  Logging initialized (build: 7.6.7600.256, tz: -0400)  ===========

    2012-07-06    13:19:25:232    1204    12e0    Misc    WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe are not trusted: Error 0x800b0001

    The Windows Update Agent on the client has been updated to v7.6.7600.256 and you've not yet installed KB2720211 to the WSUS server. Install KB2720211!

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Saturday, July 7, 2012 7:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    i run this tool and i get this msg error:

    content  |  Error: Forbidden |  Incorrect proxy client configuration - use settings tab to test proxy configuration settings; may also be caused by misconfigured SSL implemetation or access rights on WSUS Server

    I dont have a proxy configuration or any kind of proxy...so what could it be the problem?

    I just identified one (unexpected) cause of this particular message.

    In a typical WSUS/IIS installation, the Directory Browsing role service on IIS7 is not enabled. As such, when you test a v-dir URL that has no returnable content, such as the ~/content v-dir on WSUS, IIS just returns an HTTP 200 and a blank response.

    However if you enable the Directory Browsing role service, and then try to access the same resource, IIS returns an HTTP 403.14 result code -- because there is a directory, but browsing is not enabled for that v-dir.

    The resolution for this is NOT to enable Directory Browsing!!!

    The resolution is to confirm that you have a justified reason for having the Directory Browsing role service enabled -- and if not, to disable it.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    • Proposed as answer by antwesor Friday, July 13, 2012 4:22 PM
    • Marked as answer by Lawrence Garvin Tuesday, July 17, 2012 5:48 PM
    Thursday, July 12, 2012 4:53 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi everyone, i have a problem with my WSUS Server, all my windows 7 and vista cant find the updates from Wsus, but in the screen of my Wsus Software they appear like they already updated, even with the actual date.....i have Wsus 3.0 SP2 installed on a W2k3 32 Bits. So whats is wrong with my WSUS ? The XP machines works fine...thanks for the help.

    Check out the new Diagnostic tool for WSUS Agent from Solarwinds. NOTE : I do NOT work for Solarwinds.

    http://www.solarwinds.com/resources/videos/free-solarwinds-diagnostic-tool-for-the-wsus-agent.html?CMP=EMC-DCE-SWI-FT_DRIP_WSUS_EDUCATION-WSUS-VID&elq=e39269f80ee844559775133126bc02fd

    Running this on one of the Windows 7 or Widows Vista clients should help.




    • Edited by antwesor Friday, July 6, 2012 3:27 PM
    Wednesday, June 27, 2012 3:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    U really DONT ? :P ahaha thanks i run this tool and i get this msg error:

    content  |  Error: Forbidden |  Incorrect proxy client configuration - use settings tab to test proxy configuration settings; may also be caused by misconfigured SSL implemetation or access rights on WSUS Server

    I dont have a proxy configuration or any kind of proxy...so what could it be the problem?

    Wednesday, June 27, 2012 3:40 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    U really DONT ? :P ahaha thanks i run this tool and i get this msg error:

    content  |  Error: Forbidden |  Incorrect proxy client configuration - use settings tab to test proxy configuration settings; may also be caused by misconfigured SSL implemetation or access rights on WSUS Server

    I dont have a proxy configuration or any kind of proxy...so what could it be the problem?


    I am having the same issue, there are five updates showing as needed and all are approved for install but the client will not download them from the server. The Solarwinds tool is showing the same error message as above.
    Wednesday, June 27, 2012 3:54 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    If the diagnostic tool reports that there is a proxy error, then that means your client systems

    • ARE being routed through a proxy and that proxy is blocking access, or
    • they're configured to use a proxy server and that proxy server doesn't exist, or
    • they're not being routed through a proxy and they NEED to be routed through that proxy correctly.

    The first thing to determine is whether the client is configured to use a proxy server (and maybe should not be).

    On Windows Vista and Windows 7 systems, run the command netsh winhttp show proxy and post the results here.

    [Added 7/17] -or-, if the diagnostic tool reports the proxy error ONLY on the Content resource, then that would indicate that the Directory Browsing role service of the Web Server role on the WSUS server has been enabled. The Directory Browsing role service is not required for a WSUS server, and it should be disabled. If you cannot disable it due to other applications, then you'll have to make accomodations for this proxy error, which is normal in that case, as the /Content v-dir is returning an HTTP 403.14 (Directory Browsing not permitted) error when the Diagnostic Tool tests for the existence of that v-dir.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin


    • Marked as answer by Clarence Zhang Tuesday, July 10, 2012 2:25 AM
    • Edited by Lawrence Garvin Tuesday, July 17, 2012 5:51 PM Added exception concerning Directory Browsing role service
    Sunday, July 1, 2012 8:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I did get the same error with the client tool and netsh result from client device is

    C:>netsh winhttp show proxy

    Current WinHTTP proxy settings:

     Direct access  (no proxy server).

    I have checked the IE settings also. Is there something else we need to check?

    Thanks

    Note: I dont see any issues on this client device for checking or downloading updates from the wsus. But the tool returns this error.(i am evaluating this tool to use it on other clients). Is this something i can ignore?

    
    

    
    Thursday, July 5, 2012 4:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    So, I make three observations:

    • Clients cannot communicate with the WSUS server.
    • The Diagnostic Tool says there is an incorrect proxy configuration.
    • The netsh winhttp tells us there is no proxy configuration.

    That pretty much leaves us with two possibilities:

    • There should be a proxy server (there IS a proxy server) and it's not configured
    • The URL for the WSUS server is not correct.

    The real question now is to inspect what one of these Windows 7 systems is actually doing. Please do the following:

    1. Record the system time.
    2. Reboot the machine.
    3. After restart, run this command: wuauclt /resetauthorization /detectnow.
    4. Wait 30 minutes.
    5. Post the entries from the WindowsUpdate.log starting at the time recorded in Step #1.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Thursday, July 5, 2012 8:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for the quick response.

    ================WINDOWSUPDATE.LOG====================================================

    Reboot time : 13:17

    executed command @13:19

    wuauclt /resetauthorization /detectnow

    collected logs @ 13:49

    2012-07-06    13:19:07:531    1204    13d4    Misc    ===========  Logging initialized (build: 7.6.7600.256, tz: -0400)  ===========
    2012-07-06    13:19:08:509    1204    13d4    Misc      = Process: C:\Windows\system32\svchost.exe
    2012-07-06    13:19:08:583    1204    13d4    Misc      = Module: c:\windows\system32\wuaueng.dll
    2012-07-06    13:19:07:531    1204    13d4    Service    *************
    2012-07-06    13:19:11:078    1204    13d4    Service    ** START **  Service: Service startup
    2012-07-06    13:19:13:910    1204    13d4    Service    *********
    2012-07-06    13:19:16:901    1204    13d4    Agent      * WU client version 7.6.7600.256
    2012-07-06    13:19:17:021    1204    13d4    Agent      * Base directory: C:\Windows\SoftwareDistribution
    2012-07-06    13:19:17:072    1204    13d4    Agent      * Access type: No proxy
    2012-07-06    13:19:17:725    1204    13d4    Agent      * Network state: Connected
    2012-07-06    13:19:18:855    1204    664    Report    CWERReporter::Init succeeded
    2012-07-06    13:19:18:855    1204    664    Agent    ***********  Agent: Initializing Windows Update Agent  ***********
    2012-07-06    13:19:18:868    1204    664    Agent    ***********  Agent: Initializing global settings cache  ***********
    2012-07-06    13:19:18:868    1204    664    Agent      * WSUS server: http://10.20.2.1:80
    2012-07-06    13:19:18:868    1204    664    Agent      * WSUS status server: http://10.20.2.1:80
    2012-07-06    13:19:18:868    1204    664    Agent      * Target group: (Unassigned Computers)
    2012-07-06    13:19:18:868    1204    664    Agent      * Windows Update access disabled: No
    2012-07-06    13:19:18:883    1204    664    DnldMgr    Download manager restoring 0 downloads
    2012-07-06    13:19:18:885    1204    664    AU    ###########  AU: Initializing Automatic Updates  ###########
    2012-07-06    13:19:18:907    1204    664    AU      # WSUS server: http://10.20.2.1:80
    2012-07-06    13:19:18:907    1204    664    AU      # Detection frequency: 22
    2012-07-06    13:19:18:907    1204    664    AU      # Approval type: Pre-download notify (Policy)
    2012-07-06    13:19:19:638    1204    13d4    Setup    Service restarting after SelfUpdate
    2012-07-06    13:19:19:784    1204    664    Report    ***********  Report: Initializing static reporting data  ***********
    2012-07-06    13:19:20:245    1204    664    Report      * OS Version = 6.1.7600.0.0.65792
    2012-07-06    13:19:20:245    1204    664    Report      * OS Product Type = 0x00000004
    2012-07-06    13:19:20:444    1204    664    Report      * Computer Brand = Hewlett-Packard
    2012-07-06    13:19:20:445    1204    664    Report      * Computer Model = HP Compaq 6000 Pro MT PC
    2012-07-06    13:19:20:472    1204    664    Report      * Bios Revision = 786G2 v01.09
    2012-07-06    13:19:20:472    1204    664    Report      * Bios Name = Default System BIOS
    2012-07-06    13:19:20:472    1204    664    Report      * Bios Release Date = 2009-08-25T00:00:00
    2012-07-06    13:19:20:472    1204    664    Report      * Locale ID = 1033
    2012-07-06    13:19:20:532    1204    13d4    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2012-07-06    13:19:20:533    1204    664    AU    Successfully wrote event for AU health state:0
    2012-07-06    13:19:20:691    1204    664    AU    Initializing featured updates
    2012-07-06    13:19:20:707    1204    664    AU    Found 0 cached featured updates
    2012-07-06    13:19:20:708    1204    664    AU    Successfully wrote event for AU health state:0
    2012-07-06    13:19:20:712    1204    664    AU    Successfully wrote event for AU health state:0
    2012-07-06    13:19:20:712    1204    664    AU    AU finished delayed initialization
    2012-07-06    13:19:20:712    1204    664    AU    Triggering AU detection through DetectNow API
    2012-07-06    13:19:20:712    1204    664    AU    Triggering Online detection (non-interactive)
    2012-07-06    13:19:20:816    1204    13d4    AU    #############
    2012-07-06    13:19:20:816    1204    13d4    AU    ## START ##  AU: Search for updates
    2012-07-06    13:19:20:816    1204    13d4    AU    #########
    2012-07-06    13:19:20:856    1204    13d4    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {D4AD82F8-0C99-4FC7-9F6B-ABE2E4BB4338}]
    2012-07-06    13:19:21:618    1204    12e0    Agent    *************
    2012-07-06    13:19:21:618    1204    12e0    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-07-06    13:19:21:618    1204    12e0    Agent    *********
    2012-07-06    13:19:21:618    1204    12e0    Agent      * Online = Yes; Ignore download priority = No
    2012-07-06    13:19:21:618    1204    12e0    Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2012-07-06    13:19:21:618    1204    12e0    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2012-07-06    13:19:21:618    1204    12e0    Agent      * Search Scope = {Machine}
    2012-07-06    13:19:21:619    1204    12e0    Setup    Checking for agent SelfUpdate
    2012-07-06    13:19:21:619    1204    12e0    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2012-07-06    13:19:21:653    1204    12e0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2012-07-06    13:19:21:707    1204    12e0    Misc     Microsoft signed: Yes
    2012-07-06    13:19:24:855    1204    12e0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2012-07-06    13:19:24:859    1204    12e0    Misc     Microsoft signed: Yes
    2012-07-06    13:19:24:884    1204    12e0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2012-07-06    13:19:24:919    1204    12e0    Misc     Microsoft signed: Yes
    2012-07-06    13:19:25:011    1204    12e0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2012-07-06    13:19:25:017    1204    12e0    Misc     Microsoft signed: Yes
    2012-07-06    13:19:25:100    1204    12e0    Setup    Determining whether a new setup handler needs to be downloaded
    2012-07-06    13:19:25:226    1204    12e0    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
    2012-07-06    13:19:25:232    1204    12e0    Misc     Microsoft signed: Yes
    2012-07-06    13:19:25:232    1204    12e0    Misc    WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe are not trusted: Error 0x800b0001
    2012-07-06    13:19:25:232    1204    12e0    Setup    WARNING: Trust verification failed for WuSetupV.exe. It will be deleted and downloaded, error = 0x800B0001
    2012-07-06    13:19:25:232    1204    12e0    Setup    SelfUpdate handler update required: Current version: 7.6.7600.256, required version: 7.6.7600.256
    2012-07-06    13:19:25:232    1204    12e0    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
    2012-07-06    13:19:26:998    1204    12e0    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2012-07-06    13:19:26:998    1204    12e0    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2012-07-06    13:19:27:239    1204    12e0    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2012-07-06    13:19:27:239    1204    12e0    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2012-07-06    13:19:27:636    1204    12e0    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2012-07-06    13:19:27:638    1204    12e0    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
    2012-07-06    13:19:32:531    1204    12e0    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2012-07-06    13:19:32:531    1204    12e0    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://10.20.2.1:80/ClientWebService/client.asmx
    2012-07-06    13:19:32:562    1204    12e0    PT    WARNING: Cached cookie has expired or new PID is available
    2012-07-06    13:19:32:563    1204    12e0    PT    Initializing simple targeting cookie, clientId = 1693765575, target group = , DNS name = jmclean-w7.office.ABCInc.com
    2012-07-06    13:19:32:563    1204    12e0    PT      Server URL = http://10.20.2.1:80/SimpleAuthWebService/SimpleAuth.asmx
    2012-07-06    13:19:57:455    1204    12e0    Agent    WARNING: Failed to evaluate Installed rule, updateId = {189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB}.101, hr = 80242013
    2012-07-06    13:20:05:037    1204    12e0    PT    +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2012-07-06    13:20:05:037    1204    12e0    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://10.20.2.1:80/ClientWebService/client.asmx
    2012-07-06    13:20:06:046    1204    12e0    Agent      * Found 0 updates and 76 categories in search; evaluated appl. rules of 1938 out of 5358 deployed entities
    2012-07-06    13:20:06:089    1204    12e0    Agent    *********
    2012-07-06    13:20:06:089    1204    12e0    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-07-06    13:20:06:089    1204    12e0    Agent    *************
    2012-07-06    13:20:06:118    1204    11a4    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {D4AD82F8-0C99-4FC7-9F6B-ABE2E4BB4338}]
    2012-07-06    13:20:06:118    1204    11a4    AU      # 0 updates detected
    2012-07-06    13:20:06:119    1204    11a4    AU    #########
    2012-07-06    13:20:06:119    1204    11a4    AU    ##  END  ##  AU: Search for updates [CallId = {D4AD82F8-0C99-4FC7-9F6B-ABE2E4BB4338}]
    2012-07-06    13:20:06:119    1204    11a4    AU    #############
    2012-07-06    13:20:06:120    1204    11a4    AU    Successfully wrote event for AU health state:0
    2012-07-06    13:20:06:120    1204    11a4    AU    Featured notifications is disabled.
    2012-07-06    13:20:06:120    1204    11a4    AU    AU setting next detection timeout to 2012-07-07 11:25:24
    2012-07-06    13:20:06:121    1204    11a4    AU    Successfully wrote event for AU health state:0
    2012-07-06    13:20:06:123    1204    11a4    AU    Successfully wrote event for AU health state:0
    2012-07-06    13:20:06:135    1204    12e0    Report    REPORT EVENT: {6C3A427D-B783-42F2-9C38-E8799DDF2362}    2012-07-06 13:19:20:811-0400    1    199    101    {0011B9ED-9189-4D58-BE25-FA2F13FC3D6C}    1    240005    SelfUpdate    Success    Content Install    Installation successful and restart required for the following update: Windows Update Aux
    2012-07-06    13:20:06:189    1204    12e0    Report    CWERReporter finishing event handling. (00000000)
    2012-07-06    13:20:12:125    1204    12e0    Report    REPORT EVENT: {679F1BFE-63A8-4E00-A14C-55349B6ABBDF}    2012-07-06 13:20:06:088-0400    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
    2012-07-06    13:20:12:125    1204    12e0    Report    REPORT EVENT: {8946394C-9D26-43B3-937D-F70A360D80B3}    2012-07-06 13:20:06:088-0400    1    156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting client status.
    2012-07-06    13:20:12:126    1204    12e0    Report    CWERReporter finishing event handling. (00000000)
    2012-07-06    13:35:42:841    1204    12e0    Report    Uploading 3 events using cached cookie, reporting URL = http://10.20.2.1:80/ReportingWebService/ReportingWebService.asmx
    2012-07-06    13:35:43:218    1204    12e0    Report    Reporter successfully uploaded 3 events.
    ==============================================================================

    executed the diagnostic tool again

    ==================================================

    # Solarwinds® Diagnostic Tool for the WSUS Agent
    # 7/6/2012
    Machine state
      User rights:                                       User has administrator rights
      Update service status:                             Running
      Background Intelligent Transfer service status:    Running
      OS Version:                                        Windows 7 Enterprise
      Windows update agent version:                      7.6.7600.256 (WU Agent is OK)
    Windows Update Agent configuration settings
      Automatic Update:                                  Enabled
      Options:                                           Notify before download and installation
      Use WSUS Server:                                   Enabled
      Windows Update Server:                             http://10.20.2.1:80
      Windows Update Status Server:                      http://10.20.2.1:80
      WSUS URLs are identical:                           Identical
      WSUS URL is valid:                                 Valid URL
    WSUS Server Connectivity
      clientwebservice/client.asmx:                      OK
      simpleauthwebservice/simpleauth.asmx:              OK
      content:                                           Error: Forbidden (Incorrect proxy client configuration - use settings tab to test proxy configuration settings; may also be caused by misconfigured SSL implementation or access rights on WSUS server)
      selfupdate/iuident.cab:                            OK
      iuident.cab:                                       OK
    ========================================================================================

    Will you be able to provide the details of what the tool is checking for "content"? (with default wsus installation the directory browsing is not enabled in the IIS server for the contents folder)

    Thanks

    Friday, July 6, 2012 6:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    ==OR==

    2012-07-06    13:19:07:531    1204    13d4    Misc    ===========  Logging initialized (build: 7.6.7600.256, tz: -0400)  ===========

    2012-07-06    13:19:25:232    1204    12e0    Misc    WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe are not trusted: Error 0x800b0001

    The Windows Update Agent on the client has been updated to v7.6.7600.256 and you've not yet installed KB2720211 to the WSUS server. Install KB2720211!

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Saturday, July 7, 2012 7:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    content:  Error: Forbidden (Incorrect proxy client configuration - use settings tab to test proxy configuration settings; may also be caused by misconfigured SSL implementation or access rights on WSUS server)

    I don't think this is related to the WUAgent v7.6 and KB2720211 issue, but it is possible that this scenario is causing this failure reading from the /content store. I saw this message one other time on one my own systems, before this update was a factor, which I also at that time knew to be a false indication -- well false in that nothing was actually dysfunctional on my system -- but maybe true in terms of how the analysis logic is written inside the tool.

    Let's get your WSUS server updated and see if this message persists. If it does, then I'll ask you to take that issue over to the SolarWinds Thwack forums where we have a forum dedicated to this tool. In the meantime, I'll take another look at my systems and see if I can reproduce it.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Saturday, July 7, 2012 7:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    after installing the KB 2720211 the "not trusted" issue got fixed. thank you

    2012-07-10    10:21:58:464    1320    10ec    Misc    ===========  Logging initialized (build: 7.6.7600.256, tz: -0400)  ===========
    2012-07-10    10:21:58:514    1320    10ec    Misc      = Process: C:\Windows\system32\svchost.exe
    2012-07-10    10:21:58:563    1320    10ec    Misc      = Module: c:\windows\system32\wuaueng.dll
    2012-07-10    10:21:58:464    1320    10ec    Service    *************
    2012-07-10    10:21:58:663    1320    10ec    Service    ** START **  Service: Service startup
    2012-07-10    10:21:58:763    1320    10ec    Service    *********
    2012-07-10    10:21:59:027    1320    10ec    Agent      * WU client version 7.6.7600.256
    2012-07-10    10:21:59:077    1320    10ec    Agent      * Base directory: C:\Windows\SoftwareDistribution
    2012-07-10    10:21:59:579    1320    10ec    Agent      * Access type: No proxy
    2012-07-10    10:21:59:745    1320    10ec    Agent      * Network state: Connected
    2012-07-10    10:22:27:139    1320    9f0    Report    CWERReporter::Init succeeded
    2012-07-10    10:22:27:139    1320    9f0    Agent    ***********  Agent: Initializing Windows Update Agent  ***********
    2012-07-10    10:22:27:139    1320    9f0    Agent    ***********  Agent: Initializing global settings cache  ***********
    2012-07-10    10:22:27:139    1320    9f0    Agent      * WSUS server: http://10.20.2.1:80
    2012-07-10    10:22:27:139    1320    9f0    Agent      * WSUS status server: http://10.20.2.1:80
    2012-07-10    10:22:27:139    1320    9f0    Agent      * Target group: (Unassigned Computers)
    2012-07-10    10:22:27:140    1320    9f0    Agent      * Windows Update access disabled: No
    2012-07-10    10:22:27:160    1320    9f0    DnldMgr    Download manager restoring 0 downloads
    2012-07-10    10:22:27:174    1320    9f0    AU    ###########  AU: Initializing Automatic Updates  ###########
    2012-07-10    10:22:27:175    1320    9f0    AU      # WSUS server: http://10.20.2.1:80
    2012-07-10    10:22:27:175    1320    9f0    AU      # Detection frequency: 22
    2012-07-10    10:22:27:175    1320    9f0    AU      # Approval type: Pre-download notify (Policy)
    2012-07-10    10:22:27:627    1320    10ec    Report    ***********  Report: Initializing static reporting data  ***********
    2012-07-10    10:22:27:627    1320    10ec    Report      * OS Version = 6.1.7600.0.0.65792
    2012-07-10    10:22:27:627    1320    10ec    Report      * OS Product Type = 0x00000004
    2012-07-10    10:22:27:669    1320    10ec    Report      * Computer Brand = Hewlett-Packard
    2012-07-10    10:22:27:669    1320    10ec    Report      * Computer Model = HP Compaq 6000 Pro MT PC
    2012-07-10    10:22:27:702    1320    10ec    Report      * Bios Revision = 786G2 v01.09
    2012-07-10    10:22:27:702    1320    10ec    Report      * Bios Name = Default System BIOS
    2012-07-10    10:22:27:702    1320    10ec    Report      * Bios Release Date = 2009-08-25T00:00:00
    2012-07-10    10:22:27:702    1320    10ec    Report      * Locale ID = 1033
    2012-07-10    10:22:27:728    1320    9f0    AU    Successfully wrote event for AU health state:0
    2012-07-10    10:22:27:728    1320    9f0    AU    Initializing featured updates
    2012-07-10    10:22:27:728    1320    9f0    AU    Found 0 cached featured updates
    2012-07-10    10:22:27:728    1320    9f0    AU    Successfully wrote event for AU health state:0
    2012-07-10    10:22:27:730    1320    9f0    AU    Successfully wrote event for AU health state:0
    2012-07-10    10:22:27:730    1320    9f0    AU    AU finished delayed initialization
    2012-07-10    10:22:27:731    1320    9f0    AU    Triggering AU detection through DetectNow API
    2012-07-10    10:22:27:731    1320    9f0    AU    Triggering Online detection (non-interactive)
    2012-07-10    10:22:27:731    1320    10ec    AU    #############
    2012-07-10    10:22:27:731    1320    10ec    AU    ## START ##  AU: Search for updates
    2012-07-10    10:22:27:731    1320    10ec    AU    #########
    2012-07-10    10:22:27:733    1320    10ec    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {803CD32A-9DB5-4200-B390-794466068E25}]
    2012-07-10    10:22:28:064    1320    620    Agent    *************
    2012-07-10    10:22:28:064    1320    620    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-07-10    10:22:28:064    1320    620    Agent    *********
    2012-07-10    10:22:28:064    1320    620    Agent      * Online = Yes; Ignore download priority = No
    2012-07-10    10:22:28:064    1320    620    Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2012-07-10    10:22:28:064    1320    620    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2012-07-10    10:22:28:064    1320    620    Agent      * Search Scope = {Machine}
    2012-07-10    10:22:28:064    1320    620    Setup    Checking for agent SelfUpdate
    2012-07-10    10:22:28:065    1320    620    Setup    Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2012-07-10    10:22:28:074    1320    620    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2012-07-10    10:22:28:105    1320    620    Misc     Microsoft signed: Yes
    2012-07-10    10:22:30:659    1320    620    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2012-07-10    10:22:30:663    1320    620    Misc     Microsoft signed: Yes
    2012-07-10    10:22:30:700    1320    620    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2012-07-10    10:22:30:721    1320    620    Misc     Microsoft signed: Yes
    2012-07-10    10:22:30:803    1320    620    Misc    Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2012-07-10    10:22:30:808    1320    620    Misc     Microsoft signed: Yes
    2012-07-10    10:22:30:862    1320    620    Setup    Determining whether a new setup handler needs to be downloaded
    2012-07-10    10:22:30:862    1320    620    Setup    SelfUpdate handler is not found.  It will be downloaded
    2012-07-10    10:22:30:862    1320    620    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256"
    2012-07-10    10:22:32:139    1320    620    Setup    Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2012-07-10    10:22:32:139    1320    620    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2012-07-10    10:22:32:159    1320    620    Setup    Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2012-07-10    10:22:32:159    1320    620    Setup    Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256"
    2012-07-10    10:22:32:187    1320    620    Setup    Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.256" is already installed.
    2012-07-10    10:22:32:188    1320    620    Setup    SelfUpdate check completed.  SelfUpdate is NOT required.
    2012-07-10    10:22:34:668    1320    620    PT    +++++++++++  PT: Synchronizing server updates  +++++++++++
    2012-07-10    10:22:34:668    1320    620    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://10.20.2.1:80/ClientWebService/client.asmx
    2012-07-10    10:22:34:688    1320    620    PT    WARNING: Cached cookie has expired or new PID is available
    2012-07-10    10:22:34:688    1320    620    PT    Initializing simple targeting cookie, clientId = 1693765575, target group = , DNS name = jmclean-w7.office.ABCInc.com
    2012-07-10    10:22:34:688    1320    620    PT      Server URL = http://10.20.2.1:80/SimpleAuthWebService/SimpleAuth.asmx
    2012-07-10    10:22:34:936    1320    620    PT    WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2012-07-10    10:22:34:936    1320    620    PT    WARNING: SOAP Fault: 0x00012c
    2012-07-10    10:22:34:936    1320    620    PT    WARNING:     faultstring:Fault occurred
    2012-07-10    10:22:34:936    1320    620    PT    WARNING:     ErrorCode:ConfigChanged(2)
    2012-07-10    10:22:34:936    1320    620    PT    WARNING:     Message:(null)
    2012-07-10    10:22:34:936    1320    620    PT    WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
    2012-07-10    10:22:34:936    1320    620    PT    WARNING:     ID:44e1c560-aba9-421e-b55c-6d51c175d652
    2012-07-10    10:22:35:058    1320    620    PT    WARNING: Cached cookie has expired or new PID is available
    2012-07-10    10:22:35:058    1320    620    PT    Initializing simple targeting cookie, clientId = 1693765575, target group = , DNS name = jmclean-w7.office.ABCInc.com
    2012-07-10    10:22:35:058    1320    620    PT      Server URL = http://10.20.2.1:80/SimpleAuthWebService/SimpleAuth.asmx
    2012-07-10    10:22:48:188    1320    620    Agent    WARNING: Failed to evaluate Installed rule, updateId = {189A8F50-0C3A-4FDF-8BC2-BC23A3EB11FB}.101, hr = 80242013
    2012-07-10    10:22:52:369    1320    620    PT    +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2012-07-10    10:22:52:370    1320    620    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://10.20.2.1:80/ClientWebService/client.asmx
    2012-07-10    10:22:53:348    1320    620    Agent      * Found 0 updates and 76 categories in search; evaluated appl. rules of 1936 out of 5454 deployed entities
    2012-07-10    10:22:53:365    1320    620    Agent    *********
    2012-07-10    10:22:53:365    1320    620    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-07-10    10:22:53:365    1320    620    Agent    *************
    2012-07-10    10:22:53:389    1320    828    AU    >>##  RESUMED  ## AU: Search for updates [CallId = {803CD32A-9DB5-4200-B390-794466068E25}]
    2012-07-10    10:22:53:389    1320    828    AU      # 0 updates detected
    2012-07-10    10:22:53:390    1320    828    AU    #########
    2012-07-10    10:22:53:390    1320    828    AU    ##  END  ##  AU: Search for updates [CallId = {803CD32A-9DB5-4200-B390-794466068E25}]
    2012-07-10    10:22:53:390    1320    828    AU    #############
    2012-07-10    10:22:53:391    1320    828    AU    Successfully wrote event for AU health state:0
    2012-07-10    10:22:53:391    1320    828    AU    Featured notifications is disabled.
    2012-07-10    10:22:53:392    1320    828    AU    AU setting next detection timeout to 2012-07-11 09:11:35
    2012-07-10    10:22:53:392    1320    828    AU    Successfully wrote event for AU health state:0
    2012-07-10    10:22:53:393    1320    828    AU    Successfully wrote event for AU health state:0
    2012-07-10    10:22:53:418    1320    620    Report    CWERReporter finishing event handling. (00000000)
    2012-07-10    10:22:58:384    1320    620    Report    REPORT EVENT: {05913828-23BD-48A1-ACF7-02AEA2823DAE}    2012-07-10 10:22:53:364-0400    1    147    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Software Synchronization    Windows Update Client successfully detected 0 updates.
    2012-07-10    10:22:58:384    1320    620    Report    REPORT EVENT: {ED05D21F-44A1-4175-8CB0-7A5071A23079}    2012-07-10 10:22:53:364-0400    1    156    101    {00000000-0000-0000-0000-000000000000}    0    0    AutomaticUpdates    Success    Pre-Deployment Check    Reporting client status.
    2012-07-10    10:22:58:387    1320    620    Report    CWERReporter finishing event handling. (00000000)

    Tuesday, July 10, 2012 2:33 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You are right. The KB doesnt have any impact on this, but its something to do with the "directory browsing" settings.

    I have enabled the directory browsing on  contents folder and i verified the "http://localhost/Content/" availability and then ran the report. The result is all success. Please see the results below.

    Now my question is, what is the expected setting on this folder? the settings were untouched since the install of WSUS and now i have enabled it. Does it have any impact on functionality? (i didnt see any issue)

    # Solarwinds® Diagnostic Tool for the WSUS Agent
    # 7/10/2012
    Machine state
      User rights:                                       User has administrator rights
      Update service status:                             Running
      Background Intelligent Transfer service status:    Running
      OS Version:                                        Windows 7 Enterprise
      Windows update agent version:                      7.6.7600.256 (WU Agent is OK)
    Windows Update Agent configuration settings
      Automatic Update:                                  Enabled
      Options:                                           Notify before download and installation
      Use WSUS Server:                                   Enabled
      Windows Update Server:                             http://10.20.2.1:80:80
      Windows Update Status Server:                      http://10.20.2.1:80:80
      WSUS URLs are identical:                           Identical
      WSUS URL is valid:                                 Valid URL
    WSUS Server Connectivity
      clientwebservice/client.asmx:                      OK
      simpleauthwebservice/simpleauth.asmx:              OK
      content:                                           OK
      selfupdate/iuident.cab:                            OK
      iuident.cab:                                       OK

    I am going to post the results in to the Solarwinds forum also, but please clarify on the settings required for this contents folder.

    Tuesday, July 10, 2012 2:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    i run this tool and i get this msg error:

    content  |  Error: Forbidden |  Incorrect proxy client configuration - use settings tab to test proxy configuration settings; may also be caused by misconfigured SSL implemetation or access rights on WSUS Server

    I dont have a proxy configuration or any kind of proxy...so what could it be the problem?

    I just identified one (unexpected) cause of this particular message.

    In a typical WSUS/IIS installation, the Directory Browsing role service on IIS7 is not enabled. As such, when you test a v-dir URL that has no returnable content, such as the ~/content v-dir on WSUS, IIS just returns an HTTP 200 and a blank response.

    However if you enable the Directory Browsing role service, and then try to access the same resource, IIS returns an HTTP 403.14 result code -- because there is a directory, but browsing is not enabled for that v-dir.

    The resolution for this is NOT to enable Directory Browsing!!!

    The resolution is to confirm that you have a justified reason for having the Directory Browsing role service enabled -- and if not, to disable it.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    • Proposed as answer by antwesor Friday, July 13, 2012 4:22 PM
    • Marked as answer by Lawrence Garvin Tuesday, July 17, 2012 5:48 PM
    Thursday, July 12, 2012 4:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Lawrence and sorry for the late answer...i paste the results like u said to me...


    C:\Users\msifuentes>netsh winhttp show proxy

    Configuración actual del proxy WinHTTP:

        Acceso directo (sin servidor proxy).

    Monday, July 16, 2012 8:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks Lawrence and sorry for the late answer...i paste the results like u said to me...

    C:\Users\msifuentes>netsh winhttp show proxy

    Configuración actual del proxy WinHTTP:

        Acceso directo (sin servidor proxy).


    As noted above, the 'content' error you experienced in the Diagnostic Tool, in the absence of a real proxy error (which would also be flagged on the other four resource tests as well), is likely caused because the Directory Browsing role service has been enabled in the Web Server role of the WSUS server. If you do not have a specific need for the Directory Browsing role service, then you should disable it. If you do need it, then just understand that this would be a normal indication in that situation, since the /content v-dir is returning an HTTP 403.14 to the Diagnostic Tool.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Product Manager, SolarWinds
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    Tuesday, July 17, 2012 5:48 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Sorry Lawrence, it was long time ago when i post this and no one answer me, so i forget to read it all....im gonna try all the solutions that you propose and i let you know later how is working. Thank you so much.
    Friday, July 20, 2012 1:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    i got rid of the error by enabling directory browsing on the content directory

    thats on IIS 6 on Server 2003 SP2   standard edition


    • Edited by colm_sm Thursday, October 18, 2012 2:45 PM
    Thursday, October 18, 2012 2:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I also got rid of that error by enabling directory browsing in IIS7. I still have a problem updating with error 80244019.

    Tuesday, July 2, 2013 1:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    i got rid of the error by enabling directory browsing on the content directory

    thats on IIS 6 on Server 2003 SP2   standard edition

    The objective is NOT to get rid of the "Error". The "Error" is a false indication, and you SHOULD NOT (NEVER!) enable directory browsing on a website that does not explicitly require it .. most specifically not on WSUS!

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.


    Monday, July 8, 2013 1:14 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I also got rid of that error by enabling directory browsing in IIS7.

    The objective is NOT to get rid of the "Error". The "Error" is a false indication, and you SHOULD NOT (NEVER!) enable directory browsing on a website that does not explicitly require it .. most specifically not on WSUS!
    I still have a problem updating with error 80244019.
    The 0x80244019 is an HTTP 404 and it means that whatever resource the client is trying to access, is not present. Post the detection event with this 0x80244019 error code, and we'll go from there.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Monday, July 8, 2013 1:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hey Lawrence, sorry for necroing this three and a half year old thread, but I have been searching all over for a solution for the 0x80244019 update error and haven't found anything (well, I'd like to run the wsusutil reset command, but my superiors are adamant that this isn't the fix since our WSUS server was just rebuilt a few months ago, allegedly after we started having these issues. I just started working on this problem myself in the last two weeks with very limited access to the WSUS server.)

    I would greatly appreciate if we could pick up where you and that other fellow left off. Here's that detection event with the code:

    2017-01-13    12:02:34:008     912    1c40    DnldMgr    ** START **  DnldMgr: Downloading updates [CallerId = AutomaticUpdatesWuApp]
    2017-01-13    12:02:34:008     912    1c40    DnldMgr    *********
    2017-01-13    12:02:34:008     912    1c40    DnldMgr      * Call ID = {248FF739-2E7D-4DDC-A576-28A8A9491ADD}
    2017-01-13    12:02:34:008     912    1c40    DnldMgr      * Priority = 3, Interactive = 1, Owner is system = 0, Explicit proxy = 0, Proxy session id = 1, ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2017-01-13    12:02:34:008     912    1c40    DnldMgr      * Updates to download = 1
    2017-01-13    12:02:34:008     912    1c40    Agent      *   Title = Security Update for Windows 7 for x64-based Systems (KB3075226)
    2017-01-13    12:02:34:008     912    1c40    Agent      *   UpdateId = {521EC9F7-851C-44EE-93A5-30236365C011}.201
    2017-01-13    12:02:34:008     912    1c40    Agent      *     Bundles 1 updates:
    2017-01-13    12:02:34:008     912    1c40    Agent      *       {97ECA772-3B3B-44EA-A0BF-E628DA518637}.201
    2017-01-13    12:02:34:009     912    1c40    PT    +++++++++++  PT: Synchronizing file locations  +++++++++++
    2017-01-13    12:02:34:009     912    1c40    PT      + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://10.40.42.60:8530/ClientWebService/client.asmx
    2017-01-13    12:02:34:010     912    1f64    AU    Successfully wrote event for AU health state:0
    2017-01-13    12:02:34:030     912    1c40    DnldMgr    ***********  DnldMgr: New download job [UpdateId = {97ECA772-3B3B-44EA-A0BF-E628DA518637}.201]  ***********
    2017-01-13    12:02:34:031     912    1c40    DnldMgr      * Queueing update for download handler request generation.
    2017-01-13    12:02:34:031     912    1c40    DnldMgr    Generating download request for update {97ECA772-3B3B-44EA-A0BF-E628DA518637}.201
    2017-01-13    12:02:34:080     912    1c40    Handler    Generating request for CBS update 97ECA772-3B3B-44EA-A0BF-E628DA518637 in sandbox C:\Windows\SoftwareDistribution\Download\34dca3533356dd35dfa473094df68716
    2017-01-13    12:02:34:080     912    1c40    Handler    Selecting self-contained because update has express payload but server doesn't support it.
    2017-01-13    12:02:34:080     912    1c40    Handler    Selected payload type is ptSelfContained
    2017-01-13    12:02:34:080     912    1c40    Handler    Detected download state is dsStart
    2017-01-13    12:02:34:080     912    1c40    Handler    Adding windows6.1-kb3075226-x64.cab (entire file) to request list.
    2017-01-13    12:02:34:081     912    1c40    Handler    Request generation for CBS update complete with hr=0x0 and pfResetSandbox=0
    2017-01-13    12:02:34:081     912    1c40    DnldMgr    ***********  DnldMgr: New download job [UpdateId = {97ECA772-3B3B-44EA-A0BF-E628DA518637}.201]  ***********
    2017-01-13    12:02:34:150     912    1c40    DnldMgr      * BITS job initialized, JobId = {3074167E-8A25-49A7-9A6C-B64F99AFA51D}
    2017-01-13    12:02:34:196     912    1c40    DnldMgr      * Downloading from http://10.40.42.60:8530/Content/F5/766C9CCE189BDF1B626BCBEDAF1CC767A2530CF5.cab to C:\Windows\SoftwareDistribution\Download\34dca3533356dd35dfa473094df68716\windows6.1-kb3075226-x64.cab (full file).
    2017-01-13    12:02:34:303     912    1c40    Agent    *********
    2017-01-13    12:02:34:303     912    17ec    DnldMgr    WARNING: BITS job {3074167E-8A25-49A7-9A6C-B64F99AFA51D} failed, updateId = {97ECA772-3B3B-44EA-A0BF-E628DA518637}.201, hr = 0x80190194, BG_ERROR_CONTEXT = 5
    2017-01-13    12:02:34:303     912    1c40    Agent    **  END  **  Agent: Downloading updates [CallerId = AutomaticUpdatesWuApp]
    2017-01-13    12:02:34:303     912    1c40    Agent    *************
    2017-01-13    12:02:34:303     912    17ec    DnldMgr      Progress failure bytes total = 5009399, bytes transferred = 0
    2017-01-13    12:02:34:303     912    17ec    DnldMgr      Failed job file: URL = http://10.40.42.60:8530/Content/F5/766C9CCE189BDF1B626BCBEDAF1CC767A2530CF5.cab, local path = C:\Windows\SoftwareDistribution\Download\34dca3533356dd35dfa473094df68716\windows6.1-kb3075226-x64.cab
    2017-01-13    12:02:34:335     912    17ec    DnldMgr    Error 0x80244019 occurred while downloading update; notifying dependent calls.
    2017-01-13    12:02:34:342     912    1f64    AU    >>##  RESUMED  ## AU: Download update [UpdateId = {521EC9F7-851C-44EE-93A5-30236365C011}]
    2017-01-13    12:02:34:342     912    1f64    AU      # WARNING: Download failed, error = 0x80244019
    2017-01-13    12:02:34:342     912    1c40    Report    REPORT EVENT: {CFF8F832-AB79-46D4-A8DA-03B074D67D39}    2017-01-13 12:02:31:881-0500    1    161    101    {C72F0E3A-6C54-4E25-857D-63E050D34ADA}    203    80244019    AutomaticUpdatesWuApp    Failure    Content Download    Error: Download failed.
    2017-01-13    12:02:34:342     912    1f64    AU    #########
    2017-01-13    12:02:34:343     912    1f64    AU    ##  END  ##  AU: Download updates
    2017-01-13    12:02:34:343     912    1f64    AU    #############
    2017-01-13    12:02:34:343     912    1f64    AU    Setting AU scheduled install time to 2017-01-14 17:00:00
    2017-01-13    12:02:34:343     912    1f64    AU    Successfully wrote event for AU health state:0
    2017-01-13    12:02:34:343     912    1f64    AU    Currently showing Progress UX client - so not launching any other client
    2017-01-13    12:02:34:346     912    1f64    AU    Successfully wrote event for AU health state:0
    2017-01-13    12:02:34:351     912    1144    AU    Getting featured update notifications.  fIncludeDismissed = true
    2017-01-13    12:02:34:351     912    1144    AU    No featured updates available.
    2017-01-13    12:02:34:353     912    1c40    Report    CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2017-01-13    12:02:34:353     912    1c40    Report    WER Report sent: 7.6.7601.23453 0x80244019(0) 72F0E3A-6C54-4E25-857D-63E050D34ADA Download 203 0 AutomaticUpdatesWuApp {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2017-01-13    12:02:34:354     912    1c40    Report    REPORT EVENT: {EC89BE8C-C295-42DF-843A-A5E8D54A65A3}    2017-01-13 12:02:32:983-0500    1    161    101    {36451B50-3F6F-48CB-89D0-EE69FF62A67F}    201    80244019    AutomaticUpdatesWuApp    Failure    Content Download    Error: Download failed.
    2017-01-13    12:02:34:354     912    1c40    Report    REPORT EVENT: {6D80181C-8BED-40D7-8868-E281302AD521}    2017-01-13 12:02:33:368-0500    1    161    101    {F7087A7B-2458-4167-AA70-7A671AF9009B}    201    80244019    AutomaticUpdatesWuApp    Failure    Content Download    Error: Download failed.
    2017-01-13    12:02:34:354     912    1c40    Report    REPORT EVENT: {A0035194-10F3-430D-A531-592B7D49BDEC}    2017-01-13 12:02:33:648-0500    1    161    101    {24AEB988-B368-435B-923B-C09B8A2D3FA5}    203    80244019    AutomaticUpdatesWuApp    Failure    Content Download    Error: Download failed.
    2017-01-13    12:02:34:361     912    1c40    Report    CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2017-01-13    12:02:34:361     912    1c40    Report    WER Report sent: 7.6.7601.23453 0x80244019(0) 6451B50-3F6F-48CB-89D0-EE69FF62A67F Download 201 0 AutomaticUpdatesWuApp {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2017-01-13    12:02:34:370     912    1c40    Report    CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2017-01-13    12:02:34:371     912    1c40    Report    WER Report sent: 7.6.7601.23453 0x80244019(0) 7087A7B-2458-4167-AA70-7A671AF9009B Download 201 0 AutomaticUpdatesWuApp {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2017-01-13    12:02:34:380     912    1c40    Report    CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2017-01-13    12:02:34:380     912    1c40    Report    WER Report sent: 7.6.7601.23453 0x80244019(0) 4AEB988-B368-435B-923B-C09B8A2D3FA5 Download 203 0 AutomaticUpdatesWuApp {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2017-01-13    12:02:36:258     912    1ecc    AU    BeginInteractiveInstall invoked for Install with sessionId 1
    2017-01-13    12:02:36:259     912    1ecc    AU    Auto-approved 0 update(s) for install (for Ux), installType=0
    2017-01-13    12:02:36:259     912    1ecc    AU    WARNING: BeginInteractiveInstall failed, error = 0x8024000C
    2017-01-13    12:02:36:259    6868    834    CltUI    FATAL: BeginInteractiveInstall for install returned code 8024000C
    2017-01-13    12:02:36:889    6868    834    CltUI    WARNING: AU directive Interactive Progress is exiting due to error 8024000C
    2017-01-13    12:02:37:109     912    1438    AU    AU received handle event
    2017-01-13    12:02:37:109     912    1438    AU    UpdateDownloadProperties: 0 download(s) are still in progress.
    2017-01-13    12:02:37:111     912    1438    AU    Triggering Offline detection (non-interactive)
    2017-01-13    12:02:37:111     912    1438    AU    AU setting pending client directive to 'Install Complete Ux'
    2017-01-13    12:02:37:111     912    1438    AU    WARNING: Pending directive, 'Install Complete Ux', is not applicable
    2017-01-13    12:02:37:115     912    1438    AU    Successfully wrote event for AU health state:0
    2017-01-13    12:02:37:115     912    1438    AU    #############
    2017-01-13    12:02:37:115     912    1438    AU    ## START ##  AU: Search for updates
    2017-01-13    12:02:37:115     912    1438    AU    #########
    2017-01-13    12:02:37:115     912    1c40    Report    REPORT EVENT: {E90E1525-D1B7-480D-AF85-3C1573AF2FAF}    2017-01-13 12:02:34:004-0500    1    161    101    {757415A6-070E-4018-B2B7-727C3C804023}    202    80244019    AutomaticUpdatesWuApp    Failure    Content Download    Error: Download failed.
    2017-01-13    12:02:37:115     912    1c40    Report    REPORT EVENT: {8DEE7CF7-8EAC-4C12-B0AF-3D7B5CCD43B2}    2017-01-13 12:02:34:342-0500    1    161    101    {521EC9F7-851C-44EE-93A5-30236365C011}    201    80244019    AutomaticUpdatesWuApp    Failure    Content Download    Error: Download failed.
    2017-01-13    12:02:37:160     912    1438    AU    <<## SUBMITTED ## AU: Search for updates [CallId = {386D1001-B25B-4590-B181-256B5D331B07}]
    2017-01-13    12:02:37:164     912    1c40    Report    CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2017-01-13    12:02:37:164     912    1c40    Report    WER Report sent: 7.6.7601.23453 0x80244019(0) 57415A6-070E-4018-B2B7-727C3C804023 Download 202 0 AutomaticUpdatesWuApp {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2017-01-13    12:02:37:178     912    1c40    Report    CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2017-01-13    12:02:37:178     912    1c40    Report    WER Report sent: 7.6.7601.23453 0x80244019(0) 21EC9F7-851C-44EE-93A5-30236365C011 Download 201 0 AutomaticUpdatesWuApp {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2017-01-13    12:02:37:179     912    1c40    Agent    *************
    2017-01-13    12:02:37:179     912    1c40    Agent    ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2017-01-13    12:02:37:179     912    1c40    Agent    *********
    2017-01-13    12:02:37:179     912    1c40    Agent      * Online = No; Ignore download priority = No
    2017-01-13    12:02:37:179     912    1c40    Agent      * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2017-01-13    12:02:37:179     912    1c40    Agent      * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2017-01-13    12:02:37:179     912    1c40    Agent      * Search Scope = {Machine}
    2017-01-13    12:02:37:476     912    1ecc    AU    Getting featured update notifications.  fIncludeDismissed = true
    2017-01-13    12:02:37:476     912    1ecc    AU    No featured updates available.
    2017-01-13    12:02:37:496     912    1ecc    AU    WARNING: Returning due to error from GetDownloadProgressUx, error = 0x8024000C
    2017-01-13    12:02:37:496     912    1ecc    AU    WARNING: GetInteractiveInstallProgress failed, error = 0x8024000C
    2017-01-13    12:02:37:496    6972    1224    WUApp    WARNING: Call to GetInteractiveInstallProgress failed, hr=8024000C
    2017-01-13    12:03:35:410     912    1c40    Agent      * Added update {757415A6-070E-4018-B2B7-727C3C804023}.202 to search result
    2017-01-13    12:03:35:410     912    1c40    Agent      * Added update {C72F0E3A-6C54-4E25-857D-63E050D34ADA}.203 to search result
    2017-01-13    12:03:35:410     912    1c40    Agent    Update {0CC0C76A-1E06-4226-BCFD-97A042BC7B95}.202 is pruned out due to potential supersedence
    2017-01-13    12:03:35:410     912    1c40    Agent      * Added update {36451B50-3F6F-48CB-89D0-EE69FF62A67F}.201 to search result
    2017-01-13    12:03:35:410     912    1c40    Agent    Update {C00A51BA-6501-4C74-96B6-F266EC3A5722}.201 is pruned out due to potential supersedence
    2017-01-13    12:03:35:410     912    1c40    Agent    Update {B8BBA0C2-E54F-4515-8D58-C7EA28862312}.201 is pruned out due to potential supersedence
    2017-01-13    12:03:35:410     912    1c40    Agent    Update {BB2E718E-3130-480E-ACB0-690632DFD1BD}.201 is pruned out due to potential supersedence
    2017-01-13    12:03:35:410     912    1c40    Agent      * Added update {521EC9F7-851C-44EE-93A5-30236365C011}.201 to search result
    2017-01-13    12:03:35:410     912    1c40    Agent      * Added update {F7087A7B-2458-4167-AA70-7A671AF9009B}.201 to search result
    2017-01-13    12:03:35:410     912    1c40    Agent      * Added update {24AEB988-B368-435B-923B-C09B8A2D3FA5}.203 to search result
    2017-01-13    12:03:35:411     912    1c40    Agent    Update {F2DEEB13-97D0-4FC1-93FD-444CC6AB9512}.200 is pruned out due to potential supersedence
    2017-01-13    12:03:35:411     912    1c40    Agent      * Found 6 updates and 81 categories in search; evaluated appl. rules of 4159 out of 8087 deployed entities
    2017-01-13    12:03:35:459     912    1c40    Agent    *********
    2017-01-13    12:03:35:459     912    1c40    Agent    **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2017-01-13    12:03:35:459     912    1c40    Agent    *************

    Please let me know if you need anything else. Thanks in advance.

    Friday, January 13, 2017 5:46 PM