none
WSUS 2 ClientWebService/client.asmx error RRS feed

  • Question

  • The first step of upgrading from WSUS2 to WSUS 3 is to make sure the WSUS 2 server is working correctly, that's where i'm stuck. Some of the webservices don't work and i can't see why. I did search before i started writing this post and i tried a number of things including (but not limited to) enabling/disabling iis compression, checking permissions on the various directories required as per the troubleshooting blog posts, re-registering asp.net 1.1 on the services that aren't working. No difference.

    I've got a 2003 box machine with no peculiar iis setup, clean recent install. WSUS 2 installed using sql2k5ee, admin site works, selfupdate tree works. I installed a fresh win2k vm and patched it to sp4, setup the registry and use /detectnow to force an update.

    Agent	*************
    
    Agent	** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    
    Agent	*********
    
    Setup	***********  Setup: Checking whether self-update is required  ***********
    
    Setup	  * Inf file: C:\WINNT\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
    
    Setup	Update NOT required for C:\WINNT\system32\cdm.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    Setup	Update NOT required for C:\WINNT\system32\iuengine.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    Setup	Update NOT required for C:\WINNT\system32\wuapi.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    Setup	Update NOT required for C:\WINNT\system32\wuauclt.exe: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    Setup	Update NOT required for C:\WINNT\system32\wuauclt1.exe: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    Setup	Update NOT required for C:\WINNT\system32\wuaucpl.cpl: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    Setup	Update NOT required for C:\WINNT\system32\wuaueng.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    Setup	Update NOT required for C:\WINNT\system32\wuaueng1.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    Setup	Update NOT required for C:\WINNT\system32\wucltui.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    Setup	Update NOT required for C:\WINNT\system32\wups.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    Setup	Update NOT required for C:\WINNT\system32\wups2.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    Setup	Update NOT required for C:\WINNT\system32\wuweb.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    Setup	  * IsUpdateRequired = No
    
    PT	+++++++++++  PT: Synchronizing server updates  +++++++++++
    
    PT	  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://server:8530/ClientWebService/client.asmx
    
    PT	WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    
    PT	WARNING: SOAP Fault: 0x00012c
    
    PT	WARNING:     faultstring:Fault occurred
    
    PT	WARNING:     ErrorCode:InvalidCookie(1)
    
    PT	WARNING:     Message:
    
    
    
    PT	WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    
    PT	WARNING:     ID:ea2a79be-fb21-46da-a99e-bfc6601a0957
    
    PT	WARNING: Sync of Updates: 0x80244015
    
    PT	Initializing simple targeting cookie, clientId = 59c3b62f-44f0-4b78-b5dc-8a434ae4723c, target group = , DNS name = win2kupd
    
    PT	  Server URL = http://server:8530/SimpleAuthWebService/SimpleAuth.asmx
    
    PT	WARNING: No updates found from server; serverID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    
    Agent	  * WARNING: Failed to synchronize, error = 0x80244015
    
    DnldMgr	File locations for service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 changed
    
    Agent	Server changed and need resyncing with server
    
    PT	+++++++++++  PT: Synchronizing server updates  +++++++++++
    
    PT	  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://server:8530/ClientWebService/client.asmx
    
    PT	WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
    
    PT	WARNING: SOAP Fault: 0x000190
    
    PT	WARNING:     faultstring:Fault occurred
    
    PT	WARNING:     ErrorCode:InternalServerError(5)
    
    PT	WARNING:     Message:
    
    
    
    PT	WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    
    PT	WARNING:     ID:8615c78b-7339-4a9e-b7b5-abeaa28dcc18
    
    PT	WARNING: Sync of Updates: 0x8024400e
    
    Agent	  * WARNING: Failed to synchronize, error = 0x8024400E
    
    Agent	  * WARNING: Exit code = 0x8024400E
    
    Agent	*********
    
    Agent	**  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    
    Agent	*************
    
    Agent	WARNING: WU client failed Searching for update with error 0x8024400e
    
    AU	>>##  RESUMED  ## AU: Search for updates [CallId = {8984348D-F72A-4ADA-8EEE-13592F32D69C}]
    
    AU	  # WARNING: Search callback failed, result = 0x8024400E
    
    AU	#########
    
    AU	##  END  ##  AU: Search for updates [CallId = {8984348D-F72A-4ADA-8EEE-13592F32D69C}]
    
    AU	#############
    
    AU	AU setting next detection timeout to 2009-04-25 00:55:14
    
    Report	REPORT EVENT: {18960A83-E89F-4BFD-A270-F3B07CDF1710}	2009-04-24 20:55:14+0100	1	148	101	{00000000-0000-0000-0000-000000000000}	0	8024400e	AutomaticUpdates	Failure	Software Synchronization	Error: Agent failed detecting with reason: 0x8024400e
    
    
    After seeing this i checked on the server and attempting to access the failing webservice from ie yields

    Server Error in '/ClientWebService' Application.
    
    --------------------------------------------------------------------------------
    
    
    
    Request format is unrecognized. 
    
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 
    
    
    
    Exception Details: System.InvalidOperationException: Request format is unrecognized.
    with a generic error message and largely pointless stack trace into the internals of the webservices framework which i'll provider if anyone really want it. The client diagnotic tool run on the win2k client passes with no errors.

    I've trawled the internet looking for a solution to this. I've tried everything i can, i've reinstalled wsus a couple of times and the problem persists leading me to think it isn't actually a wsus problem. I can't work out how to fix it though. Please help if you can.
    • Edited by Wraith2 Friday, April 24, 2009 9:34 PM
    Friday, April 24, 2009 8:13 PM

Answers


  • This really is getting rather annoying. Have you anything that might actually help apart from telling me that my platform isn't supported or to try and operating system i don't own?

    No. Those would be the only two viable solutions to your issue as presented.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Friday, June 5, 2009 3:32 PM
    Moderator

All replies

  • I was able to get an answer from here: http://www.wsus.info/forums/index.php?showtopic=4614
    But I still have other errors, so I don't know if that ultimately fixes it.

    Anyway, that link tells you to modify the web.config in the C:\Program Files\Update Services\WebServices\clientwebservice folder

    ORIGINAL web.config snippet:
    ---------------------------
    <webServices>
    <protocols>
    <!-- <add name="HttpSoap1.2"/> -->
    <add name="HttpSoap"/>
    <add name="HttpPost"/>
    <add name="HttpGet"/>
    <!-- <add name="HttpPostLocalhost"/> -->
    <add name="Documentation"/>
    </protocols>
    </webServices>

    NEW web.config snippet
    ---------------------------

    <webServices>
    <protocols>
    <remove name="Documentation"/>
    <!-- <add name="HttpSoap1.2"/> -->
    <add name="HttpSoap"/>
    <add name="HttpPost"/>
    <add name="HttpGet"/>
    <!-- <add name="HttpPostLocalhost"/> -->
    <add name="Documentation"/>
    </protocols>

    <!-- Run SOAP Header Filter with ClientWebService -->
    <soapExtensionTypes>
    <add type="Microsoft.UpdateServices.WUShield,WUShield"
    priority="1"
    group="0" />
    </soapExtensionTypes>
    </webServices>
    Saturday, April 25, 2009 2:31 AM
  • Nope, i've already tried that. I just tried it again to ber certain. Added those lines to the ClientWebService web.config file, restarted update services and iis ,The InvaliidOperationException persists.
    Saturday, April 25, 2009 9:36 AM
  • Your logfile shows an error with a known cause and resolution.

    PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://server:8530/ClientWebService/client.asmx
    PT WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    PT WARNING: SOAP Fault: 0x00012c
    PT WARNING:     faultstring:Fault occurred
    PT WARNING:     ErrorCode:InvalidCookie(1)
    PT WARNING:     Message:

    PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    PT WARNING:     ID:ea2a79be-fb21-46da-a99e-bfc6601a0957
    PT WARNING: Sync of Updates: 0x80244015

    One place this combination of errors has been seen in in load-balanced deployments:
    http://blogs.technet.com/sus/archive/2008/10/29/wsus-clients-fail-synchronization-with-0x80244015-and-0x8024400d-errors.aspx

    In your case, though, it may be something a bit more simpler, that manifests in a similar way.

    PT Initializing simple targeting cookie, clientId = 59c3b62f-44f0-4b78-b5dc-8a434ae4723c, target group = , DNS name = win2kupd
    PT   Server URL = http://server:8530/SimpleAuthWebService/SimpleAuth.asmx
    PT WARNING: No updates found from server; serverID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    Agent   * WARNING: Failed to synchronize, error = 0x80244015
    DnldMgr File locations for service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 changed
    Agent Server changed and need resyncing with server

    Here we essentially see the client finding nothing at the URL configured. If you installed a clean WSUS v2 SP1 on a clean Win2003 installation, then why is the client attempting to access the WSUS Server on port 8530?

    Back to your original opening statement:
    The first step of upgrading from WSUS2 to WSUS 3 is to make sure the WSUS 2 server is working correctly, that's where i'm stuck.

    Perhaps you can share why you believe your WSUS 2 server was not working. Can you share an (UNEDITED) WindowsUpdate.log excerpt from a production machine dated from before you started all of your "repair" efforts? I'd like to be able to see the original issue that prompted all of this activity. Truth be told, your several attempts to "repair" the server is probably what's causing the problem now.

    None of that all withstanding anyway -- my general advice to people still running WSUS v2 is to just throw it away, and build the WSUS v3 server from scratch. In addition, you have a SQL Server 2005 Express Edition installation sitting behind your WSUS v2 server, and you'd be much better served to use the native Windows Internal Database with WSUS v3, rather than Express Edition.

    So, truly, it's your choice. If you wish to continue diagnosting this current WSUS v2 issue, I'll be happy to do so, and I've indicated what data we need to collect in order to made an educated analysis -- but for the amount of time you'll invest in that effort (and have already invested) -- I think it'll just be much better to install a new WSUS3SP1 server and forget about the WSUS2 installation entirely.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Saturday, April 25, 2009 2:42 PM
    Moderator
  • While the platform is windows2003 the actual distribution is windows home server. Load balancing is present because it's part of the underlying os but i wouldn't think it came configured out of the box and i haven't been fiddling with it and have no intrest in enabling it even if it were possible. The machine has the whs site installed on port 80 by default and while i could have removed or changed that i decided not to because when i upgraded from SUS to WSUS quite some time ago (on a different machine) i quite successfully ran WSUS on the alternate port while i configured and got to know the new version.

    It is possible that my attempts to fix the issue have clouded things but i'm quite careful in how i approach these things because i'm aware that i don't know entirely what i'm doing. At each stage i make a change test the result and then if it hasn't worked i back the changes out. The fact that the problem occurs in the first place was very unlikely to be the result of me trying to fix it. I've been through the common troubleshooting steps and tried what i can.

    I'm using wsus 2 because i've got a few gig of content that i'd really rather not download again given that my whole reason for using wsus in the first place was to lighten the load of windows updates on my slow and capped internet connection. I've been using this since sus and been stable on wsus for quite some time now. At the moment i'm trying to migrate away from what has become a virtual machine with wsus on it to a new home server which will not rely on my personal machine being available to serve updates. I realise this isn't quite the scale of deployment you may expect but the technology has worked in the past and i'd like to continue to use it to manage my family machines if possible. My plan was and is to migrate from the existing wsus2 server to a functional wsus2 server on the new machine and then upgrade that to wsus3.

    Would installing wsus3 cleanly allow me to use my existing content directories? i didn't find anything which suggested so in the documentation. Is there a way to migrate approvals from 2 to 3 without an upgrade? re-approving almost 3000 updates is an incredibly tedious task. I have tried installing 3 on the server now and the installer tells me that my database is invalid for upgrade, which is very unhelpful.

    I wasn't aware that i had removed useful information from the log portion i posted, it certainly wasn't my intention to do so. I can post one with the timestamps and associated bits and pieces in if that's what you need to help me find the problem. What did i miss? is there more information outside the region of the detection process?

    Here is a complete unabridged detection cycle, if you need more you'll have to give me instructions on how to generate it for you.
    2009-04-25	17:57:44	 732	200	Misc	===========  Logging initialized (build: 5.8.0.2607, tz: +0100)  ===========
    
    2009-04-25	17:57:44	 732	200	Misc	  = Process: C:\WINNT\system32\svchost.exe
    
    2009-04-25	17:57:44	 732	200	Misc	  = Module: C:\WINNT\system32\wuaueng.dll
    
    2009-04-25	17:57:44	 732	200	Service	*************
    
    2009-04-25	17:57:44	 732	200	Service	** START **  Service: Service startup
    
    2009-04-25	17:57:44	 732	200	Service	*********
    
    2009-04-25	17:57:44	 732	200	Agent	  * WU client version 5.8.0.2607
    
    2009-04-25	17:57:44	 732	200	Agent	  * SusClientId = '59c3b62f-44f0-4b78-b5dc-8a434ae4723c'
    
    2009-04-25	17:57:44	 732	200	Agent	  * Base directory: C:\WINNT\SoftwareDistribution
    
    2009-04-25	17:57:44	 732	200	Agent	  * Access type: No proxy
    
    2009-04-25	17:57:44	 732	200	Agent	  * Network state: Connected
    
    2009-04-25	17:57:58	 732	438	Agent	***********  Agent: Initializing Windows Update Agent  ***********
    
    2009-04-25	17:57:58	 732	438	Agent	***********  Agent: Initializing global settings cache  ***********
    
    2009-04-25	17:57:58	 732	438	Agent	  * WSUS server: http://server:8530
    
    2009-04-25	17:57:58	 732	438	Agent	  * WSUS status server: http://server:8530
    
    2009-04-25	17:57:58	 732	438	Agent	  * Target group: (Unassigned Computers)
    
    2009-04-25	17:57:58	 732	438	Agent	  * Windows Update access disabled: No
    
    2009-04-25	17:57:58	 732	438	DnldMgr	Download manager restoring 0 downloads
    
    2009-04-25	17:57:58	 732	438	AU	###########  AU: Initializing Automatic Updates  ###########
    
    2009-04-25	17:57:58	 732	438	AU	  # WSUS server: http://server:8530
    
    2009-04-25	17:57:58	 732	438	AU	  # Detection frequency: 22
    
    2009-04-25	17:57:58	 732	438	AU	  # Approval type: Pre-install notify (User preference)
    
    2009-04-25	17:57:58	 732	438	AU	  # Auto-install minor updates: No (Policy)
    
    2009-04-25	17:57:58	 732	438	AU	Triggering AU detection through DetectNow API
    
    2009-04-25	17:57:58	 732	200	AU	#############
    
    2009-04-25	17:57:58	 732	200	AU	## START ##  AU: Search for updates
    
    2009-04-25	17:57:58	 732	200	AU	#########
    
    2009-04-25	17:57:58	 732	200	AU	<<## SUBMITTED ## AU: Search for updates [CallId = {2BFA18DD-BA02-422F-867F-2241BF7432C5}]
    
    2009-04-25	17:57:58	 732	450	Agent	*************
    
    2009-04-25	17:57:58	 732	450	Agent	** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    
    2009-04-25	17:57:58	 732	450	Agent	*********
    
    2009-04-25	17:58:01	 732	450	Setup	***********  Setup: Checking whether self-update is required  ***********
    
    2009-04-25	17:58:01	 732	450	Setup	  * Inf file: C:\WINNT\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
    
    2009-04-25	17:58:01	 732	450	Setup	Update NOT required for C:\WINNT\system32\cdm.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    2009-04-25	17:58:01	 732	450	Setup	Update NOT required for C:\WINNT\system32\iuengine.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    2009-04-25	17:58:01	 732	450	Setup	Update NOT required for C:\WINNT\system32\wuapi.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    2009-04-25	17:58:01	 732	450	Setup	Update NOT required for C:\WINNT\system32\wuauclt.exe: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    2009-04-25	17:58:01	 732	450	Setup	Update NOT required for C:\WINNT\system32\wuauclt1.exe: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    2009-04-25	17:58:01	 732	450	Setup	Update NOT required for C:\WINNT\system32\wuaucpl.cpl: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    2009-04-25	17:58:01	 732	450	Setup	Update NOT required for C:\WINNT\system32\wuaueng.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    2009-04-25	17:58:01	 732	450	Setup	Update NOT required for C:\WINNT\system32\wuaueng1.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    2009-04-25	17:58:01	 732	450	Setup	Update NOT required for C:\WINNT\system32\wucltui.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    2009-04-25	17:58:01	 732	450	Setup	Update NOT required for C:\WINNT\system32\wups.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    2009-04-25	17:58:01	 732	450	Setup	Update NOT required for C:\WINNT\system32\wups2.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    2009-04-25	17:58:01	 732	450	Setup	Update NOT required for C:\WINNT\system32\wuweb.dll: target version = 5.8.0.2607, required version = 5.8.0.2607
    
    2009-04-25	17:58:01	 732	450	Setup	  * IsUpdateRequired = No
    
    2009-04-25	17:58:01	 732	450	PT	+++++++++++  PT: Synchronizing server updates  +++++++++++
    
    2009-04-25	17:58:01	 732	450	PT	  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://server:8530/ClientWebService/client.asmx
    
    2009-04-25	17:58:01	 732	450	PT	Initializing simple targeting cookie, clientId = 59c3b62f-44f0-4b78-b5dc-8a434ae4723c, target group = , DNS name = win2kwsus
    
    2009-04-25	17:58:01	 732	450	PT	  Server URL = http://server:8530/SimpleAuthWebService/SimpleAuth.asmx
    
    2009-04-25	17:58:01	 732	450	PT	WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
    
    2009-04-25	17:58:01	 732	450	PT	WARNING: SOAP Fault: 0x000190
    
    2009-04-25	17:58:01	 732	450	PT	WARNING:     faultstring:Fault occurred
    
    2009-04-25	17:58:01	 732	450	PT	WARNING:     ErrorCode:InternalServerError(5)
    
    2009-04-25	17:58:01	 732	450	PT	WARNING:     Message:
    
            
    
    2009-04-25	17:58:01	 732	450	PT	WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    
    2009-04-25	17:58:01	 732	450	PT	WARNING:     ID:5be26383-0174-46ca-ac65-0d5b8e082965
    
    2009-04-25	17:58:01	 732	450	PT	WARNING: Sync of Updates: 0x8024400e
    
    2009-04-25	17:58:01	 732	450	Agent	  * WARNING: Failed to synchronize, error = 0x8024400E
    
    2009-04-25	17:58:01	 732	450	Report	***********  Report: Initializing static reporting data  ***********
    
    2009-04-25	17:58:01	 732	450	Report	  * OS Version = 5.0.2195.4.0.65536
    
    2009-04-25	17:58:01	 732	450	Report	  * Computer Brand = VMware, Inc.
    
    2009-04-25	17:58:01	 732	450	Report	  * Computer Model = VMware Virtual Platform
    
    2009-04-25	17:58:01	 732	450	Report	  * Bios Revision = 6.00
    
    2009-04-25	17:58:01	 732	450	Report	  * Bios Name = Default System BIOS
    
    2009-04-25	17:58:01	 732	450	Report	  * Bios Release Date = 2008-07-29T00:00:00
    
    2009-04-25	17:58:01	 732	450	Report	  * Locale ID = 1033
    
    2009-04-25	17:58:01	 732	450	Agent	  * WARNING: Exit code = 0x8024400E
    
    2009-04-25	17:58:01	 732	450	Agent	*********
    
    2009-04-25	17:58:01	 732	450	Agent	**  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    
    2009-04-25	17:58:01	 732	450	Agent	*************
    
    2009-04-25	17:58:01	 732	450	Agent	WARNING: WU client failed Searching for update with error 0x8024400e
    
    2009-04-25	17:58:01	 732	450	AU	>>##  RESUMED  ## AU: Search for updates [CallId = {2BFA18DD-BA02-422F-867F-2241BF7432C5}]
    
    2009-04-25	17:58:01	 732	450	AU	  # WARNING: Search callback failed, result = 0x8024400E
    
    2009-04-25	17:58:01	 732	450	AU	#########
    
    2009-04-25	17:58:01	 732	450	AU	##  END  ##  AU: Search for updates [CallId = {2BFA18DD-BA02-422F-867F-2241BF7432C5}]
    
    2009-04-25	17:58:01	 732	450	AU	#############
    
    2009-04-25	17:58:01	 732	450	AU	AU setting next detection timeout to 2009-04-25 21:58:01
    
    2009-04-25	17:58:06	 732	450	Report	REPORT EVENT: {2134EA6A-5B0D-4203-9BF8-24911B002E0B}	2009-04-25 17:58:01+0100	1	148	101	{00000000-0000-0000-0000-000000000000}	0	8024400e	AutomaticUpdates	Failure	Software Synchronization	Error: Agent failed detecting with reason: 0x8024400e
    
    2009-04-25	18:01:08	 732	450	PT	Initializing simple targeting cookie, clientId = 59c3b62f-44f0-4b78-b5dc-8a434ae4723c, target group = , DNS name = win2kwsus
    
    2009-04-25	18:01:08	 732	450	PT	  Server URL = http://server:8530/SimpleAuthWebService/SimpleAuth.asmx
    
    2009-04-25	18:01:08	 732	450	Report	Uploading 2 events using cached cookie, reporting URL = http://server:8530/ReportingWebService/ReportingWebService.asmx
    
    2009-04-25	18:01:08	 732	450	Report	Reporter successfully uploaded 2 events.
    
    2009-04-25	18:01:29	 732	200	Service	*********
    
    2009-04-25	18:01:29	 732	200	Service	**  END  **  Service: Service exit [Exit code = 0x240001]
    
    2009-04-25	18:01:29	 732	200	Service	*************
    
    

    Confusingly while one webservice fails it does successfully report events with another, and win2kwsus does appear in the wsus admin website with the status listed as not yet reported status.


    To be clear this is not a server which has been working previously. It is a new install with content and approval migration from another server which continues to work perfectly well on a machine which was virtualized some time ago. The new machine will update itself but a clean win2k+sp4 install fails with the log output i have provided.
    • Edited by Wraith2 Saturday, April 25, 2009 5:17 PM clarification
    Saturday, April 25, 2009 5:10 PM
  • While the platform is windows2003 the actual distribution is windows home server.
    And, pray tell, based on =WHAT= information did you conclude that WSUS 3.0 was supported on a Windows Home Server installation???

    I think we've resolved this issue, no?

    WSUS needs to be installed on a Standard or Enterprise Edition of Windows Server, or on Small Business Server.



    > I'm using wsus 2 because i've got a few gig of content that i'd really rather not download again

    At the risk of being rude, that's a pointless reason for using an old, non-supported version. WSUS 3 is perfectly capable of using an existing content store, regardless of what version it was originally installed with. Frankly, I'm surprised that you claim you couldn't find any information about this fact, given that there's more than sufficient documentation covering the upgrade process from WSUS 2 to WSUS 3, all of which, if not explicitly stating, certainly implies that reality. And, beyond that, there's two years of peer content in newsgroups and forums when thousands of environment before yours upgraded, or asked about upgrading.

    Of course, trying to use WSUS 3.0 with a content store that old may also be an exercise in futility, since most of the content downloaded to a functioning WSUS 2.0 server has since been superceded and is probably worthless.


    > At the moment i'm trying to migrate away from what has become a virtual machine with wsus on it

    I suspect, this is the only reliable way you're going to deploy WSUS in a WHS environment. It's certainly the only way I would recommend doing so.

    But then, if your only machines are a WHS and your PC running Virtual PC (Virtual Server?) then what's your motivation for maintaining a multi-gig content store on WSUS anyway? much less the simpler question of why, even, do you have a WSUS Server for two machines?


    > To be clear this is not a server which has been working previously. It is a new install with content and approval
    > migration from another server which continues to work perfectly well on a machine which was virtualized some time ago.

    Herein exists an entirely new collection of reasons why this server may not be functioning correctly, depending on how the metadata was 'migrated' from the other server to this one. The fact that it's working perfectly well on another machine is even more reason we should abandon the current course of trying to get WSUS 2.0 to work on Windows Home Server.

    If you'd like some help migrating/upgrading your existing WSUS 2.0 VM to WSUS 3.0 -- either in the same VM, or on another VM on another server, or even another VM on the same host, I'll be happy to help you there. But WSUS 2.0, in general, is no longer a supported product; it was never supported on Windows Home Server, and if I pushed the question, I'd bet a fair amount of money that WSUS 3.0 isn't supported on Windows Home Server either -- and that's not even asking the more mundane question of whether it would even work. So far you're the only person who's tried it, and you're doing so in an extremely complex and convoluted scenario.

    I'll make you this deal, though. If you can get a virgin installation of WSUS 3.0 SP1 working on a Windows Home Server -- I'll gladly help you migrate your WSUS 2.0 approvals (and content, if there's actually any value in that content) to a working WSUS 3.0 SP1 installation on your Windows Home Server.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Saturday, April 25, 2009 9:29 PM
    Moderator
  • Supported? on WHS? i very much doubt it. Possible though? yes. For example http://www.wegotserved.co.uk/2008/01/06/how-to-integrate-windows-update-services-v3-wsus-into-windows-home-server/ is a reasonable basis to think that wsus 3 at least works on WHS. WHS is afterall some bits and pieces on top of 2k3sbs, msinfo even identifies the os as 2k3sbs which is a supported operating system for wsus3. 2k3 was also a supported os for wsus2. Wsus2 only required a server operating system because the installer was created with it as a dependency, wsus3 probably makes some use of server specific features but i seriously doubt there is a technical basis for a server based operating system not to allow it to work. wsus2 works locally at the moment so supported at not it is at least functional enough to patch itself. I don't see that the setup for either wsus version is particularly complex or convoluted but i seem to be missing some knowledge about the webservices configuration that i need so i thought i'd ask someone who might know.

    I know wsus2 is old, that's why i was trying to upgrade to 3. The wsus 3 deployment guide, which is afterall the vendor supplied documentation, tells me to have a working wsus2 build before i start trying to upgrade. The internet sources on this are confusing confused often wrong, when they're not trying to wade through the rest to find the correct information is an arduous task at best. The content downloaded to my wsus2 server isn't useless because i'm careful to decline superceded updates and only keep patches for systems that i know i need, removing uneeded content by declining and sweeping with the debug tool.

    I didn't claim to have only two machines using the wsus2 server, in fact i made no mention of the number. It is in fact around ten at the moment but that fluctuates as vm's come and go. I'm a developer and i have need of clean builds to test things so i sometimes install an old os into a vm and then patch it to the level i require with the local wsus server. If i had only two machines maintaining the existing server would obviously be more trouble that it is worth. As it is finding a way to move ~12 gig of content that would take me about a week to download again from a working machine to a newer more capable and better deployment technology seemed like a good idea. Migrating from 2 to 2 and then following the vendor supplied documentation to upgrade from 2 to 3 seemed like a reasonable plan of action.

    The metadata was migrated using the wsusutil tool supplied in the setup package for wsus2 following the instructions in the documentation for that version. Despite what you seem to think i'm not just throwing things about and expecting them to work, i'm following the documentation.

    After all that and having i think both agreed that i'm doing something that isn't supported and which may or may not work at all can you from that log tell what the client is having a problem with?

    With your assertion that i can simply transplant my content directory i'll have a go at putting in a clean wsus3sp1 install and see how it goes.

    Saturday, April 25, 2009 11:06 PM
  • Supported? on WHS? i very much doubt it. Possible though? yes. For example http://www.wegotserved.co.uk/2008/01/06/how-to-integrate-windows-update-services-v3-wsus-into-windows-home-server/ is a reasonable basis to think that wsus 3 at least works on WHS.


    Excuse me... this article is about imposing =WSUS3= on a WHS server, correct?

    As I recall, this thread has been about fixing =WSUS2= on said server, and a migrated WSUS 2 at that!

    So, let me reiterate my previous offer:
    I'll make you this deal, though. If you can get a virgin installation of WSUS 3.0 SP1 working on a Windows Home Server -- I'll gladly help you migrate your WSUS 2.0 approvals (and content, if there's actually any value in that content) to a working WSUS 3.0 SP1 installation on your Windows Home Server.

    If I find anything else of merit in the above post; I'll respond to that separately.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Monday, April 27, 2009 4:36 PM
    Moderator
  • Supported? on WHS? i very much doubt it. Possible though? yes. For example http://www.wegotserved.co.uk/2008/01/06/how-to-integrate-windows-update-services-v3-wsus-into-windows-home-server/ is a reasonable basis to think that wsus 3 at least works on WHS.


    Excuse me... this article is about imposing =WSUS3= on a WHS server, correct?

    As I recall, this thread has been about fixing =WSUS2= on said server, and a migrated WSUS 2 at that!

    So, let me reiterate my previous offer:
    I'll make you this deal, though. If you can get a virgin installation of WSUS 3.0 SP1 working on a Windows Home Server -- I'll gladly help you migrate your WSUS 2.0 approvals (and content, if there's actually any value in that content) to a working WSUS 3.0 SP1 installation on your Windows Home Server.

    If I find anything else of merit in the above post; I'll respond to that separately.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Monday, April 27, 2009 4:36 PM
    Moderator
  • Ok. WSUS3 installed, new database, synchronized and all approvals done.

    Works fine with a win2k vm on my client machine, patches fully.

    Vista x64 client machine, physical machine. Doesn't work. Not the same error, a new one (to me). Here's the complete log entry. The same error is reported with the server trying to update itself.
    2009-04-28	18:50:06:151	 768	d1c	Misc	===========  Logging initialized (build: 7.1.6001.65, tz: +0100)  ===========
    
    2009-04-28	18:50:06:151	 768	d1c	Misc	  = Process: C:\Windows\system32\svchost.exe
    
    2009-04-28	18:50:06:151	 768	d1c	Misc	  = Module: c:\windows\system32\wuaueng.dll
    
    2009-04-28	18:50:06:151	 768	d1c	Service	*************
    
    2009-04-28	18:50:06:151	 768	d1c	Service	** START **  Service: Service startup
    
    2009-04-28	18:50:06:151	 768	d1c	Service	*********
    
    2009-04-28	18:50:06:155	 768	d1c	Agent	  * WU client version 7.1.6001.65
    
    2009-04-28	18:50:06:156	 768	d1c	Agent	  * Base directory: C:\Windows\SoftwareDistribution
    
    2009-04-28	18:50:06:156	 768	d1c	Agent	  * Access type: No proxy
    
    2009-04-28	18:50:06:156	 768	d1c	Agent	  * Network state: Connected
    
    2009-04-28	18:50:51:171	 768	d1c	Agent	***********  Agent: Initializing Windows Update Agent  ***********
    
    2009-04-28	18:50:51:171	 768	d1c	Agent	***********  Agent: Initializing global settings cache  ***********
    
    2009-04-28	18:50:51:171	 768	d1c	Agent	  * WSUS server: http://server:8530
    
    2009-04-28	18:50:51:171	 768	d1c	Agent	  * WSUS status server: http://server:8530
    
    2009-04-28	18:50:51:171	 768	d1c	Agent	  * Target group: (Unassigned Computers)
    
    2009-04-28	18:50:51:171	 768	d1c	Agent	  * Windows Update access disabled: No
    
    2009-04-28	18:50:51:482	 768	d1c	DtaStor	Default service for AU is {00000000-0000-0000-0000-000000000000}
    
    2009-04-28	18:50:51:503	 768	d1c	DtaStor	Default service for AU is {9482F4B4-E343-43B6-B170-9A65BC822C77}
    
    2009-04-28	18:50:51:506	 768	d1c	Agent	WARNING: Failed to read the service id for re-registration 0x80070002
    
    2009-04-28	18:50:51:506	 768	d1c	Agent	WARNING: Missing service entry in the backup data store; cleaning up
    
    2009-04-28	18:50:51:512	 768	d1c	DnldMgr	Download manager restoring 0 downloads
    
    2009-04-28	18:50:51:514	 768	d1c	AU	###########  AU: Initializing Automatic Updates  ###########
    
    2009-04-28	18:50:51:516	 768	d1c	AU	  # WSUS server: http://server:8530
    
    2009-04-28	18:50:51:516	 768	d1c	AU	  # Detection frequency: 22
    
    2009-04-28	18:50:51:516	 768	d1c	AU	  # Approval type: Pre-download notify (User preference)
    
    2009-04-28	18:50:51:517	 768	d1c	AU	AU finished delayed initialization
    
    2009-04-28	18:50:51:680	 768	d1c	Report	***********  Report: Initializing static reporting data  ***********
    
    2009-04-28	18:50:51:680	 768	d1c	Report	  * OS Version = 6.0.6001.1.0.65792
    
    2009-04-28	18:50:51:680	 768	d1c	Report	  * OS Product Type = 0x00000001
    
    2009-04-28	18:50:51:716	 768	d1c	Report	  * Computer Brand = System manufacturer
    
    2009-04-28	18:50:51:717	 768	d1c	Report	  * Computer Model = P5Q-PRO
    
    2009-04-28	18:50:51:719	 768	d1c	Report	  * Bios Revision = 0506   
    
    2009-04-28	18:50:51:719	 768	d1c	Report	  * Bios Name = BIOS Date: 05/26/08 00:51:17 Ver: 08.00.14
    
    2009-04-28	18:50:51:719	 768	d1c	Report	  * Bios Release Date = 2008-05-26T00:00:00
    
    2009-04-28	18:50:51:719	 768	d1c	Report	  * Locale ID = 2057
    
    2009-04-28	18:50:53:590	 768	1238	AU	Triggering AU detection through DetectNow API
    
    2009-04-28	18:50:53:590	 768	1238	AU	Triggering Online detection (interactive)
    
    2009-04-28	18:50:53:590	 768	d1c	AU	#############
    
    2009-04-28	18:50:53:590	 768	d1c	AU	## START ##  AU: Search for updates
    
    2009-04-28	18:50:53:590	 768	d1c	AU	#########
    
    2009-04-28	18:50:53:592	 768	d1c	AU	<<## SUBMITTED ## AU: Search for updates [CallId = {D3C0597C-47F4-46BA-8085-FB4051AFB2CD}]
    
    2009-04-28	18:50:53:592	 768	11e8	Agent	*************
    
    2009-04-28	18:50:53:592	 768	11e8	Agent	** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    
    2009-04-28	18:50:53:592	 768	11e8	Agent	*********
    
    2009-04-28	18:50:53:592	 768	11e8	Agent	  * Online = Yes; Ignore download priority = No
    
    2009-04-28	18:50:53:592	 768	11e8	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"
    
    2009-04-28	18:50:53:592	 768	11e8	Agent	  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    
    2009-04-28	18:50:53:592	 768	11e8	Setup	Checking for agent SelfUpdate
    
    2009-04-28	18:50:53:593	 768	11e8	Setup	Client version: Core: 7.1.6001.65  Aux: 7.1.6001.65
    
    2009-04-28	18:50:53:612	 768	11e8	Misc	Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    
    2009-04-28	18:50:53:620	 768	11e8	Misc	 Microsoft signed: Yes
    
    2009-04-28	18:50:53:639	 768	11e8	Misc	Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    
    2009-04-28	18:50:53:642	 768	11e8	Misc	 Microsoft signed: Yes
    
    2009-04-28	18:50:53:686	 768	11e8	Setup	Determining whether a new setup handler needs to be downloaded
    
    2009-04-28	18:50:53:686	 768	11e8	Setup	SelfUpdate handler is not found.  It will be downloaded
    
    2009-04-28	18:50:53:686	 768	11e8	Setup	Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.1.6001.65"
    
    2009-04-28	18:50:53:996	 768	11e8	Setup	Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.1.6001.65" is already installed.
    
    2009-04-28	18:50:53:996	 768	11e8	Setup	Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.1.6001.65"
    
    2009-04-28	18:50:54:018	 768	11e8	Setup	Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.1.6001.65" is already installed.
    
    2009-04-28	18:50:54:018	 768	11e8	Setup	Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.1.6001.65"
    
    2009-04-28	18:50:54:052	 768	11e8	Setup	Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.1.6001.65" is already installed.
    
    2009-04-28	18:50:54:052	 768	11e8	Setup	SelfUpdate check completed.  SelfUpdate is NOT required.
    
    2009-04-28	18:50:54:854	 768	11e8	PT	+++++++++++  PT: Synchronizing server updates  +++++++++++
    
    2009-04-28	18:50:54:854	 768	11e8	PT	  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://server:8530/ClientWebService/client.asmx
    
    2009-04-28	18:50:54:890	 768	11e8	PT	WARNING: Cached cookie has expired or new PID is available
    
    2009-04-28	18:50:54:891	 768	11e8	PT	Initializing simple targeting cookie, clientId = 34a8be7e-899a-4138-ac40-048e44066f0c, target group = , DNS name = client
    
    2009-04-28	18:50:54:891	 768	11e8	PT	  Server URL = http://server:8530/SimpleAuthWebService/SimpleAuth.asmx
    
    2009-04-28	18:50:58:013	 768	11e8	PT	WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
    
    2009-04-28	18:50:58:013	 768	11e8	PT	WARNING: SOAP Fault: 0x000190
    
    2009-04-28	18:50:58:013	 768	11e8	PT	WARNING:     faultstring:Fault occurred
    
    2009-04-28	18:50:58:013	 768	11e8	PT	WARNING:     ErrorCode:InternalServerError(5)
    
    2009-04-28	18:50:58:013	 768	11e8	PT	WARNING:     Message:(null)
    
    2009-04-28	18:50:58:013	 768	11e8	PT	WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    
    2009-04-28	18:50:58:013	 768	11e8	PT	WARNING:     ID:5c343eab-48b4-4b6c-8686-6092f5c738ed
    
    2009-04-28	18:50:58:013	 768	11e8	PT	WARNING: PTError: 0x8024400e
    
    2009-04-28	18:50:58:013	 768	11e8	PT	WARNING: SyncUpdates_WithRecovery failed.: 0x8024400e
    
    2009-04-28	18:50:58:013	 768	11e8	PT	WARNING: Sync of Updates: 0x8024400e
    
    2009-04-28	18:50:58:013	 768	11e8	PT	WARNING: SyncServerUpdatesInternal failed: 0x8024400e
    
    2009-04-28	18:50:58:013	 768	11e8	Agent	  * WARNING: Failed to synchronize, error = 0x8024400E
    
    2009-04-28	18:50:58:014	 768	11e8	Agent	  * WARNING: Exit code = 0x8024400E
    
    2009-04-28	18:50:58:014	 768	11e8	Agent	*********
    
    2009-04-28	18:50:58:014	 768	11e8	Agent	**  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    
    2009-04-28	18:50:58:014	 768	11e8	Agent	*************
    
    2009-04-28	18:50:58:014	 768	11e8	Agent	WARNING: WU client failed Searching for update with error 0x8024400e
    
    2009-04-28	18:50:58:015	 768	1350	AU	>>##  RESUMED  ## AU: Search for updates [CallId = {D3C0597C-47F4-46BA-8085-FB4051AFB2CD}]
    
    2009-04-28	18:50:58:015	 768	1350	AU	  # WARNING: Search callback failed, result = 0x8024400E
    
    2009-04-28	18:50:58:015	 768	1350	AU	  # WARNING: Failed to find updates with error code 8024400E
    
    2009-04-28	18:50:58:015	 768	1350	AU	#########
    
    2009-04-28	18:50:58:015	 768	1350	AU	##  END  ##  AU: Search for updates [CallId = {D3C0597C-47F4-46BA-8085-FB4051AFB2CD}]
    
    2009-04-28	18:50:58:015	 768	1350	AU	#############
    
    2009-04-28	18:50:58:017	 768	1350	AU	AU setting next detection timeout to 2009-04-28 22:50:58
    
    2009-04-28	18:51:03:014	 768	11e8	Report	REPORT EVENT: {E85E0D73-E1E8-480C-AE2C-ED8BD9DA0BDD}	2009-04-28 18:50:58:014+0100	1	148	101	{00000000-0000-0000-0000-000000000000}	0	8024400e	AutomaticUpdates	Failure	Software Synchronization	Windows Update Client failed to detect with error 0x8024400e.
    So, error code 0x8024400e.
    I did the requisite googling. I disabled WU and BITS on the client, deleted SoftwareUpdates. No dice.
    I found http://support.microsoft.com/kb/954960 and checked, the .66 version of the client dll is installed on the server so that update has been applied. I tried the workaround steps anyway, made no difference.  I can't do anything with the office 2003 sp update since it has expirde. Office 2003 isn't installed on my client machine and has never been.

    There is an error in the SoftwareDistribution.log file on the server but it is not the error mentioned in that KB article, the KB article lists an ArgumentException while i'm getting a NullReferenceException, here have some more log:

    09-04-28 18:04:07.921 UTC	Error	w3wp.6	ClientImplementation.SyncUpdates	System.NullReferenceException: Object reference not set to an instance of an object.
    
       at Microsoft.UpdateServices.Internal.DataAccessCache.GetCoreUpdateXml(Int32[] revisionIds, DataAccess da, Int64 maxXmlPerRequest)
    
       at Microsoft.UpdateServices.Internal.ClientImplementation.GetSyncInfo(DataAccess dataAccess, Hashtable stateTable, Hashtable deploymentTable, Boolean haveGroupsChanged, Boolean doChunking)
    
       at Microsoft.UpdateServices.Internal.ClientImplementation.SoftwareSync(DataAccess dataAccess, UnencryptedCookieData cookieData, Int32[] installedNonLeafUpdateIds, Int32[] leafUpdateIds, Boolean haveGroupsChanged, Boolean expressQuery)
    
       at Microsoft.UpdateServices.Internal.ClientImplementation.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
    
       at Microsoft.UpdateServices.Internal.ClientImplementation.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
    
       at Microsoft.UpdateServices.Internal.Client.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
    
       at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
    
       at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
    
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
    
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
    
       at System.Web.Services.Protocols.LogicalMethodInfo.Invoke(Object target, Object[] values)
    
       at System.Web.Services.Protocols.WebServiceHandler.Invoke()
    
       at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()
    
       at System.Web.Services.Protocols.SyncSessionlessHandler.ProcessRequest(HttpContext context)
    
       at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
    
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
    
       at System.Web.HttpApplication.ApplicationStepManager.ResumeSteps(Exception error)
    
       at System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)
    
       at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
    
       at System.Web.HttpRuntime.ProcessRequestNoDemand(HttpWorkerRequest wr)
    
       at System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType)
    
    2009-04-28 18:04:07.921 UTC	Warning	w3wp.6	SoapUtilities.CreateException	ThrowException: actor = http://server:8530/ClientWebService/client.asmx, ID=7f29f181-b09c-4c20-abc2-9718056a845e, ErrorCode=InternalServerError, Message=, Client=?
    • Edited by Wraith2 Tuesday, April 28, 2009 7:10 PM clarification and correction
    Tuesday, April 28, 2009 6:12 PM
  • > 2009-04-28 18:50:54:891 768 11e8 PT Initializing simple targeting cookie, clientId = 34a8be7e-899a-4138-ac40-048e44066f0c, target group = , DNS name = client
    > 2009-04-28 18:50:54:891 768 11e8 PT   Server URL = http://server:8530/SimpleAuthWebService/SimpleAuth.asmx
    > 2009-04-28 18:50:58:013 768 11e8 PT WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
    > 2009-04-28 18:50:58:013 768 11e8 PT WARNING: SOAP Fault: 0x000190
    > 2009-04-28 18:50:58:013 768 11e8 PT WARNING:     faultstring:Fault occurred
    > 2009-04-28 18:50:58:013 768 11e8 PT WARNING:     ErrorCode:InternalServerError(5)

    Okay, so we're in agreement that your core issue is the 0x8024400E error with SOAP Fault: 0x0190, and you've also received the "InternalServerError(5)" marker. I'll reiterate my continuing point that this issue is exactly as described in KB954960. The problem, though, I fear, is that you're so convinced that you don't have this issue, that you've not actually performed the remediation steps as documented in that KB article.


    > There is an error in the SoftwareDistribution.log file on the server but it is not the error mentioned in that KB article, the KB article lists an ArgumentException
    > while i'm getting a NullReferenceException

    There are several problems with this point:

    1. The log snippet from the SoftwareDistribution.log is timestamped 18:04 UTC; and the log snippet from the WindowsUpdate.log is timestamped 18:50 LOCAL. These are not even corresponding events! And even forgiving the possible misinterpretation of the logs as UTC and/or LOCAL time -- they're still 46 minutes apart!

    2. Making a literal comparision of the log snippets without actually reading the text of the KB article. The KB article states: a message that resembles the following message and the key point in making the comparison to the log entries in the SoftwareDistribution.log (other than properly converting for the differences between LOCAL time and UTC time, is to match the ID as expressly stated in this text from the KB article: To locate this message, search the WSUS server for the ID that is obtained from the client log.


    > I found http://support.microsoft.com/kb/954960 and checked, the .66 version of the client dll is installed on the server so that update has been applied

    Noted. I would suggest reinstalling the actual KB update just to make sure it was performed correctly. Of course, it should also be noted that this 'update' is included in WSUS 3 SP1, but it's impact in an unsupported environment is difficult to speculate on.


    > I can't do anything with the office 2003 sp update since it has expirde. Office 2003 isn't installed on my client machine and has never been.

    The issue in KB954960 has absolutely nothing to do with whether Office 2003 is installed anywhere or not. This problem is caused by a defect in the WSUS metadata database. Furthemore, Office 2003 Service Pack 1 Update ID: D359F493-0AAD-43FA-AF5C-6763326CD98F is NOT an expired update. It is a superseded update (by Office 2003 Service Pack 2), but the issue is caused by the presence of the update on the server, not it's status, or lack thereof.

    As documented in the KB article, the procedure that should be performed (as a workaround to upgrading to WSUS 3.0 SP1). I would suggest performing the procedure even if you don't think you need to -- there's nothing to loose by performing it, and you just might resolve the issue.

    1. Confirm that the update is DECLINED. If the update is not declined, then DECLINE the update.
    2. APPROVE the update for installation. To do this, right-click the update, click Approve, and then click OK. Do not make any changes to the approval settings in the Approve Updates dialog box.
    3. DECLINE the update.


    It also might be worth installing a clean WSUS3SP1 on Win2003SP2 and see if you can replicate this issue on a supported platform.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Wednesday, April 29, 2009 2:44 AM
    Moderator
  • >> Okay, so we're in agreement that your core issue is the 0x8024400E error with SOAP Fault: 0x0190, and you've also received the "InternalServerError(5)" marker.

    It is my current issue. The original issue was not resolved it merely went away when i gave up on trying to migrate approvals from my existing server.

    >>I'll reiterate my continuing point that this issue is exactly as described in KB954960.
    >> The problem, though, I fear, is that you're so convinced that you don't have this issue,
    >> that you've not actually performed the remediation steps as documented in that KB article.

    You're wrong.
    I tried the workaround steps detailed in the KB article. Then i tested, it failed.
    I applied the patch linked to in the KB article even though i had checked that it was already applied. I tested, it failed.
    The result of this testing was that i had quite a number of the same exception messages in both server and client logs which is why the timestamps on the logs i posted don't match.

    >> Making a literal comparision of the log snippets without actually reading the text of the KB article.
    ArgumentException and NullReferenceException are quite different things. An argument exception is typically thrown by a programmer, a nullref is typically thrown by the runtime. The former is mostly a guard, the second is an error. This distinction in the context of the log message could be quite important and you should know this. The distinction also makes the otherwise similar looking error message different to the one described in the article, a conclusion which is supported by the fact that the listed fixes for the problem detailed in the article fail to make any difference to this problem.

    >> Office 2003 Service Pack 1 Update ID: D359F493-0AAD-43FA-AF5C-6763326CD98F is NOT an expired update.
    >>It is a superseded update

    It is both superceeded and expired. I could argue with you but i'll just provide a screenshot because it is becoming clear that you doubt my ability to do simple tasks like reading correctly.
    http://picasaweb.google.com/wraith2/Misc#5330175826238112962

    >> It also might be worth installing a clean WSUS3SP1 on Win2003SP2 and see if you can replicate this issue
    >> on a supported platform.

    Yes i agree it might be worthwhile but if i had a windows2003sp2 system to install wsus on do you not think i would have done so? I don't, if i had i would have used it, i didn't because i haven't.

    The fact that wsus3 does not support WHS may have less to do with the fact that it doesn't work and more to do with the fact that WSUS3 predates WHS' existance by several years. It isn't unreasonable to expect that products that don't exist don't make it into the supported lists for such things.

    On the other hand windows 2003 small business server is on the supported list, and so is supported. Windows Home Server is built on top of Windows 2003 small business server, you can prove this using msinfo32 in the system and seeing that it reports itself as windows 2003 small business server.

    Now i agree that there might be some configuration or patch that is present on whs that isn't on sbs which causes problems which is why having tried to fix this myself i'm here asking questions of people who i thought would be able to help. I've a reasonable idea how wsus works having used and maintained it from sus through wsus2, 3 isn't radically different from 2 in the method of network communication, the databases look pretty similar at a casual glance, the client systems haven't changed. In short apart from your cries of "Not supported!" have you any factual basis for your implication that wsus3 will not work on WHS (a position seemingly refuted by the guide i linked to in my earlier posts on how to install wsus3 on whs) other than that you haven't eve tried it.

    Now, lets have yet more logs shall we? i've been very careful to make sure that the times match this time, the apparent difference is to to the fact that the UK is currenty in BST which is +1 from GMT. The seconds don't quite match up but i'm not about to go and configure ntp just yet, they're close enough to be clearly the same event.
    First the client:


    2009-04-29 18:46:02:386  388 13f8 Misc ===========  Logging initialized (build: 7.1.6001.65, tz: +0100)  ===========
    2009-04-29 18:46:02:386  388 13f8 Misc   = Process: C:\Windows\system32\svchost.exe
    2009-04-29 18:46:02:386  388 13f8 Misc   = Module: c:\windows\system32\wuaueng.dll
    2009-04-29 18:46:02:386  388 13f8 Service *************
    2009-04-29 18:46:02:386  388 13f8 Service ** START **  Service: Service startup
    2009-04-29 18:46:02:386  388 13f8 Service *********
    2009-04-29 18:46:02:389  388 13f8 Agent   * WU client version 7.1.6001.65
    2009-04-29 18:46:02:389  388 13f8 Agent   * Base directory: C:\Windows\SoftwareDistribution
    2009-04-29 18:46:02:389  388 13f8 Agent   * Access type: No proxy
    2009-04-29 18:46:02:390  388 13f8 Agent   * Network state: Connected
    2009-04-29 18:46:18:647  388 dd0 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2009-04-29 18:46:18:648  388 dd0 Agent ***********  Agent: Initializing global settings cache  ***********
    2009-04-29 18:46:18:648  388 dd0 Agent   * WSUS server: http://server:8530
    2009-04-29 18:46:18:648  388 dd0 Agent   * WSUS status server: http://server:8530
    2009-04-29 18:46:18:648  388 dd0 Agent   * Target group: (Unassigned Computers)
    2009-04-29 18:46:18:648  388 dd0 Agent   * Windows Update access disabled: No
    2009-04-29 18:46:18:648  388 dd0 DnldMgr Download manager restoring 0 downloads
    2009-04-29 18:46:18:649  388 dd0 AU ###########  AU: Initializing Automatic Updates  ###########
    2009-04-29 18:46:18:649  388 dd0 AU   # WSUS server: http://server:8530
    2009-04-29 18:46:18:649  388 dd0 AU   # Detection frequency: 22
    2009-04-29 18:46:18:649  388 dd0 AU   # Approval type: Pre-download notify (User preference)
    2009-04-29 18:46:18:651  388 dd0 AU AU finished delayed initialization
    2009-04-29 18:46:18:651  388 dd0 AU Triggering AU detection through DetectNow API
    2009-04-29 18:46:18:651  388 dd0 AU Triggering Online detection (non-interactive)
    2009-04-29 18:46:18:803  388 13f8 Report ***********  Report: Initializing static reporting data  ***********
    2009-04-29 18:46:18:803  388 13f8 Report   * OS Version = 6.0.6001.1.0.65792
    2009-04-29 18:46:18:804  388 13f8 Report   * OS Product Type = 0x00000001
    2009-04-29 18:46:18:840  388 13f8 Report   * Computer Brand = System manufacturer
    2009-04-29 18:46:18:840  388 13f8 Report   * Computer Model = P5Q-PRO
    2009-04-29 18:46:18:842  388 13f8 Report   * Bios Revision = 0506  
    2009-04-29 18:46:18:842  388 13f8 Report   * Bios Name = BIOS Date: 05/26/08 00:51:17 Ver: 08.00.14
    2009-04-29 18:46:18:842  388 13f8 Report   * Bios Release Date = 2008-05-26T00:00:00
    2009-04-29 18:46:18:842  388 13f8 Report   * Locale ID = 2057
    2009-04-29 18:46:18:843  388 13f8 AU #############
    2009-04-29 18:46:18:843  388 13f8 AU ## START ##  AU: Search for updates
    2009-04-29 18:46:18:843  388 13f8 AU #########
    2009-04-29 18:46:18:845  388 13f8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {99F24357-69DB-428D-BB62-0F359A57363F}]
    2009-04-29 18:46:19:133  388 12cc Agent *************
    2009-04-29 18:46:19:133  388 12cc Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-04-29 18:46:19:133  388 12cc Agent *********
    2009-04-29 18:46:19:133  388 12cc Agent   * Online = Yes; Ignore download priority = No
    2009-04-29 18:46:19:133  388 12cc 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"
    2009-04-29 18:46:19:133  388 12cc Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2009-04-29 18:46:19:133  388 12cc Setup Checking for agent SelfUpdate
    2009-04-29 18:46:19:133  388 12cc Setup Client version: Core: 7.1.6001.65  Aux: 7.1.6001.65
    2009-04-29 18:46:19:134  388 12cc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2009-04-29 18:46:19:140  388 12cc Misc  Microsoft signed: Yes
    2009-04-29 18:46:21:401  388 12cc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2009-04-29 18:46:21:404  388 12cc Misc  Microsoft signed: Yes
    2009-04-29 18:46:21:406  388 12cc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2009-04-29 18:46:21:409  388 12cc Misc  Microsoft signed: Yes
    2009-04-29 18:46:21:412  388 12cc Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2009-04-29 18:46:21:414  388 12cc Misc  Microsoft signed: Yes
    2009-04-29 18:46:21:456  388 12cc Setup Determining whether a new setup handler needs to be downloaded
    2009-04-29 18:46:21:456  388 12cc Setup SelfUpdate handler is not found.  It will be downloaded
    2009-04-29 18:46:21:457  388 12cc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.1.6001.65"
    2009-04-29 18:46:21:459  388 12cc Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.1.6001.65" is already installed.
    2009-04-29 18:46:21:460  388 12cc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.1.6001.65"
    2009-04-29 18:46:21:481  388 12cc Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.1.6001.65" is already installed.
    2009-04-29 18:46:21:481  388 12cc Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.1.6001.65"
    2009-04-29 18:46:21:514  388 12cc Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.1.6001.65" is already installed.
    2009-04-29 18:46:21:514  388 12cc Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2009-04-29 18:46:23:476  388 12cc PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2009-04-29 18:46:23:476  388 12cc PT   + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://server:8530/ClientWebService/client.asmx
    2009-04-29 18:46:24:780  388 12cc PT WARNING: SyncUpdates failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
    2009-04-29 18:46:24:780  388 12cc PT WARNING: SOAP Fault: 0x000190
    2009-04-29 18:46:24:780  388 12cc PT WARNING:     faultstring:Fault occurred
    2009-04-29 18:46:24:780  388 12cc PT WARNING:     ErrorCode:InternalServerError(5)
    2009-04-29 18:46:24:780  388 12cc PT WARNING:     Message:(null)
    2009-04-29 18:46:24:781  388 12cc PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
    2009-04-29 18:46:24:781  388 12cc PT WARNING:     ID:4bf7a34f-3581-4eda-b333-693c2728433a
    2009-04-29 18:46:24:781  388 12cc PT WARNING: PTError: 0x8024400e
    2009-04-29 18:46:24:781  388 12cc PT WARNING: SyncUpdates_WithRecovery failed.: 0x8024400e
    2009-04-29 18:46:24:781  388 12cc PT WARNING: Sync of Updates: 0x8024400e
    2009-04-29 18:46:24:781  388 12cc PT WARNING: SyncServerUpdatesInternal failed: 0x8024400e
    2009-04-29 18:46:24:781  388 12cc Agent   * WARNING: Failed to synchronize, error = 0x8024400E
    2009-04-29 18:46:24:788  388 12cc Agent   * WARNING: Exit code = 0x8024400E
    2009-04-29 18:46:24:788  388 12cc Agent *********
    2009-04-29 18:46:24:788  388 12cc Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2009-04-29 18:46:24:788  388 12cc Agent *************
    2009-04-29 18:46:24:788  388 12cc Agent WARNING: WU client failed Searching for update with error 0x8024400e
    2009-04-29 18:46:24:790  388 f80 AU >>##  RESUMED  ## AU: Search for updates [CallId = {99F24357-69DB-428D-BB62-0F359A57363F}]
    2009-04-29 18:46:24:790  388 f80 AU   # WARNING: Search callback failed, result = 0x8024400E
    2009-04-29 18:46:24:790  388 f80 AU   # WARNING: Failed to find updates with error code 8024400E
    2009-04-29 18:46:24:790  388 f80 AU #########
    2009-04-29 18:46:24:790  388 f80 AU ##  END  ##  AU: Search for updates [CallId = {99F24357-69DB-428D-BB62-0F359A57363F}]
    2009-04-29 18:46:24:790  388 f80 AU #############
    2009-04-29 18:46:24:790  388 f80 AU AU setting next detection timeout to 2009-04-29 22:46:24
    2009-04-29 18:46:29:788  388 12cc Report REPORT EVENT: {11D60853-6264-4C38-88E6-B9D9A983D17D} 2009-04-29 18:46:24:788+0100 1 148 101 {00000000-0000-0000-0000-000000000000} 0 8024400e AutomaticUpdates Failure Software Synchronization Windows Update Client failed to detect with error 0x8024400e.

     

    And now the server:


    2009-04-29 17:45:46.386 UTC Info WsusService.5 ThreadEntry ThreadHelper.ThreadStart
    2009-04-29 17:45:46.386 UTC Info WsusService.5 SusService.SusServiceStartUpThreadProc WSUS Server Version: 3.1.6001.65
    2009-04-29 17:45:46.589 UTC Info WsusService.5 SusService.CleanUpIntermediateFileDownload CleanupIntermediateFileDownload
    2009-04-29 17:45:46.980 UTC Info WsusService.7 ThreadEntry ThreadHelper.ThreadStart
    2009-04-29 17:45:46.980 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: CatalogSyncAgent, EventInfo: Startup
    2009-04-29 17:45:46.980 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ContentSyncAgent, EventInfo: Startup
    2009-04-29 17:45:46.980 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: StateMachineReset, EventInfo: Startup
    2009-04-29 17:45:46.995 UTC Info WsusService.9 ThreadEntry ThreadHelper.ThreadStart
    2009-04-29 17:45:46.995 UTC Info WsusService.9 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: CatalogSyncAgent
    2009-04-29 17:45:46.995 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: RollupAgent, EventInfo: Startup
    2009-04-29 17:45:46.995 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: EmailNotificationAgent, EventInfo: Startup
    2009-04-29 17:45:46.995 UTC Info WsusService.9 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ContentSyncAgent
    2009-04-29 17:45:46.995 UTC Info WsusService.9 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: StateMachineReset
    2009-04-29 17:45:47.011 UTC Info WsusService.9 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: RollupAgent
    2009-04-29 17:45:47.027 UTC Info WsusService.12 ThreadEntry ThreadHelper.ThreadStart
    2009-04-29 17:45:47.027 UTC Info WsusService.12 ResetStateMachineAgent.WakeUpWorkerThreadProc State Machine Reset Agent Starting
    2009-04-29 17:45:47.027 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: ConfigurationChange, EventInfo: ConfigurationChange
    2009-04-29 17:45:47.042 UTC Info WsusService.10 ThreadEntry ThreadHelper.ThreadStart
    2009-04-29 17:45:47.042 UTC Info WsusService.10 CatalogSyncAgent.HandleCatalogSyncStateCorrection Handling systemStartup work...
    2009-04-29 17:45:47.042 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: DeploymentChange, EventInfo: DeploymentChange
    2009-04-29 17:45:47.042 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: FileLocationChange, EventInfo: FileLocationChange
    2009-04-29 17:45:47.042 UTC Info WsusService.11 ThreadEntry ThreadHelper.ThreadStart
    2009-04-29 17:45:47.042 UTC Info WsusService.11 SusEventDispatcher.RegisterEventHandler RegisterEventHandler called for NotificationEventName: ConfigurationChange
    2009-04-29 17:45:47.042 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: HardwareIDChange, EventInfo: HardwareIDChange
    2009-04-29 17:45:47.058 UTC Info WsusService.10 CatalogSyncAgent.HandleCatalogSyncStateCorrection Finished systemStartup work.
    2009-04-29 17:45:47.058 UTC Info WsusService.7 SusEventDispatcher.TriggerEvent TriggerEvent called for NotificationEventName: LanguageChange, EventInfo: LanguageChange
    2009-04-29 17:45:47.074 UTC Info WsusService.9 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: EmailNotificationAgent
    2009-04-29 17:45:47.089 UTC Info WsusService.9 SusEventDispatcher.DispatchManagerWorkerThreadProc DispatchManager Worker Thread Processing NotificationEvent: ConfigurationChange
    2009-04-29 17:45:47.089 UTC Info WsusService.5 SusService.SusServiceStartUpThreadProc EventId=501,Type=Information,Category=WsusService,Message=Update Services Service Started
    2009-04-29 17:45:47.105 UTC Info WsusService.10 CatalogSyncAgent.UpdateServerHealthStatusBasedOnError ServerHealth: Updating Server Health for Component: CatalogSyncAgent, Marking as Not Running
    2009-04-29 17:45:47.120 UTC Info WsusService.17 ThreadEntry ThreadHelper.ThreadStart
    2009-04-29 17:45:47.120 UTC Info WsusService.17 EmailNotificationAgent.WakeUpWorkerThreadProc Email Notification Agent Starting
    2009-04-29 17:45:47.120 UTC Info WsusService.12 ResetStateMachineAgent.WakeUpWorkerThreadProc State Machine Reset Agent Finished
    2009-04-29 17:45:47.167 UTC Info WsusService.11 EventLogEventReporter.ReportEvent EventId=361,Type=Information,Category=Synchronization,Message=Content synchronization started.
    2009-04-29 17:45:47.183 UTC Info WsusService.17 EmailNotificationAgent.WakeUpWorkerThreadProc Email Notification Agent Finished
    2009-04-29 17:45:47.761 UTC Info WsusService.11 ContentSyncAgent.WakeUpWorkerThreadProc ServerHealth: Updating Server Health for Component: ContentSyncAgent Running, Marking as Running
    2009-04-29 17:45:47.855 UTC Info WsusService.11 ContentSyncAgent.WakeUpWorkerThreadProc ContentSyncAgent found no more Jobs, thread exitting
    2009-04-29 17:45:47.855 UTC Info WsusService.11 EventLogEventReporter.ReportEvent EventId=363,Type=Information,Category=Synchronization,Message=Content synchronization succeeded.
    2009-04-29 17:45:47.886 UTC Info WsusService.11 ContentSyncAgent.WakeUpWorkerThreadProc ServerHealth: Updating Server Health for Component: ContentSyncAgent, Marking as Not Running
    2009-04-29 17:46:30.308 UTC Error w3wp.1 ClientImplementation.SyncUpdates System.NullReferenceException: Object reference not set to an instance of an object.
       at Microsoft.UpdateServices.Internal.DataAccessCache.GetCoreUpdateXml(Int32[] revisionIds, DataAccess da, Int64 maxXmlPerRequest)
       at Microsoft.UpdateServices.Internal.ClientImplementation.GetSyncInfo(DataAccess dataAccess, Hashtable stateTable, Hashtable deploymentTable, Boolean haveGroupsChanged, Boolean doChunking)
       at Microsoft.UpdateServices.Internal.ClientImplementation.SoftwareSync(DataAccess dataAccess, UnencryptedCookieData cookieData, Int32[] installedNonLeafUpdateIds, Int32[] leafUpdateIds, Boolean haveGroupsChanged, Boolean expressQuery)
       at Microsoft.UpdateServices.Internal.ClientImplementation.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
       at Microsoft.UpdateServices.Internal.ClientImplementation.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
       at Microsoft.UpdateServices.Internal.Client.SyncUpdates(Cookie cookie, SyncUpdateParameters parameters)
       at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
       at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
       at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
       at System.Web.Services.Protocols.LogicalMethodInfo.Invoke(Object target, Object[] values)
       at System.Web.Services.Protocols.WebServiceHandler.Invoke()
       at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()
       at System.Web.Services.Protocols.SyncSessionlessHandler.ProcessRequest(HttpContext context)
       at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
       at System.Web.HttpApplication.ApplicationStepManager.ResumeSteps(Exception error)
       at System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)
       at System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
       at System.Web.HttpRuntime.ProcessRequestNoDemand(HttpWorkerRequest wr)
       at System.Web.Hosting.ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType)
    2009-04-29 17:46:30.308 UTC Warning w3wp.1 SoapUtilities.CreateException ThrowException: actor = http://server:8530/ClientWebService/client.asmx, ID=4bf7a34f-3581-4eda-b333-693c2728433a, ErrorCode=InternalServerError, Message=, Client=?

     

    As you can see the errors are still there. All the steps provided to rectify this situation have been taken short of using a product i don't own.

    Do you have any idea of how to solve this without just reinstalling and hoping it doesn't happen again?

    Wednesday, April 29, 2009 6:25 PM
  • >> Office 2003 Service Pack 1 Update ID: D359F493-0AAD-43FA-AF5C-6763326CD98F is NOT an expired update.
    >>It is a superseded update

    It is both superceeded and expired. I could argue with you but i'll just provide a screenshot because it is becoming clear that you doubt my ability to do simple tasks like reading correctly.
    http://picasaweb.google.com/wraith2/Misc#5330175826238112962

    I stand corrected on this point. The update is expired. I'm using a different interface and the ribbon warning for expiration is not visible to me.

    Normally this type of update should not be expired, and particularly so since it's the subject of an active resolution procedure that requires the update status to be changed.

    The expiration certainly does interfere with trying to decline/approve/decline the update. As it so happens, I'm currently in a conversation with the WSUS team about these various svchost.exe issues, and their several resolutions. I'll see if I can get some useful feedback about this particular situation.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Wednesday, April 29, 2009 10:30 PM
    Moderator
  • >> Making a literal comparision of the log snippets without actually reading the text of the KB article.
    ArgumentException and NullReferenceException are quite different things. An argument exception is typically thrown by a programmer, a nullref is typically thrown by the runtime. The former is mostly a guard, the second is an error. This distinction in the context of the log message could be quite important and you should know this. The distinction also makes the otherwise similar looking error message different to the one described in the article, a conclusion which is supported by the fact that the listed fixes for the problem detailed in the article fail to make any difference to this problem.


    This is really pointless argument, given that the two log snippets you posted were timed several minutes apart from one another (my original estimate was more, since I didn't know your exact time zone, but I was very confident that 18:50LOCAL != 18:04GMT.


    Now looking at your new set of log entries, which are ~1 hour apart

    > 2009-04-29 17:46:30.308 UTC Error w3wp.1 ClientImplementation.SyncUpdates System.NullReferenceException: Object reference not set to an instance of an object.

    I can now conclude that your 0x8024400E error is being logged as a NullReferenceException.

    Since you so eloquently described the difference between a NullReferenceException and an ArgumentException, it may well be that the current situation you're encountering has nothing at all to do with the existing, documented issues and resolutions. But, at least now, we have some empirical, consistent, information with which we can base that conclusion upon.

    So... what do you propose? There's no known resolution for your issue, because it's never before been encountered or documented, to my knowledge. My recommendation, in normal circumstances, would be to place a call to Product Support Services, but that would require that your enviroment is installed in a supported environment.

    You claimed in an earlier post to be a developer, yet you don't have a copy of a six-year old operating system to test this scenario against? (Ironically, Evaluation Editions of Windows Server 2003 Enterprise Edition are available for free... might I suggest downloading one?) -- and ultimately, your original stated purpose was to "Upgrade to WSUS v3), and doing that will require a licensed installation of Windows Server 2003 (Standard or Enterprise). Truly, until you build a supported environment, we're going to do nothing but spin our wheels in this thread.






    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Wednesday, April 29, 2009 10:35 PM
    Moderator
  • If you re-read my post i clearly explained why there is a difference in the times in the logs. One uses UTC the other uses local time. The fact that the original log entries were minutes apart didn't change their contents, the same system produced the same results based on the same actions quite a number of times.

    I don't claim to be a developer. I am a developer. That doesn't make me a rich developer and it doesn't mean i've got operating systems lying around unused or available to me. If you have that's nice for you but you'd be better off assuming that not everyone has your resources.

    >> My recommendation, in normal circumstances, would be to place a call to Product Support Services, but
    >> that would require that your enviroment is installed in a supported environment.

    You still haven't given me any reason for your assumption that wsus3 couldn't work on whs. You've made it very clear that it isn't supported but not being supported doesn't mean it won't work, do you have any technical reason at all to conclude that it shouldn't work? I've explained why i think it will work.

    [edit]
    It started working last night when i found that an ssl port exception had been disabled on the firewall. With that exception enabled i managed to get both the server machine itself and my vista64 client machine to sync correctly. It seemed to be fixed. I went to bed, went to work and came back today to find that again i can't update. The server was left on as servers generally are, it wasn't rebooted powered down or tampered with at all during the day because there was no-one around to do so. In short it appeared to be fixed and then today isn't. If it weren't also failing on the server machine again (where it had started to work) i would suspect that my client was somehow to blame.

    This really is getting rather annoying. Have you anything that might actually help apart from telling me that my platform isn't supported or to try and operating system i don't own?
    • Edited by Wraith2 Thursday, April 30, 2009 6:12 PM it went wrong again
    Thursday, April 30, 2009 12:03 AM

  • This really is getting rather annoying. Have you anything that might actually help apart from telling me that my platform isn't supported or to try and operating system i don't own?

    No. Those would be the only two viable solutions to your issue as presented.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    Friday, June 5, 2009 3:32 PM
    Moderator