Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: A memory leak occurs when you use the sp_OAMethod stored procedure or the sp_OAGetProperty stored procedure to call a method of a COM object in SQL Server 2005

FIX: A memory leak occurs when you use the sp_OAMethod stored procedure or the sp_OAGetProperty stored procedure to call a method of a COM object in SQL Server 2005

View products that this article applies to.

Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release.

↑ Back to the top

This article describes the following about this hotfix release:
  • The issues that are fixed by the 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

↑ Back to the top

Symptoms

In Microsoft SQL Server 2005, when you call a method of a component object model (COM) object by using the sp_OAMethod stored procedure or the sp_OAGetProperty stored procedure, a memory leak occurs. For the sp_OAMethod stored procedure, this problem occurs if the method returns the result in the output parameter of the method. For the sp_OAGetProperty stored procedure, this problem occurs if the stored procedure returns a property value in the OUTPUT parameter.

Additionally, if the memory leaks exhausts the non-buffer pool memory region, the following error message is logged in the SQL Server error log file:
2008-05-01 08:35:07.80 spid535 Downgrading backup log buffers from 1024K to 64K
2008-05-06 09:35:22.55 spid77 Failed Virtual Allocate Bytes: FAIL_VIRTUAL_RESERVE 1048576
2008-05-06 10:48:04.85 spid593 Error: 701, Severity: 17, State: 123.
2008-05-06 10:48:04.85 spid593 There is insufficient system memory to run this query.

↑ Back to the top

Cause

This problem occurs because SQL Server 2005 does not release the memory that is allocated to the variable that holds the output parameter value.

↑ Back to the top

Resolution

Cumulative update information

The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
936305 Cumulative update package 2 for SQL Server 2005 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Microsoft SQL Server 2005 Service Pack 1 (SP1) installed to apply this hotfix.

For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005

Restart information

You do not have to restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix file information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
SQL Server 2005 32-bit version
File nameFile versionFile sizeDateTimePlatform
Bcp.exe2005.90.2232.069,48809-May-200719:36x86
Databasemailengine.dll9.0.2232.075,12009-May-200719:36x86
Logread.exe2005.90.2232.0400,75209-May-200719:37x86
Microsoft.analysisservices.adomdclient.dll9.0.2232.0546,16009-May-200719:37x86
Microsoft.analysisservices.deploymentengine.dll9.0.2232.0140,65609-May-200719:37x86
Microsoft.analysisservices.dll9.0.2232.01,217,90409-May-200719:37x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2232.078,19209-May-200719:37x86
Microsoft.sqlserver.sqlenum.dll9.0.2232.0910,70409-May-200719:37x86
Msasxpress.dll9.0.2232.024,94409-May-200719:37x86
Msgprox.dll2005.90.2232.0200,56009-May-200719:37x86
Msmdlocal.dll9.0.2232.015,646,06409-May-200719:37x86
Msmdredir.dll9.0.2232.03,993,96809-May-200719:37x86
Odsole70.dll2005.90.2232.059,76009-May-200719:37x86
Qrdrsvc.exe2005.90.2232.0369,52009-May-200719:37x86
Rdistcom.dll2005.90.2232.0643,44009-May-200719:37x86
Repldp.dll2005.90.2232.0187,24809-May-200719:37x86
Replmerg.exe2005.90.2232.0320,88009-May-200719:37x86
Replprov.dll2005.90.2232.0550,25609-May-200719:37x86
Replrec.dll2005.90.2232.0784,75209-May-200719:37x86
Replsub.dll2005.90.2232.0407,40809-May-200719:37x86
Spresolv.dll2005.90.2232.0177,00809-May-200719:37x86
Sqlaccess.dll2005.90.2232.0350,57609-May-200719:37x86
Sqlagent90.exe2005.90.2232.0321,39209-May-200719:37x86
Sqlservr.exe2005.90.2232.028,979,11209-May-200719:37x86
Sqsrvres.dll2005.90.2232.066,41609-May-200719:37x86
Xmlsub.dll2005.90.2232.0195,44009-May-200719:37x86
Xpstar90.dll2005.90.2232.0295,28009-May-200719:37x86
Xpstar90.rll2005.90.2232.0155,50409-May-200719:37x86
SQL Server 2005 x64-based version
File nameFile versionFile sizeDateTimePlatform
Bcp.exe2005.90.2232.088,94409-May-200716:46x64
Databasemailengine.dll9.0.2232.075,12009-May-200716:46x86
Logread.exe2005.90.2232.0525,16809-May-200716:46x64
Microsoft.analysisservices.adomdclient.dll9.0.2232.0546,16009-May-200716:46x86
Microsoft.analysisservices.adomdclient.dll9.0.2232.0546,16009-May-200719:37x86
Microsoft.analysisservices.deploymentengine.dll9.0.2232.0140,65609-May-200719:37x86
Microsoft.analysisservices.dll9.0.2232.01,217,90409-May-200719:37x86
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2232.094,06409-May-200716:46x64
Microsoft.sqlserver.mgdsqldumper.dll2005.90.2232.078,19209-May-200719:37x86
Microsoft.sqlserver.sqlenum.dll9.0.2232.0877,93609-May-200716:46x86
Msasxpress.dll9.0.2232.030,06409-May-200716:46x64
Msasxpress.dll9.0.2232.024,94409-May-200719:37x86
Msgprox.dll2005.90.2232.0262,00009-May-200716:46x64
Msmdlocal.dll9.0.2232.015,646,06409-May-200719:37x86
Msmdredir.dll9.0.2232.03,993,96809-May-200719:37x86
Odsole70.dll2005.90.2232.090,99209-May-200716:46x64
Qrdrsvc.exe2005.90.2232.0434,03209-May-200716:46x64
Rdistcom.dll2005.90.2232.0836,46409-May-200716:46x64
Repldp.dll2005.90.2232.0237,93609-May-200716:46x64
Repldp.dll2005.90.2232.0187,24809-May-200719:37x86
Replmerg.exe2005.90.2232.0417,64809-May-200716:46x64
Replprov.dll2005.90.2232.0747,88809-May-200716:46x64
Replrec.dll2005.90.2232.01,010,54409-May-200716:46x64
Replsub.dll2005.90.2232.0528,24009-May-200716:46x64
Spresolv.dll2005.90.2232.0225,64809-May-200716:46x64
Sqlaccess.dll2005.90.2232.0357,74409-May-200716:46x86
Sqlagent90.exe2005.90.2232.0392,56009-May-200716:46x64
Sqlservr.exe2005.90.2232.039,373,16809-May-200716:46x64
Sqsrvres.dll2005.90.2232.078,19209-May-200716:46x64
Xmlsub.dll2005.90.2232.0319,85609-May-200716:46x64
Xpstar90.dll2005.90.2232.0543,60009-May-200716:46x64
Xpstar90.rll2005.90.2232.0156,01609-May-200716:46x64

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

For more information about the same problem in Microsoft SQL Server 2000, click the following article number to view the article in the Microsoft Knowledge Base:

816937 FIX: A memory leak may occur when you use the sp_OAMethod stored procedure to call a method of a COM object

For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:

822499 New naming schema for Microsoft SQL Server software update packages

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top

More Information

In the following sample script, you use the sp_OAMethod stored procedure and the sp_OAGetProperty stored procedure to obtain results by using the OUTPUT parameter. If you run this script repeatedly on a new connection to SQL Server 2005, a memory leak occurs every time.
DECLARE @object int;
DECLARE @hr int;
DECLARE @src varchar(255), @desc varchar(255);
EXEC @hr = sp_OACreate 'SQLDMO.SQLServer', @object OUT;
IF @hr <> 0 BEGIN
EXEC sp_OAGetErrorInfo @object, @src OUT, @desc OUT
RETURN 
END
EXEC @hr = sp_OASetProperty @object, 'LoginSecure', 'TRUE'
IF @hr <> 0 BEGIN
EXEC sp_OAGetErrorInfo @object
RETURN
END
EXEC @hr = sp_OAMethod @object, 'Connect', NULL, '<ComputerName>\<InstanceName>'
IF @hr <> 0 BEGIN
EXEC sp_OAGetErrorInfo @object
RETURN
END
DECLARE @property varchar(255)
EXEC @hr = sp_OAMethod @object, 'HostName', @property OUT
IF @hr <> 0 BEGIN
EXEC sp_OAGetErrorInfo @object
RETURN
END
PRINT @property
EXEC @hr = sp_OAGetProperty @object, 'HostName', @property OUT
IF @hr <> 0 BEGIN
EXEC sp_OAGetErrorInfo @object
RETURN
END
PRINT @property
EXEC @hr = sp_OADestroy @object
IF @hr <> 0 BEGIN
EXEC sp_OAGetErrorInfo @object
RETURN
END
Additionally, you may experience an access violation because the problemthat is described in the "Symptoms" section occurs. The SQL error log file will include the following information:
2008-03-24 10:03:09.51 spid51      Using 'odsole70.dll' version '2005.90.1399' to execute extended stored procedure 'sp_OACreate'. This is an informational message only; no user action is required.
2008-03-24 10:03:13.43 spid51      Using 'dbghelp.dll' version '4.0.5'
2008-03-24 10:03:13.51 spid51      ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\LOG\SQLDump0001.txt
2008-03-24 10:03:13.53 spid51      SqlDumpExceptionHandler: Process 51 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.
2008-03-24 10:03:13.53 spid51      * *******************************************************************************
2008-03-24 10:03:13.53 spid51      *
2008-03-24 10:03:13.53 spid51      * BEGIN STACK DUMP:
2008-03-24 10:03:13.53 spid51      *   03/24/08 10:03:13 spid 51
2008-03-24 10:03:13.53 spid51      *
2008-03-24 10:03:13.54 spid51      *
2008-03-24 10:03:13.54 spid51      *   Exception Address = 0000000033387164 Module(odsole70+0000000000007164)
2008-03-24 10:03:13.54 spid51      *   Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION
2008-03-24 10:03:13.54 spid51      *   Access Violation occurred reading address 0000000006264FF8
The fix for this problem is in the Odsole70.dll file. The first fixed version of the binary is 2005.90.2232.0.


Microsoft SQL Server 2005 Service Pack 2 (SP2) does not include this fixed binary. If you experience this problem in SQL Server 2005 SP2, you must install a cumulative update to fix this problem.

The first cumulative update that includes this fix is Cumulative update package 2 for SQL Server 2005 SP2. The build for this update is 09.00.3175. Therefore, you can install the latest cumulative update for SQL Server 2005 or any cumulative update that was released after June 2007 to resolve this issue.

For more information about cumulative updates for SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

↑ Back to the top

Keywords: kb, kbautohotfix, kbhotfixserver, kbfix, kbexpertiseadvanced, kbqfe, kbpubtypekc

↑ Back to the top

Article Info
Article ID : 937277
Revision : 1
Created on : 1/7/2017
Published on : 10/8/2011
Exists online : False
Views : 1020