FIX: Access Violation in MDAC Components When Running Under Low Memory Conditions

View products that this article applies to.

This article was previously published under Q317802

Expand all | Collapse all

SYMPTOMS

When Microsoft Data Access Components (MDAC) components are used under extremely low memory conditions, an unhandled access violation (AV) may occur.

Back to the top

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

290211 (http://support.microsoft.com/kb/290211/EN-US/ ) INF: How to Obtain the Latest SQL Server 2000 Service Pack

The English version of this fix should have the following file attributes or later:

 Date         Version          Size     File name      Platform
 ---------------------------------------------------------------
 24-JAN-2002  2.70.8324.0      307,200  Msadce.dll     x86
 05-MAR-2002  2.70.8505.0      147,456  Msadds.dll     x86
 24-JAN-2002  2.70.8324.0      487,424  Msado15.dll    x86
 24-JAN-2002  2.70.8324.0      413,696  Oledb32.dll    x86
 23-JAN-2002  2000.081.8323.0  450,560  Sqloledb.dll   x86

Back to the top

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 SQL Server 2000 Service Pack 3.

Back to the top

MORE INFORMATION

Under extremely low memory conditions, a memory allocation can fail. In certain situations inside MDAC components, memory allocation failures can cause an unhandled access violation. This fix corrects several such issues that were found during advanced stress-testing of various MDAC components.

Back to the top