Article ID: 282229 - View products that this article applies to.
This article was previously published under Q282229
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 351363 (Shiloh_bugs)
Calling OLE Automation support stored procedures, namely sp_OAMethod, sp_OAGetProperty, and sp_OASetProperty, leak a small amount of memory in the OLE Automation Object operation DLL (Odsole70.dll) file. This may cause the following errors to be reported in the SQL Server error log:
Sometimes, the following error has also been reported:
2000-11-27 11:22:59.87 server SQL Server could not spawn process_loginread thread.
2000-11-27 11:25:09.42 server SQL Server could not spawn process_loginread thread.
2000-11-27 11:55:06.09 spid431 WARNING: Failed to reserve contiguous memory of Size= 65536.
2000-11-27 11:55:06.09 spid1714 WARNING: Failed to reserve contiguous memory of Size= 65536.
In very rare situations, this may also result in the termination of the SQL Server process. Note that the preceding symptoms usually occur a long time after the server was started and only when the OLE Automation stored procedures are used frequently.
When calling any of the sp_OA procedures, a string that was allocated was not freed, leaking few bytes on each call. The size of the leak is not fixed and is dependent on the string.
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/290211/EN-US/ )INF: How to Obtain the Latest SQL Server 2000 Service Pack
HotfixNOTE: The following hotfix was created prior to Microsoft SQL Server 2000 Service Pack 1.
The English version of this fix should have the following file attributes or later:
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.
File name Platform ---------------------- s80231i.exe X86
Microsoft has confirmed that this is a problem in Microsoft SQL Server 2000. This problem was first corrected in SQL Server 2000 Service Pack 1.