This article was previously published under Q308566
This article has been archived. It is offered "as is" and will no longer be updated.
This article is part 4 of 4 in a series of articles documenting the bugsfixed in MSXML 3.0 Service Pack 2 (MSXML 3.0 SP2). For additional information about MSXML 3.0 SP2, click the article number below to view the article in the Microsoft Knowledge Base:
308480 INFO: How to Obtain the Latest Microsoft XML 3.0 Service Pack
The following bugs have been fixed in MSXML 3.0 SP2:
Bug: Microsoft.XMLHTTP in Replace mode does not send the body for the GET method
Microsoft.XMLHTTP (the older version of XMLHTTP) sends the body for the GET method, but MSXML2.XMLHTTP (the later version of XMLHTTP) does not. Because of this, when you install the MSXML parser in Replace mode and you use the older progID, you may receive the following error message:
Failed to load(Request)
Bug: MSXML DOM does not generate a validation error when you use a schema from XMLSchemaCache
MSXML DOM does not generate a validation error when you use a schema from XMLSchemaCache to validate an XML document when the following conditions are met:
The minLength or maxLength constraint is imposed on an element with dt:type="string".
An explicit namespace prefix is not specified in the schema.
Bug: Scripts that use MSXML run in Outlook Express
In Outlook Express, scripts that use MSXML do not access the Custom Security Manager.
Bug: The TLS structure leaks when you use MSXML in sp_OAxxx stored procedures
When you use MSXML inside a Microsoft SQL Server stored procedure through sp_OACreate, and a client application repeatedly opens and closes connections through which the stored procedures are run, a memory leak occurs inside SQL Server.
308563 INFO: List of Issues Fixed in Microsoft XML 3.0 Service Pack 2 (Part 1 of 4)
308564 INFO: List of Issues Fixed in Microsoft XML 3.0 Service Pack 2 (Part 2 of 4)
308565 INFO: List of Issues Fixed in Microsoft XML 3.0 Service Pack 2 (Part 3 of 4)