FIX: sp_OA Procedures Cause Memory Leak in SQLSERVR.EXE

 Last reviewed: October 31, 1997
Article ID: Q151601

The information in this article applies to:
  • Microsoft SQL Server, version 6.5
BUG#: 14447 (6.50)

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 Microsoft SQL Server version 6.5. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.5. You must also apply Service Pack 3 for Windows NT 4.0. For information on obtaining the NT Service Pack, see the following Knowledge Base article: 

   
      ARTICLE-ID: Q152734
      TITLE     : 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 the 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

Additional query words: sp sproc
Keywords : kbbug6.50 kbfix6.50.sp3 SSrvStProc kbprg
Version : 6.5
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbfix

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 31, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.