P
P James
Hi,
My project has been running for 4 years in ASP/IIS (originally on NT4, then
on Win2003 as of 1 year ago), using the following code to parse the request
object using the XML DOM:
Set oASPRequest = GetObjectContext.Item("Request")
Set oRequestDOM = CreateObject("MSXML.DOMDocument")
If Not oRequestDOM.Load(oASPRequest) Then Err.Raise 64000, , "ASP
Request object could not be parsed."
....and suddenly on 12/23 it started producing an error on the third line of
code above.
I'm not at work right now, so I can't get at the error information available
from the DOM, so I will reply to this post with that information. I'm
wondering if anyone knows what might be causing this to suddenly fail. I
will be looking into what, if any, security hot-fixes were applied to the
server recently.
If anyone can shed any light on this, I would sincerely appreciate it.
Thanks,
PJ
My project has been running for 4 years in ASP/IIS (originally on NT4, then
on Win2003 as of 1 year ago), using the following code to parse the request
object using the XML DOM:
Set oASPRequest = GetObjectContext.Item("Request")
Set oRequestDOM = CreateObject("MSXML.DOMDocument")
If Not oRequestDOM.Load(oASPRequest) Then Err.Raise 64000, , "ASP
Request object could not be parsed."
....and suddenly on 12/23 it started producing an error on the third line of
code above.
I'm not at work right now, so I can't get at the error information available
from the DOM, so I will reply to this post with that information. I'm
wondering if anyone knows what might be causing this to suddenly fail. I
will be looking into what, if any, security hot-fixes were applied to the
server recently.
If anyone can shed any light on this, I would sincerely appreciate it.
Thanks,
PJ