Error 0x80244019 in Corp. Environment

We are having the same issue. Assuming it is the proxy
server as people bypassing the proxy have no issues.

We are running ISA 2000 sp1 on win2k.

At the moment I am considering allowing people to bypass
the proxy for the update addresses.

Another tick in the replace ISA with an appliance check
list my manager is putting together.


>-----Original Message-----
>I am getting error # 0x80244019 on a Windows XP SP1a
machine in a corporate
>environment on windows update v5. Its through a proxy
server.
>
>Here is part of the update file:
>
>2004-09-01 13:35:12-0500 772 1f4 WU client
succeeds
>CClientCallRecorder::BeginFindUpdates from WindowsUpdate
with call id
>{FC2C8B87-E5E2-48B1-99F5-132CD2252D4B}
>2004-09-01 13:35:12-0500 772 320 WU client
executing call
>{FC2C8B87-E5E2-48B1-99F5-132CD2252D4B} of type Search Call
>2004-09-01 13:35:13-0500 1232 e8 Trying to
make out of proc datastore active
>2004-09-01 13:35:13-0500 1232 e8 Out of
proc datastore is now active
>2004-09-01 13:35:13-0500 772 320 PT: Using
serverID
>{9482F4B4-E343-43B6-B170-9A65BC822C77}
>2004-09-01 13:35:13-0500 772 320 PT: Using
server URL
>https://v5.windowsupdate.microsoft.c...tWebService/cl
ient.asmx
>2004-09-01 13:35:13-0500 772 320 PT:
Calling GetConfig on server
>2004-09-01 13:35:13-0500 772 320 Add header
for accept-encoding: xpress
>succeeded
>2004-09-01 13:35:27-0500 772 320
DetectCompressionType returning type 0,
>hr=0x1
>2004-09-01 13:35:27-0500 772 320 GetConfig:
0x80244019
>2004-09-01 13:35:27-0500 772 320 PT: Cannot
recover from fault,
>origin=GetConfig, hr=0x80244019
>2004-09-01 13:35:27-0500 772 320 Sync of
Updates: 0x80244019
>2004-09-01 13:35:27-0500 772 320 WU client
failed Searching for update with
>error 0x80244019
>2004-09-01 13:35:27-0500 772 320 WU client
calls back to search call
>WindowsUpdate with code Call failed and error 0x80244019
>2004-09-01 13:35:27-0500 772 320 WU client
completed and deleted call
>{FC2C8B87-E5E2-48B1-99F5-132CD2252D4B}
>2004-09-01 13:35:27-0500 1388 4b8 Operation
completed due to earlier error.
>(hr=80244019)
>2004-09-01 13:35:27-0500 1388 4b8 Unable to
complete asynchronous search
>successfully. (hr=80244019)
>2004-09-01 13:35:32-0500 772 320 REPORT
EVENT:
>{C851B993-05D4-40A7-A2D8-8D510F7F2D1C} 504 2004-09-01
>13:35:27-0500 1 148 101 {00000000-0000-
0000-0000-000000000000} 0 80244019
WindowsUpdate Failure Software
>Synchronization Error: Agent failed detecting with
reason: 0x80244019
>
>.
>

Check out KB885819. This may provide a workaround until MS fixes the problem.

"Thomas Z" wrote:

> Does anyone know which ports Update v5 uses. Does it differ from V4 ?
> I'm behind a firewall and am thinking it might be that simple.
>
> Thomas
>
> "Tom" wrote:
>
> > We are having the same issue. Assuming it is the proxy
> > server as people bypassing the proxy have no issues.
> >
> > We are running ISA 2000 sp1 on win2k.
> >
> > At the moment I am considering allowing people to bypass
> > the proxy for the update addresses.
> >
> > Another tick in the replace ISA with an appliance check
> > list my manager is putting together.
> >
> >
> > >-----Original Message-----
> > >I am getting error # 0x80244019 on a Windows XP SP1a
> > machine in a corporate
> > >environment on windows update v5. Its through a proxy
> > server.
> > >
> > >Here is part of the update file:
> > >
> > >2004-09-01 13:35:12-0500 772 1f4 WU client
> > succeeds
> > >CClientCallRecorder::BeginFindUpdates from WindowsUpdate
> > with call id
> > >{FC2C8B87-E5E2-48B1-99F5-132CD2252D4B}
> > >2004-09-01 13:35:12-0500 772 320 WU client
> > executing call
> > >{FC2C8B87-E5E2-48B1-99F5-132CD2252D4B} of type Search Call
> > >2004-09-01 13:35:13-0500 1232 e8 Trying to
> > make out of proc datastore active
> > >2004-09-01 13:35:13-0500 1232 e8 Out of
> > proc datastore is now active
> > >2004-09-01 13:35:13-0500 772 320 PT: Using
> > serverID
> > >{9482F4B4-E343-43B6-B170-9A65BC822C77}
> > >2004-09-01 13:35:13-0500 772 320 PT: Using
> > server URL
> > >https://v5.windowsupdate.microsoft.c...tWebService/cl
> > ient.asmx
> > >2004-09-01 13:35:13-0500 772 320 PT:
> > Calling GetConfig on server
> > >2004-09-01 13:35:13-0500 772 320 Add header
> > for accept-encoding: xpress
> > >succeeded
> > >2004-09-01 13:35:27-0500 772 320
> > DetectCompressionType returning type 0,
> > >hr=0x1
> > >2004-09-01 13:35:27-0500 772 320 GetConfig:
> > 0x80244019
> > >2004-09-01 13:35:27-0500 772 320 PT: Cannot
> > recover from fault,
> > >origin=GetConfig, hr=0x80244019
> > >2004-09-01 13:35:27-0500 772 320 Sync of
> > Updates: 0x80244019
> > >2004-09-01 13:35:27-0500 772 320 WU client
> > failed Searching for update with
> > >error 0x80244019
> > >2004-09-01 13:35:27-0500 772 320 WU client
> > calls back to search call
> > >WindowsUpdate with code Call failed and error 0x80244019
> > >2004-09-01 13:35:27-0500 772 320 WU client
> > completed and deleted call
> > >{FC2C8B87-E5E2-48B1-99F5-132CD2252D4B}
> > >2004-09-01 13:35:27-0500 1388 4b8 Operation
> > completed due to earlier error.
> > >(hr=80244019)
> > >2004-09-01 13:35:27-0500 1388 4b8 Unable to
> > complete asynchronous search
> > >successfully. (hr=80244019)
> > >2004-09-01 13:35:32-0500 772 320 REPORT
> > EVENT:
> > >{C851B993-05D4-40A7-A2D8-8D510F7F2D1C} 504 2004-09-01
> > >13:35:27-0500 1 148 101 {00000000-0000-
> > 0000-0000-000000000000} 0 80244019
> > WindowsUpdate Failure Software
> > >Synchronization Error: Agent failed detecting with
> > reason: 0x80244019
> > >
> > >.
> > >
> >