FIX: A memory leak occurs when you use the sp_OAMethod stored procedure to call a method of a COM object in SQL Server 2005
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. This article describes the following about this hotfix release:
SYMPTOMSIn Microsoft SQL Server 2005, when you call a method of a component object model (COM) object by using the sp_OAMethod stored procedure, a memory leak occurs. This problem occurs if the method returns the result in the output parameter of the method. CAUSEThis problem occurs because SQL Server 2005 does not release the memory that is allocated to the variable that holds the output parameter value. RESOLUTIONA 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, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site: http://go.microsoft.com/?linkid=6294451 (http://go.microsoft.com/?linkid=6294451) 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. To create a separate service request, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support) Note The "Hotfix download available" section and the online request forms display 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.PrerequisitesYou 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 (http://support.microsoft.com/kb/913089/)
How to obtain the latest service pack for SQL Server 2005
Restart informationYou do not have to restart the computer after you apply this hotfix.Registry informationYou do not have to change the registry.Hotfix file informationThis 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
SQL Server 2005 x64-based version
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. 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 (http://support.microsoft.com/kb/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 (http://support.microsoft.com/kb/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 (http://support.microsoft.com/kb/824684/)
Description of the standard terminology that is used to describe Microsoft software updates
MORE INFORMATIONAdditionally, you may experience an access violation because the problem that is described in the "Symptoms" section occurs. The SQL Errorlog 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 (http://support.microsoft.com/kb/937137/)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
APPLIES TO
| Article Translations
|
Back to the top
