Don Miller wrote:
> For many reasons (that were discussed here in 2007 including using 
> XSLPatterns versus XPath), I have chosen to use MSXML 3.0 instead of 6.0 
> when I am interacting with SQL Server Reporting Services SOAP (the Prog ID I 
> use is MSXML2.DOMDocument.3.0 to parse and MSXML2.ServerXMLHTTP.6.0 to send 
> the request)
> 
> Everything was fine up until I upgraded my SQL Server 2005 yesterday, and I 
> inadvertently chose an option to install MSXML 6.0 during the upgrade. It 
> seems that my 3.0 code doesn't work anymore and I get the error "Object 
> required: 'xmldoc.documentElement'" where I use (Classic ASP) set xmldoc = 
> Server.CreateObject("MSXML2.DOMDocument.3.0") .
> 
> I thought that my 3.0 would still be there along with 6.0. 

MSXML 4, 5, 6 all install side by side to MSXML 3. Only MSXML 3 might 
replace older version like 2.6. So installation of MSXML 6 can't change 
or even remove your MSXML 3 installation.
The error must have different reasons. Can you give a clear description 
of the error? Does
   set xmldoc = Server.CreateObject("MSXML2.DOMDocument.3.0")
really not work any more?
But why would you get an error
   Object required: 'xmldoc.documentElement'
for that line, that does not make sense, it rather sounds as if the XML 
you are trying to parse is not well-formed and therefore the xmldoc 
object does not have a documentElement.





-- 

	Martin Honnen --- MVP XML
	http://JavaScript.FAQTs.com/