help: error number 0x800A0005 after installing winxp sp2

i am getting this error message (Windows Update has encountered an error and
cannot display the requested page. You may find the following resources
helpful in resolving the problem) number 0x800A0005, when trying to access
the web page of windows update after installing winxp sp2, any clue how to
fix it?

Hi Legend1971,

My suggestion is to try and registry the wuaueng.dll. I've included the
instructions below.

Start > Run
Type "regsvr32 /u wuaueng.dll"
Press Ok


Here are some additional dll files that you may and try and registry.


Allenh [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"legend1971" <> wrote in message
news:61C93BCF-258A-4082-9655-...
> i am getting this error message (Windows Update has encountered an error
and
> cannot display the requested page. You may find the following resources
> helpful in resolving the problem) number 0x800A0005, when trying to access
> the web page of windows update after installing winxp sp2, any clue how to
> fix it?

"AllenH [MSFT]" <a-> wrote in message
news:...
> Hi Legend1971,
>
> My suggestion is to try and registry the wuaueng.dll. I've included the
> instructions below.
>
> Start > Run
> Type "regsvr32 /u wuaueng.dll"
> Press Ok

Allen,

Are you _un_registering it *only*? ;o


---



>
>
> Here are some additional dll files that you may and try and registry.
>
>
> Allenh [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "legend1971" <> wrote in message
> news:61C93BCF-258A-4082-9655-...
>> i am getting this error message (Windows Update has encountered an error
> and
>> cannot display the requested page. You may find the following resources
>> helpful in resolving the problem) number 0x800A0005, when trying to access
>> the web page of windows update after installing winxp sp2, any clue how to
>> fix it?
>
>

thanks allen,

tried the regsvr32 /u wuaueng.dll but it dodnt work, same problem

"AllenH [MSFT]" wrote:

> Hi Legend1971,
>
> My suggestion is to try and registry the wuaueng.dll. I've included the
> instructions below.
>
> Start > Run
> Type "regsvr32 /u wuaueng.dll"
> Press Ok
>
>
> Here are some additional dll files that you may and try and registry.
>
>
> Allenh [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "legend1971" <> wrote in message
> news:61C93BCF-258A-4082-9655-...
> > i am getting this error message (Windows Update has encountered an error
> and
> > cannot display the requested page. You may find the following resources
> > helpful in resolving the problem) number 0x800A0005, when trying to access
> > the web page of windows update after installing winxp sp2, any clue how to
> > fix it?
>
>
>

bump

"legend1971" wrote:

> thanks allen,
>
> tried the regsvr32 /u wuaueng.dll but it dodnt work, same problem
>
> "AllenH [MSFT]" wrote:
>
> > Hi Legend1971,
> >
> > My suggestion is to try and registry the wuaueng.dll. I've included the
> > instructions below.
> >
> > Start > Run
> > Type "regsvr32 /u wuaueng.dll"
> > Press Ok
> >
> >
> > Here are some additional dll files that you may and try and registry.
> >
> >
> > Allenh [MSFT]
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> > "legend1971" <> wrote in message
> > news:61C93BCF-258A-4082-9655-...
> > > i am getting this error message (Windows Update has encountered an error
> > and
> > > cannot display the requested page. You may find the following resources
> > > helpful in resolving the problem) number 0x800A0005, when trying to access
> > > the web page of windows update after installing winxp sp2, any clue how to
> > > fix it?
> >
> >
> >

"legend1971" <> wrote in message
news:29858A2F-4368-42C6-B14F-...
> 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
---

> FYI from the SUS Deployment White Paper (V4):

> 800a0005 Microsoft VBScript runtime error Invalid procedure call or
argument: 'fs.OpenTextFile'

For me this problem was solved by installing VB 5 Runtime from MS.

Regards Rolf

"Rolf Loeben" <> wrote in message
news:...
>> FYI from the SUS Deployment White Paper (V4):
>
>> 800a0005 Microsoft VBScript runtime error Invalid procedure call or
> argument: 'fs.OpenTextFile'
>
> For me this problem was solved by installing VB 5 Runtime from MS.

Thanks for the feedback! Do you have any clues from the logs
that you can share so we know what file is being processed by
a program written in VBScript?


Robert
---

when searching for 800a0005 within the hd i found this file "csenvir" where
the erroe 0x800a0005 was listed in, it is very long text html file, but in
regards with my erroe here what i found

- <CONTEXT>
<keyword>vs.message.0x800A0005</keyword>
<keyword>vs.message.VB_E_IDABADOSVER</keyword>
<DocSet>C#</DocSet>
<DocSet>VBA</DocSet>
<DocSet>Visual Basic</DocSet>
<DocSet>Visual C++</DocSet>
<DocSet>Visual Studio</DocSet>
<Product>VBA</Product>
<ProductVers>kbVBA</ProductVers>
<Product>VB</Product>
<ProductVers>kbVBp700</ProductVers>
<Product>VC</Product>
<ProductVers>kbVC700</ProductVers>
<Product>VFP</Product>
<ProductVers>kbVFP700</ProductVers>
<Product>VS</Product>
<ProductVers>kbVS700</ProductVers>
<Status>New</Status>
<TopicType>kbRef</TopicType>
<Locale>kbEnglish</Locale>
- <CONTENT>
<CITEM ACTION="csenvir:VB_E_IDABADOSVER">This application requires Windows
NT 4.0 (build <number> with Service Pack <number>), or Windows 95 (build
<number> or above).</CITEM>
</CONTENT>
</CONTEXT>






"Robert Aldwinckle" wrote:

> "legend1971" <> wrote in message
> news:29858A2F-4368-42C6-B14F-...
> > 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
> ---
>
>
>

i tried to install vb5 runtime with no help for my problem

"Rolf Loeben" wrote:

> > FYI from the SUS Deployment White Paper (V4):
>
> > 800a0005 Microsoft VBScript runtime error Invalid procedure call or
> argument: 'fs.OpenTextFile'
>
> For me this problem was solved by installing VB 5 Runtime from MS.
>
> Regards Rolf
>