FIX: Access Violation When Using MSXML in a Multi-Threaded Environment
This article was previously published under Q274734
This article has been archived. It is offered "as is" and will no longer be updated.
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.
This is due to known issues with MSXML versions 2.0, 2.5 and 2.6.
You can download MSXML 3.0 and use later versions of the parser from the following Microsoft Developer Network (MSDN) Web site:
300635 INFO: How to Obtain the Latest MDAC 2.6 Service Pack
HotfixAlternatively, 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
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.
Article ID: 274734 - Last Review: 02/28/2014 00:33:34 - Revision: 1.2
Microsoft XML Parser 2.0, Microsoft XML Parser 2.5, Microsoft XML Parser 2.6
- kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbmsxmlnosweep kbqfe KB274734