Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


MSXML 3 Replaced By MSXML6 - Help

From: "Don Miller" <nospam@------.--->
To: NULL
Date: 2/13/2009 6:28:00 AM
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. So, I downloaded 
and installed the Microsoft the XML Parser (MSXML) 3.0 Service Pack 7 (SP7) 
and it still doesn't work! The only related programs I have in Add/Remove 
Programs are MSXML 6 Service Pack 2 and SQLXML4. I found the MSXML.dll and 
registered it and that didn't work either.

So, what's going on and how I can I go back to MSXML 3.0?

Thanks for any help! 




transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent