Re: error number 0x800A0005 after installing winxp sp2
From: Robert Aldwinckle (robald_at_techemail.com)
Date: 08/14/04
- Next message: ZStoner: "Re: Bad Scrollbar visible in Windows Update v5 home page"
- Previous message: Linda: "Virus: Bloodhound.Exploit.6?"
- In reply to: legend1971: "Re: error number 0x800A0005 after installing winxp sp2"
- Next in thread: Rolf Loeben: "Re: error number 0x800A0005 after installing winxp sp2"
- Reply: Rolf Loeben: "Re: error number 0x800A0005 after installing winxp sp2"
- Reply: legend1971: "Re: error number 0x800A0005 after installing winxp sp2"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 14 Aug 2004 11:15:52 -0400
"legend1971" <legend1971@discussions.microsoft.com> wrote in message
news:29858A2F-4368-42C6-B14F-809BA0C3643A@microsoft.com...
> bump
Pathetic. What have you done to try to investigate this symptom
on your own? We need details to work with not bleats of dissatisfaction.
Tried searching your files for that code? Do it without the 0x prefix too.
Do it with the decimal equivalent too: -2146828283
Search the whole harddrive. You might be missing something by assuming
that relevant hits should only occur in *.log or *.xml files
It's quite likely that the context of this error code is more signficant than
the code itself. In fact, it could be that earlier error codes within that
context are more significant than the immediate context of the code;
so it would probably be a good idea to quote from full context(s)
on a timestamp basis.
FYI from the SUS Deployment White Paper (V4):
800a0005 Microsoft VBScript runtime error Invalid procedure call or argument: 'fs.OpenTextFile'
This suggests to me that this code would be unexpected, since it is
just a canned definition and AFAIK VBScript doesn't have much
to do with WU. OTOH if it does then it may also suggest a possible
stab at a solution of simply reinstalling scripting support.
A Google Groups search for this code shows that you are going to have
to be a trailblazer on this one. There are no immediate canned solutions,
and not even any incidents which are definitely V5 related.
0x800a0005 OR 800a0005 OR 2146828283 MSFT OR MVP group:microsoft.*.windowsupdate
Good luck
Robert
---
- Next message: ZStoner: "Re: Bad Scrollbar visible in Windows Update v5 home page"
- Previous message: Linda: "Virus: Bloodhound.Exploit.6?"
- In reply to: legend1971: "Re: error number 0x800A0005 after installing winxp sp2"
- Next in thread: Rolf Loeben: "Re: error number 0x800A0005 after installing winxp sp2"
- Reply: Rolf Loeben: "Re: error number 0x800A0005 after installing winxp sp2"
- Reply: legend1971: "Re: error number 0x800A0005 after installing winxp sp2"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
