Scripting Errors in JavaScript
Myke Folkes
This is a multi-part message in MIME format.
--------------804CF0243CB7825CB310D958
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi, I am trying to get an order page/shopping cart working on a site,
and I keep getting scripting errors when ever someone tries it from
Internet Explorer.. (both 3.0 and 4.0..).
The error is:80004005.
What does this mean? What can I do to fix it? I would appreciate any
responses.
thanks
-Myke
--------------804CF0243CB7825CB310D958
Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for Myke Folkes
Content-Disposition: attachment; filename="vcard.vcf"
begin: vcard
fn: Myke Folkes
n: Folkes;Myke
adr;dom: 155 S. Oak Apt. #B7;;;Spokane;WA;99204;
email;internet: mfo...@ior.com
x-mozilla-cpt: ;0
x-mozilla-html: FALSE
version: 2.1
end: vcard
--------------804CF0243CB7825CB310D958--
JustYaz
>Hi, I am trying to get an order page/shopping cart working on a site,
>and I keep getting scripting errors when ever someone tries it from
>Internet Explorer.. (both 3.0 and 4.0..).
>
>The error is:80004005.
>
>What does this mean? What can I do to fix it? I would appreciate any
>responses.
A page to look at would help.
Eric Lippert (MS Scripting Dev)
I've got good news and bad news.
The good news is that is a totally well known error message.
The bad news is that it is E_FAIL: "Something failed". Not particularly
helpful.
Perhaps you could be more specific.
Eric
JustYaz wrote in message <19971207222...@ladder02.news.aol.com>...
Duncan Crombie
> JustYaz wrote in message <
> >>The error is:80004005.
Eric Lippert (MS Scripting Dev) wrote:
> Perhaps you could be more specific.
Perhaps the browser should be more specific, Eric (-:
--
-----
Duncan Crombie
dcro...@ozemail.com.au
Eric Lippert (MS Scripting Dev)
That's why I need more specifics -- it probably is not the browser. It
would be nice if every ActiveX control returned a decent EXCEPINFO
structure, but plenty of them just return E_FAIL whenever something goes
wrong.
Eric
Duncan Crombie wrote in message <348C9A6C...@ozemail.com.au>...
Nick Fitzsimons
Just out of curiosity, why did MS include a really uninformative number,
rather than "Something failed"? The message is well known, but it's
confusing and irritating as hell until you learn that it's just devoid
of meaningful content separate from it's actual presence.
Eric Lippert (MS Scripting Dev) wrote:
>
> I've got good news and bad news.
>
> The good news is that is a totally well known error message.
>
> The bad news is that it is E_FAIL: "Something failed". Not particularly
> helpful.
>
> Perhaps you could be more specific.
>
> Eric
>
> JustYaz wrote in message <19971207222...@ladder02.news.aol.com>...
> >>Hi, I am trying to get an order page/shopping cart working on a site,
> >>and I keep getting scripting errors when ever someone tries it from
> >>Internet Explorer.. (both 3.0 and 4.0..).
> >>
> >>The error is:80004005.
> >>
> >>What does this mean? What can I do to fix it? I would appreciate any
> >>responses.
> >
> >A page to look at would help.
--
Nick Fitzsimons
Atlas Interactive Ltd
Aberdeen / Leicester
Scotland / England
UK
Eric Lippert (MS Scripting Dev)
We accidentally and not on purpose introduced a bug into the error handling
code right before we shipped version 3.0. One of the symptoms of this bug
was that the error string was not always displayed correctly. We fixed it
in scripting 3.1, which shipped with IE4.01 and the NT Option Pack.
Sorry about that.
Eric
Nick Fitzsimons wrote in message <348E83A2...@atlasinteractive.com>...
Ralph
"Eric Lippert (MS Scripting Dev)" <Eri...@Microsoft.Com> writes
>We accidentally and not on purpose introduced a bug into
is this a new MS standard disclaimer ;-)
>the error handling
>code right before we shipped version 3.0. One of the symptoms of this bug
>was that the error string was not always displayed correctly. We fixed it
>in scripting 3.1, which shipped with IE4.01 and the NT Option Pack.
>
>Sorry about that.
>
what I was really wondering is why you referred to it as an ActiveX
error message, is the JScript interpreter an OCX ?
(my knowledge of ActiveX is v.limited)
cheers
--
Ralph
Eric Lippert (MS Scripting Dev)
Re: ActiveX
I was speaking somewhat imprecisely if I said that. The script engines are
not OCXs, and they do not provide a dispatch interface to the engine.
The Microsoft Script Control, which is available from
www.microsoft.com/scripting, DOES provide an ActiveX interface to the script
engines, and we just put a new version of the code up there this week, so
check it out.
The script engine's error propagation uses similar structures and values as
a dispatch interface would. Since the script engine can call ActiveX
controls on their dispatch interfaces, it is important that we correctly
propagate error information returned by those controls to the script host.
Re: Disclaimers. It's not the standard disclaimer... yet. :-)
Eric
Ralph wrote in message <7oNQRGAe...@truleigh.demon.co.uk>...
Kal Khatib
Sadly, it's just microsoft way of doing things: convolutionary and cryptic.
Nick Fitzsimons wrote:
> Just out of curiosity, why did MS include a really uninformative number,
> rather than "Something failed...