Microsoft Knowledge Base Email Alertz

Microsoft XML (MSXML) may experience random failures (access violations) when MSXML 4.0 Service Pack 1 (SP1) performs transforms on a free-threaded XML Document Object Model (DOM) document from multiple threads simultaneously. This problem is more...

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 326860 - Last Review: November 15, 2007 - Revision: 2.6

FIX: Access Violation in Microsoft XML 4.0 When Service Pack 1 Performs Tranforms on Cached XML Documents

Hotfix download is availableHotfix Download Available
View and request hotfix downloads
This article was previously published under Q326860

SYMPTOMS

Microsoft XML (MSXML) may experience random failures (access violations) when MSXML 4.0 Service Pack 1 (SP1) performs transforms on a free-threaded XML Document Object Model (DOM) document from multiple threads simultaneously. This problem is more likely to occur on multi-processor computers, and to occur under stress.

CAUSE

An internal part of the free-threaded XML DOM document is prematurely destroyed when MSXML 4.0 SP1 performs a transform. This issue occurs when MSXML cleans up a stack frame and, during this operation, uses a node attribute as a template parameter. Re-using this node may cause random failures because of the use of freed memory or the use of corrupted data.

RESOLUTION

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time   Version      Size (bytes)  File name
   --------------------------------------------------------------
   06-Sep-2002  16:44  4.10.9405.0     1,230,848  Msxml4.dll       

				

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

APPLIES TO
  • Microsoft XML Core Services 4.0 Service Pack 1
Keywords: 
kbautohotfix kbhotfixserver kbqfe kbbug kbfix kbmsxml400fix kbqfe KB326860
       

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