Failed to reserve contiguous memory of Size= 65536

[sonname]

Could someone please tell what this error in sql server log means? "Failed to reserve contiguous memory of Size= 65536" I have been getting these errors after every two days. When this happens, I need to stop and restart sql server, then it seems OK for a couple more days.

Thanks

 

[MeanGreen]

Here is one possibility:
FIX: SP_OA Procedures Leak Memory and Cause Various Errors

The information in this article applies to:

· Microsoft SQL Server 2000

BUG #: 351363 (Shiloh_bugs)

SYMPTOMS

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:

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.

Sometimes, the following error has also been reported:

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.

CAUSE

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.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article and should be applied only to systems experiencing this specific problem. This fix may receive additional testing at a later time, to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/directory/overview.asp

NOTE: In special cases, charges that are normally incurred for support calls may be canceled, if a Microsoft Support Professional determines that a specific update will resolve your problem. Normal support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:

File name Platform

----------------------

s80231i.exe X86

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.



STATUS

Microsoft has confirmed this to be a problem in SQL Server 2000.

Additional query words: memleak odsole ole70 dmo calls sp_oa procs


Hope this helps.

 

[MeanGreen]

I also found this:
The warning 'Failed to reserve contiguous memory' generally implies that there is
insufficient contiguous free memory in the MemToLeave area. (MemToLeave area is
primarily used by non-SQL Server code that happens to be executing within the SQL
Server process.)

In order to troubleshoot the problem, please check the following:
1. Check the Output from SQLDIAG utility: This can be obtained by running sqldiag.exe
from the command prompt from the bin subdirectory under SQL. For more information,
Please refer to Books-on-line reference: sqldiag utility

2. Do you have any non-SQL Server component running inside the SQL address space?
For example:
a) Extended stored procedures
b) sp_OA procedures calling COM objects
c) Third-party OLEDB providers or ODBC drivers
3. Verify that the sp_configure option "network packet size" is not set to 8K
or larger.

In order to find the root cause for the problem with more accuracy, I suggest you to contact the Local Product Support Service with the above collect information.


Hope this helps.