Any known issues with msxml3.dll on Windows 2003?
I am trying to migrate a VB6 business object that uses RDS for access from Windows 2000 to a Windows 2003 server environment. I have not made any changes to the application or the calling application, but I get a 440 Automation Error when the code execution reaches the XML parsing point. data that the object should process (SAXXMLReader). The application uses msxml3.dll and the dll is on the server. Does anyone know if there are known issues between msxml3 server and win2003?
Or any other suggestions?
Here's the code calling the reader:
Set reader = New SAXXMLReader
Set contentHandler = New mBL_ContentHandlerImpl
Set errorHandler = New mBL_ErrorHandlerImpl
contentHandler.rsBatch = m_rsBatch
contentHandler.rsDocument = m_rsDocument
Set reader.contentHandler = contentHandler
Set reader.errorHandler = errorHandler
reader.parse (sData)
I do not know what the value of the code is for entering the code. The SAX reader content handler implementation is large and cumbersome. The problem is not in the code, I don't believe it as this app works fine on Win 2k server.
source to share
The problem had nothing to do with any problem between msxml 3 and Windows 2003. The problem was unusual for the application in that there must be a registry entry available that was not there. This application is poorly documented, and as such, a lot had to be discovered by carefully reviewing a lot of code.
source to share