ASP / XML issue with IIS

[cordt.huneke@convergys.com]

Here is a brief description of the problem.


We have an ASP file (listener.asp) that is used to process
SOAP transactions on our web server. The ASP file uses
XML Core Services to load an XML file into a DOM document
variable. We process around 50,000 transactions a day
using this process. We have been getting intermittent
errors while trying to load the XML file. We typically
receive between 3 and 20 errors a day. We have attempted
many different fixes and we recently upgraded to XML Core
Services 4.0. None of our attempts have been successful
in resolving the issue. Here is an excerpt of the code
that fails.
Set oXMLDoc = Server.CreateOb ject
("Msxml2.DomDoc ument.4.0")
oXMLDoc.async = false
oXMLDoc.Load (strSchemaLocPh ys)

where strSchemaLocPhy s
is "C:\Inetpub\www root\cbwapiprod \CBWWorkflow.xm l".

[Jeff Cochran]

Re: ASP / XML issue with IIS

On Mon, 2 Aug 2004 12:32:24 -0700, "cordt.huneke@c onvergys.com"
<anonymous@disc ussions.microso ft.com> wrote:
[color=blue]
>Here is a brief description of the problem.[/color]
[color=blue]
>We have an ASP file (listener.asp) that is used to process
>SOAP transactions on our web server. The ASP file uses
>XML Core Services to load an XML file into a DOM document
>variable. We process around 50,000 transactions a day
>using this process. We have been getting intermittent
>errors while trying to load the XML file. We typically
>receive between 3 and 20 errors a day. We have attempted
>many different fixes and we recently upgraded to XML Core
>Services 4.0. None of our attempts have been successful
>in resolving the issue. Here is an excerpt of the code
>that fails.
> Set oXMLDoc = Server.CreateOb ject
>("Msxml2.DomDo cument.4.0")
> oXMLDoc.async = false
> oXMLDoc.Load (strSchemaLocPh ys)
>
>where strSchemaLocPhy s
>is "C:\Inetpub\www root\cbwapiprod \CBWWorkflow.xm l".[/color]

Might help if you post the error, in full.

Jeff

[Sanders Kaufman]

Re: ASP / XML issue with IIS

My experience is that "file-based" databases get these sporadic errors -
regardless of what you do.

You should always have error-handling code for if a database becomes
temporarily unavailable. At over 100 transactions per hour it's a sure bet
that SOMETHING will create this problem - antivirus stuff, anti-spam stuff,
defragmentation - something will make it unavailable for a few seconds per
day.


"cordt.huneke@c onvergys.com" <anonymous@disc ussions.microso ft.com> wrote in
message news:9a3801c478 c7$70362c40$a40 1280a@phx.gbl.. .[color=blue]
> Here is a brief description of the problem.
>
>
> We have an ASP file (listener.asp) that is used to process
> SOAP transactions on our web server. The ASP file uses
> XML Core Services to load an XML file into a DOM document
> variable. We process around 50,000 transactions a day
> using this process. We have been getting intermittent
> errors while trying to load the XML file. We typically
> receive between 3 and 20 errors a day. We have attempted
> many different fixes and we recently upgraded to XML Core
> Services 4.0. None of our attempts have been successful
> in resolving the issue. Here is an excerpt of the code
> that fails.
> Set oXMLDoc = Server.CreateOb ject
> ("Msxml2.DomDoc ument.4.0")
> oXMLDoc.async = false
> oXMLDoc.Load (strSchemaLocPh ys)
>
> where strSchemaLocPhy s
> is "C:\Inetpub\www root\cbwapiprod \CBWWorkflow.xm l".
>
>[/color]