FIX: sp_OA Procedures Cause Memory Leak in SQLSERVR.EXE (151601)



The information in this article applies to:

  • Microsoft SQL Server 6.5

This article was previously published under Q151601
BUG#: 14447 (SQLBUG_65)

SYMPTOMS

The use of sp_OA procedures causes a 16K memory leak per connect/disconnect.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 6.5. This problem has been corrected in Service Pack 5a for Microsoft SQL Server 6.5.For more information, click the following article number to view the article in the Microsoft Knowledge Base:

197177 INF: How to Obtain SQL Server 6.5 Service Pack 5a

For more information, contact your primary support provider.

You must also apply Service Pack 3 for Windows NT 4.0. For information about obtaining the Windows NT Service Pack, please see the following article in the Microsoft Knowledge Base:

152734 : How To Obtain the Latest Windows NT 4.0 Service Pack



For more information, contact your primary support provider.

MORE INFORMATION

Running the following causes a 16K leak in Sqlservr.exe:

isql -E -idmo2.sql


   ===dmo2.sql===
   DECLARE @object int
   DECLARE @hr int
   DECLARE @property varchar(255)
   DECLARE @return varchar(255)

   -- Create an object
   EXEC @hr = sp_OACreate 'SQLOLE.SQLServer', @object OUT
   IF @hr <> 0
       EXEC sp_OAGetErrorInfo @object

   -- Set a property
   EXEC @hr = sp_OASetProperty @object, 'LoginSecure', 1
   IF @hr <> 0
       EXEC sp_OAGetErrorInfo @object

   -- Call a method
   EXEC @hr = sp_OAMethod @object, 'Connect', NULL
   IF @hr <> 0
       EXEC sp_OAGetErrorInfo @object
				

Modification Type:MajorLast Reviewed:3/14/2006
Keywords:kbBug kbfix kbProgramming kbSQLServ650fix KB151601