Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 823593 - Last Review: January 21, 2004 - Revision: 2.1
INFO: List of Bugs That Are Fixed in Microsoft XML 3.0 Service Pack 4
This article provides information about the bugs that are
fixed in Microsoft XML Parser (MSXML) 3.0 Service Pack 4 (SP4).
Microsoft service packs are cumulative and include bugs that are
fixed in earlier service packs that were released for the product.
This service pack includes the bug fixes that are included in MSXML
3.0 Service Packs 1, 2, and 3.
For additional information about how to obtain MSXML 3.0
service packs, click the following article number to view the article in the
Microsoft Knowledge Base:
308480Â
(http://kbalertz.com/Feedback.aspx?kbNumber=308480/EN-US/
)
INFO: How to Obtain the Latest Microsoft XML 3.0 Service Pack
MSXML 3.0 SP4
- While transforming certain data by using the format-number
function in XSLT, an Access Violation occurs.
When you use the
format-number function in XSLT while transforming XML data, an access violation
occurs. The problem occurs when you use 18-digit numbers.
To reproduce
the problem, use the following .xsl and .xml files:
Format.xsl
<?xml version='1.0'?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:template match="http://support.microsoft.com">
<xsl:for-each select="Test/Data">
<xsl:value-of select="."/>
<!--xsl:value-of select="format-number(current(),'#.#######')"/-->
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>
Format.xml
<Test>
<Data>101101900000350196</Data>
</Test>
- Resetting an empty nodelist caused a Null reference general protection fault
(GPF).
In MSXML 3.0 SP2, calling the reset method on a node list that is empty may produce a GPF. The
following VBScript code reproduces the problem:Dim dom
Set dom = CreateObject(“MSXML2.DomDocumentâ€);
dom.loadXML “<a>abc</a>â€
dom.documentElement.firstChild.childNodes.reset()
- Crash would occur when validating circular entity reference
defined in XML Document Type Definition (DTD). The XML DTD [ Document Type
definition ] is a standard used to define the valid building blocks that can be
used to create an instance of a specific XML document. It defines an XML
document’s structure with a list of valid elements and attributes that can be
used to create an instance of the XML document. A DTD can be declared inline
within the XML document, or externally in a separate file.If declared
externally, it will need to be referenced in the XML file to which it is
applicable.
DTDs are commonly used to validate the structure of an
XML document. Validating the structure of an XML document is a very important
requirement in XML based applications that need to receive and process XML data
from a variety of internal and external sources. Validation helps verify that
the data in an XML document adheres to the structure defined in its associated
DTD. This is a proactive step that needs to be executed before the XML data is
processed in order to prevent errors that could occur as a result of invalid,
or required but missing elements and attributes in the data.
If a DTD
contains a circular reference, MSXML may stop responding. The following code
reproduces the problem:MyXml.xml
<?xml version="1.0"?>
<!DOCTYPE test [
<!ELEMENT test ANY>
<!ELEMENT a ANY>
<!ENTITY z "<a>&z;</a>">
]>
<test>&z;</test>
In this instance, the entity "z" replaces the "&z" with XML. At this
point, the parser tries to replace the entity again with the XML, thus
producing a circular reference.
MSXML 3.0 SP3
For additional information about
the problems that are fixed by MSXML 3.0 Service Pack 3, click the following
article numbers to view the articles in the Microsoft Knowledge Base:
328995Â
(http://kbalertz.com/Feedback.aspx?kbNumber=328995/EN-US/
)
INFO: List of Issues Fixed in MSXML 3.0 Service Pack 3 (Part 1)
328998Â
(http://kbalertz.com/Feedback.aspx?kbNumber=328998/
)
INFO: List of Issues Fixed in MSXML 3.0 Service Pack 3 (Part 2)
MSXML 3.0 SP2
For additional
information about the problems that are fixed by MSXML 3.0 Service Pack 2,
click the following article numbers to view the articles in the Microsoft
Knowledge Base:
308563Â
(http://kbalertz.com/Feedback.aspx?kbNumber=308563/EN-US/
)
INFO: List of Issues Fixed in Microsoft XML 3.0 Service Pack 2 (Part 1 of 4)
308564Â
(http://kbalertz.com/Feedback.aspx?kbNumber=308564/
)
INFO: List of Issues Fixed in Microsoft XML 3.0 Service Pack 2 (Part 2 of 4)
308565Â
(http://kbalertz.com/Feedback.aspx?kbNumber=308565/
)
INFO: List of Issues Fixed in Microsoft XML 3.0 Service Pack 2 (Part 3 of 4)
308566Â
(http://kbalertz.com/Feedback.aspx?kbNumber=308566/
)
INFO: List of Issues Fixed in Microsoft XML 3.0 Service Pack 2 (Part 4 of 4)
Microsoft XML Parser (MSXML) 3.0 Service Pack 1
For additional information about
the problems that are fixed by MSXML 3.0 Service Pack 1, click the following
article number to view the article in the Microsoft Knowledge Base:
292935Â
(http://kbalertz.com/Feedback.aspx?kbNumber=292935/EN-US/
)
INFO: List of Issues Fixed in Microsoft XML 3.0 Service Pack 1
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate