There's a bug in MSXML 4.0 and 5.0 (not sure about 3.0)
I'm sorry I don't have the details. It was over a month ago that I discovered it and had to work-around it.
You are better off using 3.0 or ServerXMLHTTP object instead.
I did some testing myself and here's what i found...
Code:
Set objXML = Server.CreateObject("Msxml2.DOMDocument.5.0")
permission denied
Code:
Set objXML = Server.CreateObject("Msxml2.DOMDocument.4.0")
permission denied
Code:
Set objXML = Server.CreateObject("Msxml2.DOMDocument.3.0")
worked! However, could not use some new XMLDOM features I needed
Code:
Set objXML = Server.CreateObject("Microsoft.XMLDOM")
worked! However, could not use some new XMLDOM features I needed
Code:
Set objXML = Server.CreateObject("MSXML2.ServerXMLHTTP.4.0")
worked!
I'm not sure if I did it the best way, but using the code below fixed the problem for me.
Code:
Dim objXMLHTTP, sResponseText
Set objXMLHTTP = Server.CreateObject("Msxml2.ServerXMLHTTP.4.0")
objXMLHTTP.open "GET", sWebSiteURL, false
objXMLHTTP.send
sResponseText = objXMLHTTP.responseText
set objXMLHTTP = nothing
Dim objXML
Set objXML = Server.CreateObject("Msxml2.DOMDocument.5.0")
With objXML
.async = False
.validateOnParse = False
.preserveWhiteSpace = False
.resolveExternals = False
End With
objXML.LoadXML(sResponseText)
'... use objXML object here ...
Set objXML = nothing