bmccleary
asked on
HELP!!! - Installation of MSXML Parser 4.0 SP1
I have an ASP page that uses the Microsoft XML Parser.
I had msxml4.dll (Ver 4, not SP1 and not the pre-April 2001 release) installed, the actual version was 4.08. In my ASP page I use the following to instantiate the XML DOM object:
Set objXMLDoc = Server.Createobject("MSXML
Now, I just updated my server to the MSXML 4.0 SP1 parser (version 4.10) and the page now throws the error pointing to the object creation line:
Server object error 'ASP 0177 : 80040111'
Server.CreateObject Failed
ClassFactory cannot supply requested class
Why won't my CreateObject method work with this new version? I have tried changing the line to:
Set objXMLDoc = Server.Createobject("MSXML
and
Set objXMLDoc = Server.Createobject("MSXML
but neither of those work either. This upgrade caused my entire site to go down and I can't find out how to "roll-back" to the non-SP1 version. I am in a bind here, so any help is appreciated.
I had msxml4.dll (Ver 4, not SP1 and not the pre-April 2001 release) installed, the actual version was 4.08. In my ASP page I use the following to instantiate the XML DOM object:
Set objXMLDoc = Server.Createobject("MSXML
Now, I just updated my server to the MSXML 4.0 SP1 parser (version 4.10) and the page now throws the error pointing to the object creation line:
Server object error 'ASP 0177 : 80040111'
Server.CreateObject Failed
ClassFactory cannot supply requested class
Why won't my CreateObject method work with this new version? I have tried changing the line to:
Set objXMLDoc = Server.Createobject("MSXML
and
Set objXMLDoc = Server.Createobject("MSXML
but neither of those work either. This upgrade caused my entire site to go down and I can't find out how to "roll-back" to the non-SP1 version. I am in a bind here, so any help is appreciated.
Brian,
1. what Operating System are you using?
2. what MSIE version is on the server?
Notes
=====
1. I have installed MSXML4 SP1 on top of MSXML4 for Windows 2000 Professional, Windows 2000 Server and Windows 2000 Advanced server. There was no problems encountered. Remember to close all objects which use MSXML4. This includes any COM or COM+/MTS Objects (in short, reboot box if you are using COM+/MTS as shutting down the services do not guarantee that the pointers are properly released)
2. Remember that there was the July and April releases of MSXML4 be4 it went gold. Uninstall all MSXML4 of these beta versions be4 you proceed.
3. You would have installed Windows Installer 2.0 be4 you could install MSXML4 RTM+.
1. what Operating System are you using?
2. what MSIE version is on the server?
Notes
=====
1. I have installed MSXML4 SP1 on top of MSXML4 for Windows 2000 Professional, Windows 2000 Server and Windows 2000 Advanced server. There was no problems encountered. Remember to close all objects which use MSXML4. This includes any COM or COM+/MTS Objects (in short, reboot box if you are using COM+/MTS as shutting down the services do not guarantee that the pointers are properly released)
2. Remember that there was the July and April releases of MSXML4 be4 it went gold. Uninstall all MSXML4 of these beta versions be4 you proceed.
3. You would have installed Windows Installer 2.0 be4 you could install MSXML4 RTM+.
ASKER
b1xml2,
Thanks for the response! Here's the low-down on my configuration. I did the development on one of our testing machines running W2K Professional. It had MSXML 4.08 installed (I believe that this was the non-SP1 version, but it was downloaded and installed within the past 6 months, so it should not be the older releases). It worked perfectly for development, then when I rolled it out onto the production server which is W2K Advanced Server which had MSXML 4.0 SP1 installed, then I got the error. To test out what was causing the error, I installed the SP1 on my machine and it caused the same error. According to Microsoft (http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/001/766/msdncompositedoc.xml) they recommend unregistering the DLL's before install, but only for the pre-releases. I did not do this, but after the error, I did uninstall MSXML 4.0, reboot, delete the dll's, reboot again, and reinstall, and it did not fix the problem. It sounds like the component interface changed between releases. Does this help? Am I using the correct call to instantiate the object?
Thanks for the response! Here's the low-down on my configuration. I did the development on one of our testing machines running W2K Professional. It had MSXML 4.08 installed (I believe that this was the non-SP1 version, but it was downloaded and installed within the past 6 months, so it should not be the older releases). It worked perfectly for development, then when I rolled it out onto the production server which is W2K Advanced Server which had MSXML 4.0 SP1 installed, then I got the error. To test out what was causing the error, I installed the SP1 on my machine and it caused the same error. According to Microsoft (http://msdn.microsoft.com/downloads/default.asp?url=/downloads/sample.asp?url=/msdn-files/027/001/766/msdncompositedoc.xml) they recommend unregistering the DLL's before install, but only for the pre-releases. I did not do this, but after the error, I did uninstall MSXML 4.0, reboot, delete the dll's, reboot again, and reinstall, and it did not fix the problem. It sounds like the component interface changed between releases. Does this help? Am I using the correct call to instantiate the object?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also,
if you have MSXML3 installed on your box, as an interim measure, use the progid "Msxml2.DOMDocument.3.0". To call MSXML4, you are using the right progid "Msxml2.DOMDocument.4.0"
if you have MSXML3 installed on your box, as an interim measure, use the progid "Msxml2.DOMDocument.3.0". To call MSXML4, you are using the right progid "Msxml2.DOMDocument.4.0"
ASKER
I did have MSIE 6.0 already installed, so I don't know what fixed the problem, but it is fixed now. I had to completly uninstall MSXML and reinstall IE6 and MSXML and the problem seemed to fix itself. Also, I did have to use the "MSXML2.DOMDocument.4.0" reference instead of the "MSXML2.DOMDocument". Thanks for info!
ASKER