none
WSUS clients wont contact WSUS server

    Pergunta

  • Hi,

    Situation:
    - WSUS Server running on Server 2008R2 X64
    - Client: Server 2003R2, being used as Citrix Terminal server
    - Antivirus: G-Data

    Since a couple of weaks, the clients wont connect to the wsus server.

    Errorcode in logfile in one of the clients:0x8024400a, part of the logfile:

    2013-02-05	11:56:22:343	1100	4464	Report	WARNING: Reporter failed to upload events with hr = 8024400a.
    2013-02-05	12:11:36:561	1100	42f4	PT	WARNING: GetConfig failure, error = 0x8024400A, soap client error = 10, soap error code = 0, HTTP status code = 200
    2013-02-05	12:11:36:561	1100	42f4	PT	WARNING: PTError: 0x8024400a
    2013-02-05	12:11:36:561	1100	42f4	PT	WARNING: GetConfig_WithRecovery failed: 0x8024400a
    2013-02-05	12:11:36:561	1100	42f4	PT	WARNING: RefreshConfig failed: 0x8024400a
    2013-02-05	12:11:36:561	1100	42f4	PT	WARNING: RefreshPTState failed: 0x8024400a
    2013-02-05	12:11:36:561	1100	42f4	PT	WARNING: PTError: 0x8024400a

    I already dit tried the following:
    - Force reinstall WSUS agent:

    WindowsUpdateAgent30-x86.exe /wuforce
    - Stop Au service and BITS, and delete the softwaredistribution folder

    - Run the Wsus Diag tool to check for malfunctions, this comes with no error.
    - Re-register the DLL files:

    NET STOP WUAUSERV
    REGSVR32 /S WUAPI.DLL
    REGSVR32 /S WUPS.DLL
    REGSVR32 /S WUAUENG.DLL
    REGSVR32 /S WUAUENG1.DLL
    REGSVR32 /S WUCLTUI.DLL
    REGSVR32 /S WUWEB.DLL
    REGSVR32 /S JSCRIPT.DLL
    REGSVR32 /S ATL.DLL
    REGSVR32 /S SOFTPUB.DLL
    REGSVR32 /S MSXML3.DLL
    NET START WUAUSERV


    Other clients:

    - Server 2008R2
    - Windows XP SP3
    - Windows 7 SP1

    these clients connect and update correctly.



    • Editado Mr_Tre terça-feira, 5 de fevereiro de 2013 12:09
    terça-feira, 5 de fevereiro de 2013 12:07

Respostas

  • 2013-02-05 16:30:33:518 1100 5e0 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://[hostname]:80/ClientWebService/client.asmx
    2013-02-05 16:30:33:518 1100 5e0 PT WARNING: GetConfig failure,error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200

    from WSUS Technical Reference Guide: Windows Update Agent Result Codes

    0x80244008

    WU_E_PT_SOAPCLIENT_PARSEFAULT

    SOAP client failed to parse a SOAP fault.

    If I'm understanding this error correctly, it's throwing an exception trying to parse a SOAP fault.

    0x8024400A

    WU_E_PT_SOAPCLIENT_PARSE

    SOAP client failed to parse the response from the server.

    I can't help but wonder if the SOAP fault it's unable to parse is the original 0x8024400A that was observed prior to destroying the WUAgent datastore. I should also note that the 0x8024400A error message you originally reported is a very rare error code, and throughout the history of WSUS (since the release of v2 in 2005), in the few instances that I've seen 0x8024400A .. the only resolution was to rebuild the WSUS server. An actual -cause- for that error code has never been definitively identified (thus no known remediation except to reinstall).

    You said the client is a Win2003 R2 SP2 Citrix Terminal Server ...  running as a virtual machine? You've also indicated there are multiple clients not connecting. Are all of these non-connecting clients Win2003 systems? Are they all Terminal Servers? Are they all Virtual Machines? Are they all Virtual Machines on VMWare?

    2013-02-05 16:30:32:675 1100 1740 Report   * OS Version = 5.2.3790.2.0.196624
    2013-02-05 16:30:32:800 1100 1740 Report   * Computer Brand = VMware, Inc.
    2013-02-05 16:30:32:800 1100 1740 Report   * Computer Model = VMware Virtual Platform
    2013-02-05 16:30:32:800 1100 1740 Report   * Locale ID = 1043

    You've already rebuilt the client-side SoftwareDistribution folder twice, with no relief, which strongly rules out a client-side issue as well.


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

    terça-feira, 5 de fevereiro de 2013 23:17
  • All the non-connecting clients are the same server as discribed, and they are all VMware virtual machines.
    The the thing is, the wsus server is brand new. It has been installed arond december-2012 and it has replaced an server2003 based wsus server.
    Could this be a part of the issue?

    It could be, but given that all of the affected clients are all the same operating system and all VMWare virtual machines, I'm inclined to start with the possibility that you have duplicated SusClientIDs. Refer to KB903262 to clear the necessary registry values, and retry the detection. If that doesn't clear the issue, we can dig deeper.

    If i open this URL: http://[hostname]:80/ClientWebService/client.asmx
    i get an page with application errors on it. Is this normal?

    Yes. There is a limited amount of 'browsable' content on a WSUS server. Try checking these URLs:

    • http://hostname/iuident.cab
    • http://hostname/selfupdate/iuident.cab
    • http://hostname/SimpleAuthWebService/SimpleAuth.asmx

    The first two URLs should produce a File Open/Save dialog; the third URL will provide a WSDL information page.

    ALSO.... remove the :80 from your URL. It's not necessary since port 80 is the default, and I have seen the :80 suffix cause problems

    The other thing you should do is download the SolarWinds WSUS Diagnostic Tool for the WSUS Agent and run it on one of these systems and get a report on what is working and/or is not.


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

    quinta-feira, 7 de fevereiro de 2013 01:05

Todas as Respostas

  • Hello

    Please try the following:

    stop the AU service

    Backup all files and folders in the %windir%\SoftwareDistribution folder

    Delete all files and folder in the %windir%\SoftwareDistribution folder

    DO NOT delete the %windir%\SoftwareDistribution folder itself only the the files and folders within.

    start the AU service

    Run wuauclt /detectnow /resetauthorization

    Watch the progress in the %windir%\WindowsUpdate.log file


    terça-feira, 5 de fevereiro de 2013 12:46
  • Hi,

    After doing your tips, the following entry's in the logfile :

    2013-02-05	16:30:32:675	1100	13d8	Agent	***********  Agent: Initializing Windows Update Agent  ***********
    2013-02-05	16:30:32:675	1100	13d8	Agent	***********  Agent: Initializing global settings cache  ***********
    2013-02-05	16:30:32:675	1100	1740	Report	***********  Report: Initializing static reporting data  ***********
    2013-02-05	16:30:32:675	1100	13d8	Agent	  * WSUS server: http://[hostname]:80
    2013-02-05	16:30:32:675	1100	1740	Report	  * OS Version = 5.2.3790.2.0.196624
    2013-02-05	16:30:32:675	1100	13d8	Agent	  * WSUS status server: http://[hostname]:80
    2013-02-05	16:30:32:675	1100	13d8	Agent	  * Target group: (Unassigned Computers)
    2013-02-05	16:30:32:675	1100	13d8	Agent	  * Windows Update access disabled: No
    2013-02-05	16:30:32:690	1100	13d8	DnldMgr	Download manager restoring 0 downloads
    2013-02-05	16:30:32:690	1100	13d8	AU	###########  AU: Initializing Automatic Updates  ###########
    2013-02-05	16:30:32:690	1100	13d8	AU	AU setting next sqm report timeout to 2013-02-05 15:30:32
    2013-02-05	16:30:32:690	1100	13d8	AU	  # WSUS server: http://[hostname]
    2013-02-05	16:30:32:690	1100	13d8	AU	  # Detection frequency: 10
    2013-02-05	16:30:32:690	1100	13d8	AU	  # Approval type: Pre-install notify (Policy)
    2013-02-05	16:30:32:690	1100	13d8	AU	  # Auto-install minor updates: No (User preference)
    2013-02-05	16:30:32:722	1100	13d8	AU	Initializing featured updates
    2013-02-05	16:30:32:722	1100	13d8	AU	Found 0 cached featured updates
    2013-02-05	16:30:32:800	1100	1740	Report	  * Computer Brand = VMware, Inc.
    2013-02-05	16:30:32:800	1100	1740	Report	  * Computer Model = VMware Virtual Platform
    2013-02-05	16:30:32:800	1100	1740	Report	  * Bios Revision = 6.00
    2013-02-05	16:30:32:800	1100	1740	Report	  * Bios Name = PhoenixBIOS 4.0 Release 6.0     
    2013-02-05	16:30:32:800	1100	1740	Report	  * Bios Release Date = 2011-07-12T00:00:00
    2013-02-05	16:30:32:800	1100	1740	Report	  * Locale ID = 1043
    2013-02-05	16:30:32:800	1100	13d8	AU	AU finished delayed initialization
    2013-02-05	16:30:32:800	1100	1740	AU	#############
    2013-02-05	16:30:32:800	1100	1740	AU	## START ##  AU: Search for updates
    2013-02-05	16:30:32:800	1100	1740	AU	#########
    2013-02-05	16:30:32:800	1100	1740	AU	<<## SUBMITTED ## AU: Search for updates [CallId = {91B288CB-AF16-42E6-BBF0-A04FD8D9FF97}]
    2013-02-05	16:30:32:800	1100	13d8	AU	Triggering AU detection through DetectNow API
    2013-02-05	16:30:32:800	1100	13d8	AU	Will do the detection after current detection completes
    2013-02-05	16:30:32:800	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{BA71D090-10E8-42EB-8D7B-666BD3661158}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:800	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{1D739AB9-3D0C-4647-A1A9-5AB439C05647}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:800	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{AE6AB02C-3A14-4758-8C18-5BBF1DB9A275}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:800	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{2D65E8A3-7AE1-4C4A-9D52-EE55CE14506C}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:800	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{46A51BFD-02AD-44E3-9CC5-FCCCD31D8E2A}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:800	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{D9FE1915-E5A9-42E3-8877-208E2BC07F93}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:800	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{7B955B88-271F-4DF0-9601-77140ECEE098}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:800	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{9530AD09-AA82-4924-BD5A-25056296D94A}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:800	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{55BC7B8D-4F96-4FD5-BF95-4295C222E3E9}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:800	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{7B81484A-7B3E-49DF-90CD-49B0B8CA9056}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:800	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{18A7A491-AA5C-40DF-9B1D-5BFD4002F12A}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:800	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{94A113C7-D003-4503-B07C-EE77275DA810}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:800	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{C5D01508-F5E7-4C85-BBE1-0C6E9535BF63}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{69A31663-02B7-4671-A1F8-06CB2AD5F943}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{BE9302D6-7285-4ECD-897D-FA0A6E827450}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{3D1DCDB2-2EF3-4DA2-BE1E-6C797BC49BBF}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{4A7BD0E6-6ECB-4752-8137-A797ED07A57D}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{2F6C3D3F-4FCF-405C-84A2-0367DA7F1C32}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{CF6D309E-7D98-4A90-B007-27A590BA6544}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{933E348E-527E-4C96-8947-D8CF6F29AA15}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{F17D3CCD-D889-4B88-BAAD-8D4A73996BBA}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{82FC82E3-CCB8-4134-99C6-1236437B42D2}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{05E9CE94-A546-4F93-A923-837D3BB5EB5F}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{6EA7D4A8-1083-4BE1-8734-243C73723707}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{3663FF84-9B18-48B0-B251-35345C596B75}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{C661B051-67FF-4945-9606-46F8BA834E3D}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{FEBEAFF9-ED11-41AF-9A18-432DD6E61562}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{96E6880A-7CB9-4E75-BEA7-3F5AA45135D4}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{C905EEE5-5423-4883-A5FA-18F9B655C0E8}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{0DA42DF2-DA84-46D4-89F0-1B9D6DC3AAEF}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{02F4033D-6147-4266-B62E-8D3280024106}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{A7CEEB10-23ED-4E71-9FCB-FB23997E3261}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{9FA22AA0-B21C-4437-B28C-28968827A3A5}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{5FA2CB38-A229-411D-BD88-0DEDF686C0CA}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{DD1142CB-57DA-442F-8FFC-A3CD2C9C5EE2}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{C8F956AA-0885-425A-8BBA-C988ACEA0D2A}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{1DB396F8-DF78-4D61-8723-15F41D6E39B0}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{0A431258-0377-4D84-B68C-C86BAB496128}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{36F608C2-63FF-487B-952D-96AD17B4713B}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{021AD20E-EA95-4F01-86B9-D8A48663E5B3}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{3A376949-9765-4C76-B7E7-332CFD8CDB6B}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{3FA8BBE7-D06A-460F-8D09-FBF2E0928AFA}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{C7A6F2D2-06DC-4D3E-B3F2-B5114E31E010}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{FEA39A20-5142-498E-ABC6-B84A1A0A3471}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{BB33F52E-FC57-4A2F-930B-9C691C4E8F56}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{2BE31F33-7E24-40F4-8B83-F1907F35FB09}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{73C56E7C-5D6F-4883-A0A5-5BF6EA9C2DB5}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{5B8E0487-B45E-4DEE-AC11-E9F487F47BA0}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{2B5A3BAA-B6A7-4680-80E7-81D6F4FD9B98}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{97007614-1503-426F-9EA8-C477E23A434C}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{10017890-CF9D-4A33-B6E9-87A597D93956}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{49AD407C-49A4-40E1-B6C2-BA31C7C7049C}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Report	WARNING: Failed to open event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{D15669E0-6D3A-490E-8959-77A1CF4A45E1}.bin for reading with hr = 80070002.
    2013-02-05	16:30:32:815	1100	5e0	Agent	*************
    2013-02-05	16:30:32:815	1100	5e0	Agent	** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-02-05	16:30:32:815	1100	5e0	Agent	*********
    2013-02-05	16:30:32:815	1100	5e0	Agent	  * Online = No; Ignore download priority = No
    2013-02-05	16:30:32:815	1100	5e0	Agent	  * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1"
    2013-02-05	16:30:32:815	1100	5e0	Agent	  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2013-02-05	16:30:32:815	1100	5e0	Agent	  * Search Scope = {Machine}
    2013-02-05	16:30:32:987	1100	5e0	Agent	  * Found 0 updates and 0 categories in search; evaluated appl. rules of 0 out of 0 deployed entities
    2013-02-05	16:30:32:987	1100	5e0	Agent	*********
    2013-02-05	16:30:32:987	1100	5e0	Agent	**  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-02-05	16:30:32:987	1100	5e0	Agent	*************
    2013-02-05	16:30:32:987	1100	1510	AU	>>##  RESUMED  ## AU: Search for updates [CallId = {91B288CB-AF16-42E6-BBF0-A04FD8D9FF97}]
    2013-02-05	16:30:32:987	1100	1510	AU	  # 0 updates detected
    2013-02-05	16:30:32:987	1100	1510	AU	#########
    2013-02-05	16:30:32:987	1100	1510	AU	##  END  ##  AU: Search for updates [CallId = {91B288CB-AF16-42E6-BBF0-A04FD8D9FF97}]
    2013-02-05	16:30:32:987	1100	1510	AU	#############
    2013-02-05	16:30:32:987	1100	1510	AU	Featured notifications is disabled.
    2013-02-05	16:30:32:987	1100	1740	AU	#############
    2013-02-05	16:30:32:987	1100	1740	AU	## START ##  AU: Search for updates
    2013-02-05	16:30:32:987	1100	1740	AU	#########
    2013-02-05	16:30:32:987	1100	1740	AU	<<## SUBMITTED ## AU: Search for updates [CallId = {851FCC07-5CB3-49FF-A042-C7BE40390BC2}]
    2013-02-05	16:30:32:987	1100	5e0	Agent	*************
    2013-02-05	16:30:32:987	1100	5e0	Agent	** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-02-05	16:30:32:987	1100	5e0	Agent	*********
    2013-02-05	16:30:32:987	1100	5e0	Agent	  * Online = Yes; Ignore download priority = No
    2013-02-05	16:30:32:987	1100	5e0	Agent	  * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1"
    2013-02-05	16:30:32:987	1100	5e0	Agent	  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2013-02-05	16:30:32:987	1100	5e0	Agent	  * Search Scope = {Machine}
    2013-02-05	16:30:33:268	1100	5e0	Misc	Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2013-02-05	16:30:33:300	1100	5e0	Misc	 Microsoft signed: Yes
    2013-02-05	16:30:33:315	1100	5e0	Misc	Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
    2013-02-05	16:30:33:331	1100	5e0	Misc	 Microsoft signed: Yes
    2013-02-05	16:30:33:331	1100	5e0	Setup	***********  Setup: Checking whether self-update is required  ***********
    2013-02-05	16:30:33:331	1100	5e0	Setup	  * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
    2013-02-05	16:30:33:331	1100	5e0	Setup	Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-02-05	16:30:33:331	1100	5e0	Setup	Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-02-05	16:30:33:331	1100	5e0	Setup	Update NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-02-05	16:30:33:331	1100	5e0	Setup	Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-02-05	16:30:33:331	1100	5e0	Setup	Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-02-05	16:30:33:331	1100	5e0	Setup	Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-02-05	16:30:33:331	1100	5e0	Setup	Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-02-05	16:30:33:331	1100	5e0	Setup	Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-02-05	16:30:33:331	1100	5e0	Setup	Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-02-05	16:30:33:331	1100	5e0	Setup	Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-02-05	16:30:33:331	1100	5e0	Setup	Update NOT required for C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups.dll\7.6.7600.256\wups.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-02-05	16:30:33:331	1100	5e0	Setup	Update NOT required for C:\WINDOWS\system32\SoftwareDistribution\Setup\ServiceStartup\wups2.dll\7.6.7600.256\wups2.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-02-05	16:30:33:331	1100	5e0	Setup	Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-02-05	16:30:33:331	1100	5e0	Setup	  * IsUpdateRequired = No
    2013-02-05	16:30:33:518	1100	5e0	PT	+++++++++++  PT: Synchronizing server updates  +++++++++++
    2013-02-05	16:30:33:518	1100	5e0	PT	  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://[hostname]:80/ClientWebService/client.asmx
    2013-02-05	16:30:33:518	1100	5e0	PT	WARNING: GetConfig failure, error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200
    2013-02-05	16:30:33:518	1100	5e0	PT	WARNING: PTError: 0x80244008
    2013-02-05	16:30:33:518	1100	5e0	PT	WARNING: GetConfig_WithRecovery failed: 0x80244008
    2013-02-05	16:30:33:518	1100	5e0	PT	WARNING: RefreshConfig failed: 0x80244008
    2013-02-05	16:30:33:518	1100	5e0	PT	WARNING: RefreshPTState failed: 0x80244008
    2013-02-05	16:30:33:518	1100	5e0	PT	WARNING: Sync of Updates: 0x80244008
    2013-02-05	16:30:33:518	1100	5e0	PT	WARNING: SyncServerUpdatesInternal failed: 0x80244008
    2013-02-05	16:30:33:518	1100	5e0	Agent	  * WARNING: Failed to synchronize, error = 0x80244008
    2013-02-05	16:30:33:518	1100	5e0	Agent	  * WARNING: Exit code = 0x80244008
    2013-02-05	16:30:33:518	1100	5e0	Agent	*********
    2013-02-05	16:30:33:518	1100	5e0	Agent	**  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-02-05	16:30:33:518	1100	5e0	Agent	*************
    2013-02-05	16:30:33:518	1100	5e0	Agent	WARNING: WU client failed Searching for update with error 0x80244008
    2013-02-05	16:30:33:518	1100	1510	AU	>>##  RESUMED  ## AU: Search for updates [CallId = {851FCC07-5CB3-49FF-A042-C7BE40390BC2}]
    2013-02-05	16:30:33:518	1100	1510	AU	  # WARNING: Search callback failed, result = 0x80244008
    2013-02-05	16:30:33:518	1100	1510	AU	  # WARNING: Failed to find updates with error code 80244008
    2013-02-05	16:30:33:518	1100	1510	AU	#########
    2013-02-05	16:30:33:518	1100	1510	AU	##  END  ##  AU: Search for updates [CallId = {851FCC07-5CB3-49FF-A042-C7BE40390BC2}]
    2013-02-05	16:30:33:518	1100	1510	AU	#############
    2013-02-05	16:30:33:518	1100	1510	AU	AU setting next detection timeout to 2013-02-05 20:30:33
    2013-02-05	16:30:37:800	1100	5e0	Report	REPORT EVENT: {4BE88F1D-7D48-4A53-A02B-D54AAB27A15B}	2013-02-05 16:30:32:722+0100	1	202	102	{00000000-0000-0000-0000-000000000000}	0	0	AutomaticUpdates	Success	Content Install	Reboot completed.
    2013-02-05	16:30:37:800	1100	5e0	Report	REPORT EVENT: {4D6BF92B-3728-48F8-B4DC-617C4CAC0617}	2013-02-05 16:30:33:518+0100	1	148	101	{00000000-0000-0000-0000-000000000000}	0	80244008	AutomaticUpdates	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x80244008.
    

    terça-feira, 5 de fevereiro de 2013 15:36
  • 2013-02-05 16:30:33:518 1100 5e0 PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://[hostname]:80/ClientWebService/client.asmx
    2013-02-05 16:30:33:518 1100 5e0 PT WARNING: GetConfig failure,error = 0x80244008, soap client error = 8, soap error code = 0, HTTP status code = 200

    from WSUS Technical Reference Guide: Windows Update Agent Result Codes

    0x80244008

    WU_E_PT_SOAPCLIENT_PARSEFAULT

    SOAP client failed to parse a SOAP fault.

    If I'm understanding this error correctly, it's throwing an exception trying to parse a SOAP fault.

    0x8024400A

    WU_E_PT_SOAPCLIENT_PARSE

    SOAP client failed to parse the response from the server.

    I can't help but wonder if the SOAP fault it's unable to parse is the original 0x8024400A that was observed prior to destroying the WUAgent datastore. I should also note that the 0x8024400A error message you originally reported is a very rare error code, and throughout the history of WSUS (since the release of v2 in 2005), in the few instances that I've seen 0x8024400A .. the only resolution was to rebuild the WSUS server. An actual -cause- for that error code has never been definitively identified (thus no known remediation except to reinstall).

    You said the client is a Win2003 R2 SP2 Citrix Terminal Server ...  running as a virtual machine? You've also indicated there are multiple clients not connecting. Are all of these non-connecting clients Win2003 systems? Are they all Terminal Servers? Are they all Virtual Machines? Are they all Virtual Machines on VMWare?

    2013-02-05 16:30:32:675 1100 1740 Report   * OS Version = 5.2.3790.2.0.196624
    2013-02-05 16:30:32:800 1100 1740 Report   * Computer Brand = VMware, Inc.
    2013-02-05 16:30:32:800 1100 1740 Report   * Computer Model = VMware Virtual Platform
    2013-02-05 16:30:32:800 1100 1740 Report   * Locale ID = 1043

    You've already rebuilt the client-side SoftwareDistribution folder twice, with no relief, which strongly rules out a client-side issue as well.


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

    terça-feira, 5 de fevereiro de 2013 23:17
  • Thanx for your reply!

    All the non-connecting clients are the same server as discribed, and they are all VMware virtual machines.
    The the thing is, the wsus server is brand new. It has been installed arond december-2012 and it has replaced an server2003 based wsus server.
    Could this be a part of the issue?

    If i open this URL: http://[hostname]:80/ClientWebService/client.asmx
    i get an page with application errors on it. Is this normal? The corrupt page could indeed result in the next error, 'get config failure', and thus could the client not get the right responce form the server.

    Rinstalling wsus. do you mean completely, including the OS and start from scratch or just removing the WSUS role and reinstall the role?
    The first thing could be a bit problematic, because the server is also running the management software for my antivirus solution.

    Well, i kinda hoped for an client-side problem, cause of the fact that other clients (w2k8, w7, XP) are connecting correctly.
    I checked other server2003 machines, who have an other role (e.g. file server / application server) who are also connection correctly. So the paltform (server2003) is also ruled out.
    It could be, of course an server side problem, but then it must be something what the other clients won't use of dont need to make an connection.
    quarta-feira, 6 de fevereiro de 2013 07:57
  • All the non-connecting clients are the same server as discribed, and they are all VMware virtual machines.
    The the thing is, the wsus server is brand new. It has been installed arond december-2012 and it has replaced an server2003 based wsus server.
    Could this be a part of the issue?

    It could be, but given that all of the affected clients are all the same operating system and all VMWare virtual machines, I'm inclined to start with the possibility that you have duplicated SusClientIDs. Refer to KB903262 to clear the necessary registry values, and retry the detection. If that doesn't clear the issue, we can dig deeper.

    If i open this URL: http://[hostname]:80/ClientWebService/client.asmx
    i get an page with application errors on it. Is this normal?

    Yes. There is a limited amount of 'browsable' content on a WSUS server. Try checking these URLs:

    • http://hostname/iuident.cab
    • http://hostname/selfupdate/iuident.cab
    • http://hostname/SimpleAuthWebService/SimpleAuth.asmx

    The first two URLs should produce a File Open/Save dialog; the third URL will provide a WSDL information page.

    ALSO.... remove the :80 from your URL. It's not necessary since port 80 is the default, and I have seen the :80 suffix cause problems

    The other thing you should do is download the SolarWinds WSUS Diagnostic Tool for the WSUS Agent and run it on one of these systems and get a report on what is working and/or is not.


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

    quinta-feira, 7 de fevereiro de 2013 01:05
  • ALSO.... remove the :80 from your URL. It's not necessary since port 80 is the default, and I have seen the :80 suffix cause problems

    Is this also adviced for the GPO settings?

    It has been a while since my last reply.

    The thing is: The day after the servers suddanly started to report again. I must have done something in my troubleshooting and trial&error what didn't fixed it right away, but after a period of time. The problem is now: it's back. The same servers are not reporting to the Wsus server. Same error, same conditions.
    In an attempt to fix the problem we have tried to completely remove the WSUS role from the server, and start from scratch. It didn't resolved the issue.

    terça-feira, 28 de maio de 2013 13:28
  • ALSO.... remove the :80 from your URL. It's not necessary since port 80 is the default, and I have seen the :80 suffix cause problems

    Is this also adviced for the GPO settings?

    Yes, that's what I meant.

    The thing is: The day after the servers suddanly started to report again. I must have done something in my troubleshooting and trial&error what didn't fixed it right away, but after a period of time. The problem is now: it's back. The same servers are not reporting to the Wsus server. Same error, same conditions.

    Well..shucks. :-//


    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.

    quinta-feira, 30 de maio de 2013 02:15