Re: Update still failing with 80240020 and 8024000c
From: Robert Aldwinckle (robald_at_techemail.com)
Date: 10/17/04
- Next message: Torgeir Bakken \(MVP\): "Re: Clean Install of Windows Xp"
- Previous message: mtlaine: "Re: Windows Update and errormessage 0xC8000158"
- In reply to: Dan Epstein: "Re: Update still failing with 80240020 and 8024000c"
- Next in thread: Dan Epstein: "Re: Update still failing with 80240020 and 8024000c"
- Reply: Dan Epstein: "Re: Update still failing with 80240020 and 8024000c"
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 17 Oct 2004 09:02:12 -0400
> I'm not the only one having this problem according to the newsgroup.
The only ones that have bothered to submit some log has the 0x800704dd
symptom or a very similar 0x800706dd symptom. (Both refer to
failures in GetUserTokenFromSessionID)
E.g. this search shows nobody posting details:
(Google Groups search for
(80240020 OR 0x80240020) -GetUserTokenFromSessionID group:microsoft.*
)
The other diagnostic I suggested last time was inconclusive because
you cleared your SoftwareDistribution directory. Are there any more
clues in the subdirectory structure yet?
Robert
---
"Dan Epstein" <dseps@yahoo.com> wrote in message
news:pde4n094ndquf4hcl5q160u07kmqjm9fue@4ax.com...
> On Sat, 16 Oct 2004 00:41:33 -0400, "Robert Aldwinckle"
> <robald@techemail.com> wrote:
>
>>Did you manage to fix that SID problem you had last month then?
>
> That problem disappeared--no references to 800704dd have been seen since
> that one instance. Just the errors referenced in the subject above,
> 80240020 and 8024000c. I'm happy to reissue my log file, but it hasn't
> changed since the last time, and reports only these errors as described:
>
> "Updates were unable to be successfully installed"
>
> with the following errors in the log file:
>
> ISusInternal API failed CClientCallRecorder::DisconnectCall with error
> 0x8024000c
> WU client failed installing updates with error 0x80240020
> WU client calls back to install call
> {FE542022-4DA9-4BF9-A4CE-C376FE27C105} with code Call failed and error
> 0x80240020
> Operation completed due to earlier error. (hr=80240020)
> SusInternal API failed CClientCallRecorder::DisconnectCall with error
> 0x8024000c
>
> I'm not the only one having this problem according to the newsgroup.
>
> Thanks,
> Dan
>
>>
>><
>>http://www.microsoft.com/windowsxp/expertzone/newsgroups/reader.mspx?&query=epstein&lang=en&cr=US&guid=&sloc=en-us&dg=microsoft.public.windowsupdate&p=1&tid=1b44f43b-99df-4a57-bb76-276b1638881a&mid=1b44f43b-99df-4a57-bb76-276b1638881a
>>>
>>
>>Notice that hr = 800704dd was reported then *before* the code
>>which filtered back to you. If you are still getting this I think it is
>>what you should be trying to change.
>>
>>
>>HTH
>>
>>Robert Aldwinckle
>>---
>>
>>
>>"Dan Epstein" <dseps@yahoo.com> wrote in message news:6emtm01er9rlc84ktuvet4egrcocdkh8a2@4ax.com...
>>> Updates download but then do not install, reporting
>>>
>>> "Updates were unable to be successfully installed"
>>>
>>> and with the following errors in the log file:
>>>
>>> ISusInternal API failed CClientCallRecorder::DisconnectCall with error
>>> 0x8024000c
>>> WU client failed installing updates with error 0x80240020
>>> WU client calls back to install call
>>> {FE542022-4DA9-4BF9-A4CE-C376FE27C105} with code Call failed and error
>>> 0x80240020
>>> Operation completed due to earlier error. (hr=80240020)
>>> SusInternal API failed CClientCallRecorder::DisconnectCall with error
>>> 0x8024000c
>>>
>>> Any ideas?
>>>
>>> Thanks!
>>
>
- Next message: Torgeir Bakken \(MVP\): "Re: Clean Install of Windows Xp"
- Previous message: mtlaine: "Re: Windows Update and errormessage 0xC8000158"
- In reply to: Dan Epstein: "Re: Update still failing with 80240020 and 8024000c"
- Next in thread: Dan Epstein: "Re: Update still failing with 80240020 and 8024000c"
- Reply: Dan Epstein: "Re: Update still failing with 80240020 and 8024000c"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|