This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
RE: Err.number & -2147221005
- To: <xsl-list at mulberrytech dot com>
- Subject: RE: Err.number & -2147221005
- From: "Chris Bayes" <Chris at Bayes dot co dot uk>
- Date: Sun, 20 Aug 2000 14:45:56 +0100
- Reply-To: xsl-list at mulberrytech dot com
Never seen it before but it is perfectly reasonable behaviour and works the
same in all versions of VBScript. -2147221005 is the ole automation error
number for Invalid class string.
-2147221005 (800401F3) Invalid class string.
So doing this with an invalid class string and on error set to resume next
>Set xmlDoc = Server.CreateObject(msxmlString)
will set Err.number to -2147221005 which is correct. However doing this
> errnumber=CINT(Err.number)
will set Err.number to 6 which is a runtime Overflow error. So then doing
this
> errnumber=CINT(Err.number)
will set errnumber to 6.
I don't know what you mean about 6 being a correct value.
Ciao Chris
XML/XSL Portal
http://www.bayes.co.uk/xml
>-----Original Message-----
>From: owner-xsl-list@mulberrytech.com
>[mailto:owner-xsl-list@mulberrytech.com]On Behalf Of lists@dunn.co.uk
>Sent: 20 August 2000 10:48
>To: XSL-List@mulberrytech.com
>Subject: Err.number & -2147221005
>
>
>Anyone found this error?
>Running ASP pages on Win2000 Advanced Server:
>
> Set xmlDoc = Server.CreateObject(msxmlString)
> If Err.number > 0 Then
>
>If I run this with a faulty msxmlString, Err.number is set to
>"-2147221005". If I do the following instead:
>
> Set xmlDoc = Server.CreateObject(msxmlString)
> errnumber=CINT(Err.number)
> errnumber=CINT(Err.number)
>
>then ... the first Err.number is -2147221005, the second is 6, the correct
>value.
>Anyone else found this?
>
>Thanks, Roland.
>
>
>
>
> XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list