|
Posted by Alex Krawarik[MSFT] on April 17, 2006, 5:34 pm
If you were Registered and logged in, you could reply and use other advanced thread options
You are using MSXML3, which has nothing to do with .NET Framework 2.0. The
problem may be on your client or server, its hard to say for sure...the
error you are seeing is coming from URLMON, Internet Explorer's networking
component but it kind of depends on what resource you are actually trying to
load in oXML.load(url)
If your break was indeed caused by a patch, you might try looking into
MS06-13 a bit, which was released April 11. I didnt see anything in there
that would specifically affect you from the information you've given thus
far, but here's the link
http://support.microsoft.com/kb/912812
> XML Experts:
>
> We have the following JavaScript that has been working well for two
> years. On Thursday, April 13, it started to fail. Someone said that
> Microsoft downloaded some automatic security updates around that time.
> We have .NET Framework 2.0 installed on our IIS Server, if that is a
> clue.
>
> ---------------------- C U T H E R E ----------------------
>
> var oXML = new ActiveXObject("MSXML2.DOMDocument.3.0");
> oXML.async = false;
> if (oXML.load(url))
> {
> // (good ...)
> }
> else
> {
> alert(oXML.parseError.errorCode + '\n\n' + oXML.parseError.reason);
> }
>
> ---------------------- C U T H E R E ----------------------
>
> oXML.parseError.errorCode = 0x800c0007, and
> oXML.parseError.reason = "No data is available for the requested
> resource."
>
> We generate our XML automatically and I put our output through an XML
> validator and our XML appears to be fine.
>
> Is there something that we need to do on our server or (IE 6.0) browser
> in order to make this work again?
>
|