Re: [Error number: 0x80244019]

From: Robert Aldwinckle (robald_at_techemail.com)
Date: 09/22/04

Next message: Kim: "Win 98 machines given XP Updates"
Previous message: oscar: "RE: GPO To block XP SP2 question"
In reply to: Mike C. - Columbus, OH: "Re: [Error number: 0x80244019]"
Messages sorted by: [ date ] [ thread ]

Date: Wed, 22 Sep 2004 14:37:20 -0400

According to Lucy's reply in this thread
the Subject error means there is an HTTP 404 error.

If so, you could perhaps investigate that by taking a packet trace
of an update attempt (e.g. to find out what URL is being used
which causes that error.)

However, I suspect this could be yet another odd symptom
of having a corrupted SoftwareDistribution subdirectory;
so before doing any diagnosis of your current symptom
I would follow Torgeir's suggestion of cleaning up
all the subdirectories he mentions.

To start getting a handle on what causes these symptoms
please tell us if you had WUV5 originally, as that would
explain why you would have odd contents which users who
transitioned straight from WUV4 to XPsp2 would not have.

HTH

Robert Aldwinckle

---
"Mike C. - Columbus, OH" <Mike C. - Columbus, OH@discussions.microsoft.com> wrote in message
news:EBD49AFD-7AFA-452F-B49E-16E67247242F@microsoft.com...
>I too am working in a large corporate environment with over 3,700 users and I
> also get the same error message.  I didn't have the option to install or use
> v5 it just shoed up and any attempts to use v4 always direct me to the v5
> area.  I have 4 machines line this.  How can I either undo the v5 setup or
> how can we get a work around?  The patches are gettting further behind every
> day/week. Most all my systems are Windows XP with the erleased version of
> Windows XP Pro SP2.
>
> My two Windows XP Home Edition systems also are using v5 of Windows Update,
> but they don't experience this error.  I didn't have a choice on the upgrade
> except to have selected No when the installation screen showed up, that would
> have negated the notice on the Windows Update screen that recommends
> selecting "Yes" if that dialog box shows up.  It's a catch-22 situation where
> we may not know when to select yes or not to any WU message in the future.
>
> Mike Corson
> DLA
>
> "John" wrote:
>
>> I am also having the same issue using the new isa proxy server, using our
>> select  xp sp1 cd...Has anyone received any help on this?  I am responsible
>> for building disk images for the enterprise and need this resolved A.S.A.P.
>>
>> John
>>
>> "Nathan" wrote:
>>
>> > I too am in a corporate environment (with an ISA proxy) and have SP1a
>> > installed and am getting the 0x80244019 error.  I cannot go back to the v4
>> > site either as it forwards on to v5.
>> >
>> > Nathan
>> >
>> >
>> >
>> > "Michael" wrote:
>> >
>> > > I get this same error number 0x80244019 in a corporate environment with XP
>> > > SP1a installed and windows update goes to v5 automatically.  I don't have SP2
>> > > installed and can't go back to v4 update, v5 showed up one day.
>> > >
>> > > Michael
>> > >
>> > > "Lucy [MSFT]" wrote:
>> > >
>> > > > This is an HTTP 404 - object not found error.
>> > > >
>> > > >
>> > > >
>> > > > PLEASE NOTE- IMPORTANT!!
>> > > > a.. The pre-release versions of Windows Update are for testing purposes
>> > > > only!
>> > > > b.. Please do not depend on the pre-release versions of Windows Update to
>> > > > keep your computer secure and up to date. If you are not a Windows XP SP2
>> > > > Beta program participant, you can keep your computer secure and up to date
>> > > > by visiting the http://v4.windowsupdate.microsoft.com site. If you are part
>> > > > of the Windows XP SP2 Beta program, please take extra care regarding
>> > > > computer security as you will not be able to go back to the Windows Update
>> > > > V4 site.
>> > > >
>> > > > -- 
>> > > > Thanks,
>> > > > Lucy [MSFT]
>> > > >
>> > > > This posting is provided "AS IS" with no warranties, and confers no rights.
>> > > >
>> > > >
>> > > > "Brian P. Adams" <Brian P. Adams@discussions.microsoft.com> wrote in message
>> > > > news:59E5C03E-D5ED-4359-A291-E827DA0BC740@microsoft.com...
>> > > > > The error description I get is "Windows Update has encountered an error
>> > > > and cannot display the requested page. You may find the following resources
>> > > > helpful in resolving the problem:"
>> > > > >
>> > > > > The entire transaction set in the WindowsUpdate.log file follows:
>> > > > >
>> > > > > 2004-07-19 11:02:06-0400 1204 1990 ISusInternal API failed
>> > > > CClientCallRecorder::DisconnectCall with error 0x8024000c
>> > > > > 2004-07-19 11:02:06-0400 6872 1ab4 ISusInternal::DisconnectCall failed,
>> > > > hr=8024000C
>> > > > > 2004-07-19 11:03:51-0400 6956 1ad8 Checking for different Redirector at:
>> > > > http://download.windowsupdate.com/msdownload/update/v5/redir/wuredir.cab
>> > > > > 2004-07-19 11:03:53-0400 6956 1ad8 WinInet: Server file is not newer.
>> > > > Skipping download.
>> > > > > 2004-07-19 11:03:53-0400 6956 1ad8 Successfully refreshed Redirector cab.
>> > > > > 2004-07-19 11:03:53-0400 6956 1ad8 WinInet: Successfully downloaded
>> > > > http://v5.windowsupdate.microsoft.com/SelfUpdate/wuident.cab to file
>> > > > C:\WINNT\SoftwareDistribution\WebSetup\wuident.cab
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 WinInet: Download speed is 44661
>> > > > bytes/sec
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 WinInet: Successfully downloaded
>> > > > http://v5.windowsupdate.microsoft.com/SelfUpdate/AU/x86/W2K/en/wusetup.cab
>> > > > to file C:\WINNT\SoftwareDistribution\WebSetup\wusetup.cab
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Loading inf file
>> > > > C:\WINNT\SoftwareDistribution\WebSetup\wusetup.inf
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Section name: cdm: Index: 0
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Section name: iuengine: Index: 1
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Section name: wuapi: Index: 2
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Section name: wuauclt: Index: 3
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Section name: wuauclt1: Index: 4
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Section name: wuaucpl: Index: 5
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Section name: wuaueng_WebSetup: Index:
>> > > > 6
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Section name: wuaueng1: Index: 7
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Section name: wuauserv_WebSetup: Index:
>> > > > 8
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Section name: wucltui: Index: 9
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Section name: wups: Index: 10
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Section name: msxml3r: Index: 11
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Section name: msxml3: Index: 12
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Required Version for binary
>> > > > C:\WINNT\system32\cdm.dll is: 5,5,3790,2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Binary: C:\WINNT\system32\cdm.dll:
>> > > > Target version: 5.5.3790.2163 Required: 5.5.3790.2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Required Version for binary
>> > > > C:\WINNT\system32\iuengine.dll is: 5,4,3790,2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Binary: C:\WINNT\system32\iuengine.dll:
>> > > > Target version: 5.4.3790.2163 Required: 5.4.3790.2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Required Version for binary
>> > > > C:\WINNT\system32\wuapi.dll is: 5,4,3790,2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Binary: C:\WINNT\system32\wuapi.dll:
>> > > > Target version: 5.4.3790.2163 Required: 5.4.3790.2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Required Version for binary
>> > > > C:\WINNT\system32\wuauclt.exe is: 5,4,3790,2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Binary: C:\WINNT\system32\wuauclt.exe:
>> > > > Target version: 5.4.3790.2163 Required: 5.4.3790.2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Required Version for binary
>> > > > C:\WINNT\system32\wuauclt1.exe is: 5,4,3790,2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Binary: C:\WINNT\system32\wuauclt1.exe:
>> > > > Target version: 5.4.3790.2163 Required: 5.4.3790.2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Required Version for binary
>> > > > C:\WINNT\system32\wuaucpl.cpl is: 5,4,3790,2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Binary: C:\WINNT\system32\wuaucpl.cpl:
>> > > > Target version: 5.4.3790.2163 Required: 5.4.3790.2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Required Version for binary
>> > > > C:\WINNT\system32\wuaueng.dll is: 5,4,3790,2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Binary: C:\WINNT\system32\wuaueng.dll:
>> > > > Target version: 5.4.3790.2163 Required: 5.4.3790.2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Required Version for binary
>> > > > C:\WINNT\system32\wuaueng1.dll is: 5,4,3790,2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Binary: C:\WINNT\system32\wuaueng1.dll:
>> > > > Target version: 5.4.3790.2163 Required: 5.4.3790.2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Required Version for binary
>> > > > C:\WINNT\system32\wucltui.dll is: 5,4,3790,2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Binary: C:\WINNT\system32\wucltui.dll:
>> > > > Target version: 5.4.3790.2163 Required: 5.4.3790.2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Required Version for binary
>> > > > C:\WINNT\system32\wups.dll is: 5,4,3790,2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 Binary: C:\WINNT\system32\wups.dll:
>> > > > Target version: 5.4.3790.2163 Required: 5.4.3790.2163
>> > > > > 2004-07-19 11:03:54-0400 6956 1ad8 AU is forbidden; setting AU approval
>> > > > type to 'disabled'.
>> > > > > 2004-07-19 11:03:57-0400 1204 1af8 WU client succeeds
>> > > > CClientCallRecorder::BeginFindUpdates from WindowsUpdate with call id
>> > > > {4C36359C-2540-4AA0-AB8D-A798FDB62959}
>> > > > > 2004-07-19 11:03:57-0400 1204 19f4 WU client executing call
>> > > > {4C36359C-2540-4AA0-AB8D-A798FDB62959} of type Search Call
>> > > > > 2004-07-19 11:03:59-0400 1204 19f4 PT: Using serverID
>> > > > {9482F4B4-E343-43B6-B170-9A65BC822C77}
>> > > > > 2004-07-19 11:03:59-0400 1204 19f4 PT: Using server URL
>> > > > https://v5.windowsupdate.microsoft.com/ClientWebService/client.asmx
>> > > > > 2004-07-19 11:03:59-0400 1204 19f4 PT: Calling GetConfig on server
>> > > > > 2004-07-19 11:03:59-0400 1204 19f4 Add header for accept-encoding: xpress
>> > > > succeeded
>> > > > > 2004-07-19 11:03:59-0400 1204 19f4 DetectCompressionType returning type 0,
>> > > > hr=0x1
>> > > > > 2004-07-19 11:03:59-0400 1204 19f4 GetConfig: 0x80244019
>> > > > > 2004-07-19 11:03:59-0400 1204 19f4 PT: Cannot recover from fault,
>> > > > origin=GetConfig, hr=0x80244019
>> > > > > 2004-07-19 11:03:59-0400 1204 19f4 Sync of Updates: 0x80244019
>> > > > > 2004-07-19 11:03:59-0400 1204 19f4 WU client failed Searching for update
>> > > > with error 0x80244019
>> > > > > 2004-07-19 11:03:59-0400 1204 19f4 WU client calls back to search call
>> > > > WindowsUpdate with code Call failed and error 0x80244019
>> > > > > 2004-07-19 11:03:59-0400 1204 19f4 WU client completed and deleted call
>> > > > {4C36359C-2540-4AA0-AB8D-A798FDB62959}
>> > > > > 2004-07-19 11:03:59-0400 6956 1978 AU is forbidden; setting AU approval
>> > > > type to 'disabled'.
>> > > > > 2004-07-19 11:03:59-0400 6956 1ad8 Operation completed due to earlier
>> > > > error. (hr=80244019)
>> > > > > 2004-07-19 11:03:59-0400 6956 1ad8 Unable to complete asynchronous search
>> > > > successfully. (hr=80244019)
>> > > > > 2004-07-19 11:04:04-0400 1204 19f4 REPORT EVENT:
>> > > > {0A6BFE1C-C6B9-4940-AB71-C49BD9F828B1} 5 2004-07-19 11:03:59-0400 1 148 101
>> > > > {00000000-0000-0000-0000-000000000000} 0 80244019 WindowsUpdate Failure
>> > > > Software Synchronization Error: Agent failed detecting with reason:
>> > > > 0x80244019
>> > > > >
>> > > >
>> > > >
>> > > >

Next message: Kim: "Win 98 machines given XP Updates"
Previous message: oscar: "RE: GPO To block XP SP2 question"
In reply to: Mike C. - Columbus, OH: "Re: [Error number: 0x80244019]"
Messages sorted by: [ date ] [ thread ]

Relevant Pages

Re: nothing happens after message "Checking for the latest version
... "Nathan Kodak", ... Windows Update issues. ... >>> regsvr32 wuapi.dll ...
(microsoft.public.windowsupdate)
Re: I cant install critical updates
... I resolved error message problem from Vista Security Center by uninstalling and reinstalling Antivir. ... How it comes I can't either manage to install manually failing updates? ... Be sure to obtain the correct version for Windows x86. ... Windows Update Agent File Versions: ...
(microsoft.public.windowsupdate)
Re: Smeared screen = spyware?
... > Windows Update, but they haven't picked up anything. ... Step four - download and install the latest video card driver. ... NVidia Video Card Drivers ...
(microsoft.public.security)
Re: SVCHost keeps crashing
... I'd mentioned previously that I had run virus scanning and anit-spyware ... installed after device drivers and windows patches. ... So the machine is not fully patched at Windows Update? ... I didn't do a repair install. ...
(microsoft.public.windowsxp.general)
Re: Windows Update Hangs in Vista
... installing the WU Agent - see "A new version of the Windows Update ... You may need to add Windows Update to the Trusted Sites Zone: ... Clearing Temporary Internet files, cookies and history in Internet Explorer ...
(microsoft.public.windowsupdate)