FIX: You notice a small memory leak when a direct or indirect call to the WrapDSOandSession method of ADO Connection object is made and the MSDataShape provider is not used in MDAC 2.8

This article describes the following information about this hotfix release:

• The issues that are fixed by this hotfix package
• The prerequisites for installing the hotfix package
• Whether you must restart the computer after you install the hotfix package
• Whether the hotfix package is replaced by any other hotfix package
• Whether you must make any registry changes
• The files that are contained in the hotfix package

When you start a program that uses ActiveX Data Objects (ADO), you may notice a small memory leak when a direct or indirect call to the WrapDSOandSession method of the ADO Connection object is made and the MSDataShape provider is not used.

This problem can also occur when you use the Catalog.Create method in Microsoft ActiveX Data Objects Extensions for Data Definition Language and Security (ADOX). If you do this, the WrapDSOandSession method is called.

For a list of previous hotfixes, click the article number to view the article in the Microsoft Knowledge Base:

This problem occurs because a memory leak occurs in the WrapDSOandSession method of the ADO Connection object. This memory leak occurs when OLE DB errors are generated.

Service pack information

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

Hotfix information

Prerequisites

You must have Microsoft Data Access Components 2.8 installed to apply this hotfix.

Restart information

You must restart the computer after you apply this hotfix.

Hotfix file information

This hotfix is available in the hotfix that is documented in Microsoft Knowledge Base article 839801. The hotfix file information is available in the following Microsoft Knowledge Base article:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

For more information about the terminology that Microsoft uses when it corrects software after it is released, click the following article number to view the article in the Microsoft Knowledge Base: