Microsoft Knowledge Base Email Alertz

KBAlertz.com: 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 Micros

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]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **


Bug Tracking Software
For bug tracking software or defect tracking software or issue tracking software, visit Axosoft.


Community Site



We Send hundreds of thousands of emails using ASP.NET Email



Expert Web Design & Graphic Design
Design44.com

ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
The ad says 3 - but KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

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




Article ID: 274734 - Last Review: September 26, 2005 - Revision: 1.1

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

This article was previously published under Q274734

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 (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  (http://kbalertz.com/Feedback.aspx?kbNumber=300635/EN-US/ ) 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.

APPLIES TO
  • Microsoft XML Parser 2.0
  • Microsoft XML Parser 2.5
  • Microsoft XML Parser 2.6
Keywords: 
kbbug kbfix kbqfe kbmsxmlnosweep kbhotfixserver KB274734
       

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

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please