FIX: Access Violation When Using MSXML in a Multi-Threaded Environment

Article translations Article translations
Article ID: 274734 - View products that this article applies to.
This article was previously published under Q274734
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page

SYMPTOMS

When you use the Microsoft XML Parser (MSXML) versions 2.0, 2.5 or 2.6 in a multi-threaded environment, your program may experience an access violation. Depending on the host application the exact symptoms may vary; for example, in a Microsoft Transaction Server (MTS) or COM+ application, an event may be logged indicating that a user component raised an exception.

CAUSE

This is due to known issues with MSXML versions 2.0, 2.5 and 2.6.

RESOLUTION

You can download MSXML 3.0 and use later versions of the parser from the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/xml
To resolve this problem, obtain the latest service pack for Microsoft Data Access Components 2.6. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
300635 INFO: How to Obtain the Latest MDAC 2.6 Service Pack

Hotfix

Alternatively, you may acquire the hotfix version of the Microsoft XML Parser that addresses this problem.

The English version of this fix should have the following file attributes or later:
   File name         Size       Date            Version
   -------------------------------------------------------
   Msxml2.dll   687,376 bytes   09/07/2000      8.0.6728.0
   Msxml2a.dll   21,776 bytes   09/07/2000      8.0.6728.0
   Msxml2r.dll   37,648 bytes   09/07/2000      8.0.6728.0
   Xmlinst.exe   26,384 bytes   09/07/2000      8.0.6728.0
				

STATUS

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

This problem was first corrected in Microsoft Data Access Components (MDAC) 2.6 Service Pack 1.

This bug has also been fixed in MSXML 2.6 Service Pack 1, which ships as part of MDAC 2.6 Service Pack 1.

This problem no longer occurs in MSXML 3.0 and later versions of the parser.

Properties

Article ID: 274734 - Last Review: February 28, 2014 - Revision: 1.2
APPLIES TO
  • Microsoft XML Parser 2.0
  • Microsoft XML Parser 2.5
  • Microsoft XML Parser 2.6
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbmsxmlnosweep kbqfe KB274734

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com