Upgrading W2K3 Server to MSXML SP2

Upgrading W2K3 Server to MSXML SP2

am 16.05.2005 21:33:01 von TrentUSTA

Hi,

Overview of Problem:
I'm experiencing some timeout issues that seem to be caused somewhere
between the IIS request to SQL and the response back to IIS. The issue seems
to me almost like a memory leak where the request responses get worse with
time. A restart of IIS seems to clear up the issue. Our NW admin ran an IP
trace and said that the request was getting to sql but the page never
renders. Upon further investigation, we found that our Db Server is running
MSXML sp2 while our web servers are running sp1. The DBA says that could
definately cause issues, possibly memory leaks, especially since we do have
stored procedures using the XML EXPLICIT clause.

Resolution:
I've been tasked with upgrading the web servers to SP2. After some
investigating, I find that we avoided upgrading in August of 2003 because we
had some issues that came about while trying to upgrade. I made the upgrade
on one of our development servers and ran into the same issue immediately.

Issue 1:
No data is available for the requested resource.
this is one of the lines of code that's erroring
doc.load(Request)
where doc = Server.CreateObject("MSXML2.DOMDocument.4.0")
async = false
setProperty "ServerHTTPRequest", true
validateOnParse = true

Upon scouring the internet a found that I could set the resolveExternals
property to false which seems to fix the download error but then the document
is not validated against my xsd file which then produces the xsi:nil
attribute invalid error message. I can then set the validateOnParse property
to false to stop that error. However, this obviously is not the correct
solution as I am seeking help.

Issue 2:
One of the asp pages accepts an incoming request as XML, disects the XML,
and creates a request to one of our partners using the ServerXMLHTTP object.
DIM http
SET http = Server.CreateObject ("MSXML2.ServerXMLHTTP")
http.open "POST", Application("site"), false
http.send (inputData)

the send method returns this to the page

msxml4.dll error '80070005'


Access is denied.

Thanks for the help,
Trent

RE: Upgrading W2K3 Server to MSXML SP2

am 16.05.2005 22:43:44 von TrentUSTA

I should also have mentioned that I've went through the excercises from the
kb...
http://support.microsoft.com/default.aspx?scid=kb;en-us;8208 82

"Trent USTA" wrote:

> Hi,
>
> Overview of Problem:
> I'm experiencing some timeout issues that seem to be caused somewhere
> between the IIS request to SQL and the response back to IIS. The issue seems
> to me almost like a memory leak where the request responses get worse with
> time. A restart of IIS seems to clear up the issue. Our NW admin ran an IP
> trace and said that the request was getting to sql but the page never
> renders. Upon further investigation, we found that our Db Server is running
> MSXML sp2 while our web servers are running sp1. The DBA says that could
> definately cause issues, possibly memory leaks, especially since we do have
> stored procedures using the XML EXPLICIT clause.
>
> Resolution:
> I've been tasked with upgrading the web servers to SP2. After some
> investigating, I find that we avoided upgrading in August of 2003 because we
> had some issues that came about while trying to upgrade. I made the upgrade
> on one of our development servers and ran into the same issue immediately.
>
> Issue 1:
> No data is available for the requested resource.
> this is one of the lines of code that's erroring
> doc.load(Request)
> where doc = Server.CreateObject("MSXML2.DOMDocument.4.0")
> async = false
> setProperty "ServerHTTPRequest", true
> validateOnParse = true
>
> Upon scouring the internet a found that I could set the resolveExternals
> property to false which seems to fix the download error but then the document
> is not validated against my xsd file which then produces the xsi:nil
> attribute invalid error message. I can then set the validateOnParse property
> to false to stop that error. However, this obviously is not the correct
> solution as I am seeking help.
>
> Issue 2:
> One of the asp pages accepts an incoming request as XML, disects the XML,
> and creates a request to one of our partners using the ServerXMLHTTP object.
> DIM http
> SET http = Server.CreateObject ("MSXML2.ServerXMLHTTP")
> http.open "POST", Application("site"), false
> http.send (inputData)
>
> the send method returns this to the page
>

msxml4.dll error '80070005'
>


> Access is denied.
>
> Thanks for the help,
> Trent