perfectxml.com
 Basic Search  Advanced Search   
Topics Resources Free Library Software XML News About Us
  home » Focus » MSXML » KB Articles Thu, Oct 11, 2007
NEWS
MSXML 4.0 SP2 now available!

 
MSXML
Basics
DOM
SAX
XPath
XSLT
Schemas
SOM
HTTP Access
.NET
Data Islands
Ask a Question
   Past Q&As
C++ Samples
DLL/Version Info
Reference Guide
Books
KB Articles
   HOW TO
   SAMPLE
   INFO
   BUG/PRB
   FIX
   Misc.
MSXML Tips
   August 2002
   September 2002
MSXML Tools

Microsoft XML Core Services

Select KB Articles Category:
Page: 1  2  3  4  5  6  
PRB: Compiler Errors When You Use #import with XML in Visual C++ .NET

When you use MSXML parser dynamic-link libraries (DLLs) such as Msxml.dll, Msxml2.dll, Msxml3.dll, or Msxml4.dll to compile a Visual C++ .NET project with #import, you may receive the following compiler error messages:

c:\sample\test.cpp(12) : error C2872: 'IXMLDOMDocumentPtr' : ambiguous symbol

could be 'c:\Program Files\Microsoft Visual Studio .NET\Vc7\include\comdefsp.h(1228) : _com_ptr_t<_IIID> IXMLDOMDocumentPtr' with [ _IIID=_com_IIID ]
or 'c:\sample\Debug\msxml3.tlh(226) : MSXML2::IXMLDOMDocumentPtr'
-or-
c:\sample\test.cpp(16) : error C2039: 'async' : is not a member of 'IXMLDOMDocument' c:\Program Files\Microsoft Visual Studio .NET\Vc7\PlatformSDK\Include\MsXml.h(1845) : see declaration of 'IXMLDOMDocument'
-or-

c:\sample\test.cpp(27) : error C2660: 'IXMLDOMDocument::load' : function does not take 1 parameters
PRB: "Schema Is Non-Deterministic" Error Message When You Add XSD to XMLSchemaCache Object

When you add an XML Schema Definition (XSD) to the Microsoft XML 4.0 XMLSchemaCache object, you may receive the following error message:
Run-time error '-2147467259(80004005)': Schema is non-deterministic
BUG: MSXML Error Message When You Package or Deploy an Application with the Exchange SDK Application Deployment Wizard

When you try to package or deploy an application by using the Microsoft Exchange SDK Application Deployment Wizard, you may receive one of the following error messages:

Msxml3.dll has been installed on your machine to replace msxml.dll rather than to run side-by-side with it. This may cause the Application Wizard to fail. Would you like to continue anyway?
-or-
Msxml4.dll has been installed on your machine to replace msxml.dll rather than to run side-by-side with it. This may cause the Application Wizard to fail. Would you like to continue anyway?
PRB: "Proxy Authentication Required" Error Message with ServerXMLHTTP Object

When you use an Active Server Pages (ASP) application that uses the ServerXMLHTTP object to retrieve data from servers through a proxy server, and the virtual directory or Web site where the application resides is configured for Anonymous access, you may receive the following error message:

Proxy Authentication Required

You must authenticate with a proxy server before this request can be serviced.

Please try the following: Log on to your proxy server and try again. If you believe you should be able to view this directory or page, please contact the Web site administrator by using the e-mail address or phone number listed on the MyServer home page.

HTTP 407 - Proxy Authentication Required This problem may persist even if the server is using the correct proxy settings through Proxycfg, and even if the application is passing proxy credentials with the setProxyCredentials method.
PRB: Error Message When an XML Document Contains Low-Order ASCII Characters

When you attempt to use versions 3.0 or later of the MSXML parser to parse XML documents that contain certain low-order non-printable ASCII characters (that is, characters below ASCII 32), you may receive the following error message:
An Invalid character was found in text content.
PRB: MSXML 4.0 SAX Parser Raises Error Event Before startElement Event

When you use the MSXML 4.0 Simple API for XML (SAX) parser to validate an element that contains an attribute that is not valid (for example, if the attribute is not defined in the schema, or the attribute contains a value that is not valid), the SAX parser raises the error event of ISAXErrorHandler ( IVBSAXErrorHandler ) before the parser raises the startElement event of ISAXContentHandler ( IVBSAXContentHandler ). When the SAX parser raises the error event, only the line number and column number information that is associated with ISAXLocator is available to identify the faulty attribute, instead of the element name that contains the attribute.




PRB: MSXML SAX Validation with "exhaustive-errors" Feature Reports Only One Error for Each XML Tag

When you use the Microsoft XML (MSXML) 4.0 Simple API for XML (SAX) parser to validate an Extensible Markup Language (XML) document against an XML Schema Definition (XSD) schema, the SAX parser reports only one error for each element. This occurs even when you set the SAXXMLReader coclass "exhaustive-errors" feature to True . For example, when an element in an XML document contains more than one invalid attribute or attribute value, the MSXML 4.0 SAX parser only reports one error.
Multi-Threaded Program Under Stress Generates Access Violation with MSXML 3.0

A complex multi-threaded program that runs for a long time under stress and that makes extensive use of the MSXML 3.0 parser may generate an access violation error. The call stack for the crash that your program experiences is as follows:

ChildEBP RetAddr Args to Child
0a4be8ac 69b5d6e1 0622483c 0caabcc0 00000001 msxml3!QueryHelper__validateContextNode+0x1f
0a4be8c4 69b5daa1 09677760 00000001 0caabcc0 msxml3!XQLSelection__setContext+0x1b
0a4be8f8 69b5dc70 00677710 00000001 0caabcc0 msxml3!XQLSelection__initSelection+0xdd
0a4be93c 69b53e3d 09677710 00000001 0caabcc0 msxml3!XQLSelection__newXQLSelection+0x63
0a4be994 7c0042f3 061bfd88 0b928ee4 0a4be9c8 msxml3!DOMNode__selectNodes+0x96
PRB: MSXML 4.0: Matching Nodes Are Not Returned When You Run XPath Queries Against XML Documents that Specify a Default Namespace Declaration

When you use the MSXML 4.0 Document Object Model (DOM) methods ( selectNodes and selectSingleNode ) to run XPath queries against an XML document that specifies a default namespace declaration, the matching node or nodes are not returned.
BUG: MSXML: NMTOKEN Values with Multiple Colon (:) Characters Are Treated as XML Names

When you use NMTOKEN values that contain multiple colon (:) characters in an XML document, the values may be treated as XML names when the MSXML parser validates the document, and you may receive the following validation error message:
Multiple colons are not allowed in a name.
PRB: "Network Error Occurred" Error Message When MSXML 4.0 Installed

When you attempt to run the setup program for the October 2001 RTM release of the MSXML 4.0 parser, you may receive the following error message:

A network error occured while attempting to read from the file <path to msxml.msi>
NOTE: In this error message, the word "occured" is a misspelling for the word "occurred."
PRB: Users Are Prompted for Credentials When Using XMLHTTP or ServerXMLHTTP to Access Remote Pages

Users of applications that use the XMLHTTP or ServerXMLHTTP objects to access a remote Web page or XML document may be prompted for credentials when the objects open a connection to a remote server, even though the remote server does not require authentication




PRB: ServerXMLHTTP Cannot Intercept a Redirected Request

The ServerXMLHTTP object was introduced in MSXML 3.0 as a powerful way to handle server-to-server communication. When you use ServerXMLHTTP to send a request to an Active Server Pages (ASP) page that redirects the request to another page, ServerXMLHTTP cannot intercept the redirect.
The DomDocument Load Method Ignores Content Expiration

When you call the load method of the XML2.DOMDocument object to load an XML document through a script, Internet Explorer sends an "If-Modified-Since" header for the XML file.
ServerXMLHTTP Stops Responding When You Send a POST Request

When you send a POST request by using ServerXMLHTTP , and the response from an HTTP/1.1 server does not contain a Connection header, and the HTTP/1.1 server keeps the connection alive after it delivers a response to an HTTP request, ServerXMLHTTP may stop responding (hang) until the timeout expires, and you may receive the following error message:
msxml3.dll error '80004005'
Unspecified error
PRB: HRESULT C00CE56E "System Does Not Support the Specified Encoding" Error Message with MSXML

When you load a remote XML document from a Web server by using either XMLHTTP or IXMLDocument::Load, you may receive the following error message:

HRESULT C00CE56E System does not support the specified encoding. This error is most prevalent when you use a Java-based middle-tier application framework
PRB: Accessing a Secure URL from a Non-Secure Page with XMLHTTP Fails with "Permission denied" Error

When you attempt to access a secure URL by using the XMLHTTP request object from a script on a non-secure Web page, you may receive one of the following error messages:
With Msxml2.XMLHTTP:
Permission Denied
With Microsoft.XMLHTTP:
Access is Denied
This problem only occurs if a non-secure page attempts to access a secure page. Accessing a secure page from another secure page does not generate an error.
PRB: Element Is Not Updated When You Add Data to an XML Data Island

When you bind an element to XML data and dynamically add more data to the data island through script, the Data Source Object (DSO) is not updated. As a result, the element cannot display the newly added data.
This problem is not specific to the XML data island; it applies to other data sources as well.




BUG: Internet Explorer Stops Responding When You Open a Corrupted XML Document

When you open an XML document with Microsoft Internet Explorer, if the XML document is corrupted (for example, if the document is a truncated UNICODE XML document), Internet Explorer stops responding (hangs) and may crash.
PRB: MSXML Performance Bottleneck in ShareMutex Under Stress

When you use the MSXML parser in a high-stress environment such as Microsoft Internet Information Services (IIS), a bottleneck may occur while the MSXML parser performs garbage collection, such as around the msxml3!ShareMutex__SleepWaitingForLock internal MSXML function. This may cause unusually long run times on XML requests, and the application or service can appear to stop responding (hang). However, if the stress is removed from the application or service, the requests are eventually run and the process stabilizes.
Page: 1  2  3  4  5  6  


  Contact Us | E-mail Us | Site Guide | About PerfectXML | Advertise ©2004 perfectxml.com. All rights reserved. | Privacy