Strange out of memory error on 2005

Hot Topic

Information for Column-Level Merge Replication
Exporting a Cube into MS Excel
Reason for Limitation and Work around for referencing Table Group fields in Footer!
SHOWSTOPPER!!!!
The SQL Server Service Broker Challange
SQLXML 4.0
Merge Tables and FileGroups
Can you please tell me where I'm going wrong in my asynchronous script component?
Script Task errors
Data Source Connection Not Setting Correctly

SQL Server

Error trying to websync
Can't pass parameter - rsAccessDenied
Need general advice on financal reporting (P&L statement)
A "not in"-lookup?
Encryption in MDF file possible?
sp_remove_document return code
Hyperlink report in new page..Urgent
readxml doesnt work :(
Multiple Connections in Managed Trigger
Customize Error Messages

Strange out of memory error on 2005

Hi,

I am getting the following:

spid53,Unknown,Failed Virtual Allocate Bytes: FAIL_VIRTUAL_RESERVE 262144
spid53,Unknown,Memory Manager <nl/> VM Reserved = 1662084 KB<nl/> VM Committed = 954940 KB <nl/> AWE Allocated = 0 KB <nl/> Reserved Memory = 1024 KB <nl/> Reserved Memory In Use = 0 KB
... <lots of memoryclerk/cachestore stuff)
...
Followed by loads of 701s (There is insufficient system memory to run this query.) until the service is stopped. No new connections can be made at this time either.

I'm running an ASP page under IIS 5.0 (on 2000) against the SQL Server. Connections are being pooled. The page just calls a stored procedure and passes some results back to the caller of the URL. It's fairly straightforward. I've tried using SQLOLEDB, the SQL Server ODBC driver and the SQL Native Client - I get the same error each time. The error appears after about 80,000 calls. Using the ODBC driver, the procedure cache buffers grew constantly, but with OLEDB or the native client, the buffer value remains constant (I guess this has something to do with sp_reset_connection being called each time a pooled connection is being reused - this doesn't occur using the ODBC driver).

The stored procedure creates/calls/destroys a COM DDL using the sp_OA procedures. I've tried running the DLL both in and out of process with no change in the behaviour.

I've also taken a part of the workload and ran it in an endless loop under Management Studio - it runs fine without any problems. So, I figure it has something to do with the connectivity from the web server.

This was running fine on SQL Server 2000 - the errors are only occurring on 2005.

Has anyone experienced something similar to this Does anyone have any ideas on where I should start looking next

Thanks in advance,
Mark

Answer this question

Strange out of memory error on 2005

  • Kosta II

    Here is some more info on my latest encouter with this error. 

    This is from the dump log.

    spid54      CImageHelper::Init () Version-specific dbghelp.dll is not used
    spid54      CImageHelper::Init () Failed load of dbghelp.dll - Not enough storage is available to process this command.

    (down a little bit...)
    spid54      *   Exception Address = 627C4C17 Module(UNKNOWN+00000000)
    spid54      *   Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION
    spid54      *   Access Violation occurred writing address 00000000

    This is from the exception log

    spid 54 Exception 0xc0000005 EXCEPTION_ACCESS_VIOLATION writing address 00000000 at 0x627C4C17

  • Joe Courchaine

    Hmm - I don't think using AWE is going to help you out here. I had a pretty good look at the output from your 701 error and the buffer pool shows at about 1.5GB - about the max you will get without using /3GB. The allocation that's failing is 128kb, meaning that the allocation will come from outside the buffer pool.

    Now if an allocation of 128kb is failing it generally means that all virtual address space has been either exhausted, or fragmented to a point where there are no more blocks of that size.

    You did mention that you are using linked servers, which do also consume memory from outside the buffer pool.
    You might consider moving the linked server out of process, assuming that you can do so.



  • keisuke

    Jerome, thanks for the response. The strange thing is I'm not using any com DLL's, or anything 3rd party. This is a recently setup server with a hyperthreading dual-core Xeon processor, 4Gig of memory, Windows 2003 Enterprise, and SQL 2005 Standard (and it's components: SSIS, SSAS, etc.)

    That's why I don't get it. I did read something I might try. From what I understand, AWE is only needed if you have MORE than 4Gig of memory, but I read that if you are running on Windows 2003 Enterprise edition, it is better to run in AWE mode. I might give that a shot, even though I don't really get it.

    If I can't figure this out in a few weeks I probably will open a ticket. Thanks again.

  • veneto

    I got the same error this morning, well it was actually waiting for me once I came in. The IT manager had already rebooted the server to kick start SQL Server.

    Only thing from microsoft on this i could find is:

    http://support.microsoft.com/kb/312948

    which relates to the same error but for SQL Server 2000 (Please don't tell me they've carried a known bug forward into 2005)

    The fix that MS recommend requires installing updates (can't install 2000 updates onto 2005 as far as I know ) so that leave the work around:

    WORKAROUND

    To work around this issue, disable Network Library protocol encryption by clicking to clear the Force Protocol Encryption check box in the Server network utility and/or the Client network utility.
    Now i just need to find where this setting has moved to in SQL Server.
    About my error. I've got a large SSIS package that imports a lot of data from an Informix CE server via ODBC/OLE DB/Linked servers into the SQL Server instance for data warehousing and reporting. Its been running fine for a couple of weeks, although steadily growing in size as more source table were added. Occasionally steps were falling over, either due to network or other data errors, to stop subsequent imports in the same package failing a "wait" had to be built inbetween each table import.
    I'll let you know if I find anything else
    Cheers
    Sam Vella


  • JJ Brychell

    Was there ever a solution to this problem I am getting the same error. We have SQL Server 2005 SP1, Reporting Services, IIS, and linked servers on our SQL Server box.

  • john ewing

    This morning, I had the same problem but not with a web application. I'm just pulling over data from several tables in a linked server to a local SQL 2005 database. With the task manager open on the server, I can watch the memory usage on the sql server process grow and grow as the data transfer occurs.

    Once the process is complete, the memory usage remains at the same level and grows again if I run another process. It appears to be some kind of memory leak, but I don't know where it is or how to plug it. There may be a command that can force a release of the memory to work around the problem, but I don't know how... mainly because I've never had to manually manage memory in good old SQL 2000.

    If anyone has answers for me and Mark, it is appreciated.
    Thanks,
    Hugh

  • bigranger75th

    Mark,

    can you post the details of your hardware - 32 or 64 bit, amount of processors, memory along with the full output from the error message in the errorlog



  • SkyBlade&amp;#33;

    Once again, i have an out of memory error that prevented my backup from running last night. I really need some help here. Here is the SQL log leading up to and including the backup error.

    03/23/2006 02:00:04,Backup,Unknown,BACKUP failed to complete the command BACKUP DATABASE [DatabaseName]. Check the backup application log for detailed messages.
    03/23/2006 02:00:04,Backup,Unknown,Error: 3041<c/> Severity: 16<c/> State: 1.
    03/23/2006 02:00:04,spid72,Unknown,There is insufficient system memory to run this query.
    03/23/2006 02:00:04,spid72,Unknown,Error: 701<c/> Severity: 17<c/> State: 17.
    03/23/2006 02:00:04,spid72,Unknown,Downgrading backup buffers from 1024K to 64K
    03/23/2006 01:55:04,Backup,Unknown,BACKUP failed to complete the command BACKUP DATABASE master. Check the backup application log for detailed messages.
    03/23/2006 01:55:04,Backup,Unknown,Error: 3041<c/> Severity: 16<c/> State: 1.
    03/23/2006 01:55:04,spid73,Unknown,There is insufficient system memory to run this query.
    03/23/2006 01:55:04,spid73,Unknown,Error: 701<c/> Severity: 17<c/> State: 17.
    03/23/2006 00:00:02,spid20s,Unknown,This instance of SQL Server has been using a process ID of 2552 since 3/21/2006 1:38:26 PM (local) 3/21/2006 7:38:26 PM (UTC). This is an informational message only; no user action is required.
    03/22/2006 15:45:27,spid67,Unknown,There is insufficient system memory to run this query.
    03/22/2006 15:45:27,spid67,Unknown,Error: 701<c/> Severity: 17<c/> State: 123.
    03/22/2006 15:45:27,spid67,Unknown,MEMORYBROKER_FOR_RESERVE <nl/> Allocations = 0 <nl/> Rate = 0 <nl/> Target Allocations = 158125 <nl/> Future Allocations = 35204 <nl/> Last Notification = GROW
    03/22/2006 15:45:27,spid67,Unknown,MEMORYBROKER_FOR_STEAL <nl/> Allocations = 952 <nl/> Rate = 123 <nl/> Target Allocations = 158125 <nl/> Future Allocations = 0 <nl/> Last Notification = GROW
    03/22/2006 15:45:27,spid67,Unknown,MEMORYBROKER_FOR_CACHE <nl/> Allocations = 1787 <nl/> Rate = -789 <nl/> Target Allocations = 158125 <nl/> Future Allocations = 0 <nl/> Last Notification = GROW
    03/22/2006 15:45:27,spid67,Unknown,Big Gateway <nl/> Configured Units = 1 Available Units = 1 Acquires = 0 <nl/> Waiters = 0 Threshold Factor = 8 Threshold = -1
    03/22/2006 15:45:27,spid67,Unknown,Medium Gateway <nl/> Configured Units = 4 Available Units = 4 Acquires = 0 <nl/> Waiters = 0 Threshold Factor = 12 Threshold = 107946666
    03/22/2006 15:45:27,spid67,Unknown,Small Gateway <nl/> Configured Units = 16 Available Units = 15 Acquires = 1 <nl/> Waiters = 0 Threshold Factor = 250000 Threshold = 250000
    03/22/2006 15:45:27,spid67,Unknown,Optimization Queue <nl/> Overall Memory = 1295360000 Target Memory = 1295360000 Last Notification = GROW Timeout = 6 Early Termination Factor = 5
    03/22/2006 15:45:27,spid67,Unknown,Small Query Memory Objects: Grants=0 Waiting=0 Maximum=7411 Available=7411 Limit=7411
    03/22/2006 15:45:27,spid67,Unknown,Query Memory Objects: Next Request=0 Waiting For=0 Cost=0 Timeout=0 Wait Time=0 Last Target=148230
    03/22/2006 15:45:27,spid67,Unknown,Query Memory Objects: Grants=0 Waiting=0 Maximum=140819 Available=140819 Limit=140819
    03/22/2006 15:45:27,spid67,Unknown,Global Memory Objects: <nl/> Resource= 205<nl/> Locks= 1250<nl/> SE Schema Mgr= 257<nl/> SQLCache= 43<nl/> Replication= 2<nl/> ServerGlobal= 25<nl/> XPGlobal= 2<nl/> Xact= 25<nl/> SETLS= 4<nl/> DatasetMemObjs= 8<nl/> SubpDescPmos= 4<nl/> SortTables= 2
    03/22/2006 15:45:27,spid67,Unknown,Process physical/virtual memory pressure: 0/0 System physical memory pressure: 0
    03/22/2006 15:45:27,spid67,Unknown,Procedure Cache: TotalProcs=0 TotalPages=17 InUsePages=0
    03/22/2006 15:45:27,spid67,Unknown,Buffer Counts: Committed=202424 Target=202424 Hashed=198903<nl/> Internal Reservation=40484 External Reservation=0<nl/> Stolen Potential=189563<nl/> Min Free=128 Visible=202424<nl/> Available Paging File=6137700352
    03/22/2006 15:45:27,spid67,Unknown,Buffer Distribution: Stolen=956 Free=782 Cached=1783<nl/> Database (clean)=165178 Database (dirty)=33724<nl/> I/O=0<c/> Latched=1
    03/22/2006 15:45:27,spid67,Unknown,OBJECTSTORE_LOCK_MANAGER (Total) <nl/> VM Reserved = 4096 KB <nl/> VM Committed = 4096 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 9976 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,OBJECTSTORE_SERVICE_BROKER (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 256 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,OBJECTSTORE_SNI_PACKET (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 464 KB<nl/> MultiPage Allocator = 48 KB
    03/22/2006 15:45:27,spid67,Unknown,OBJECTSTORE_LBSS (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 72 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,USERSTORE_SXC (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 16 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,USERSTORE_OBJPERM (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 312 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,USERSTORE_TOKENPERM (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 200 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,USERSTORE_DBMETADATA (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 408 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,USERSTORE_SCHEMAMGR (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 2064 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_SYSTEMROWSET (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 160 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_EVENTS (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 16 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_BROKERTO (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 8 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_BROKERREADONLY (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 32 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_BROKERRSB (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 8 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_BROKERUSERCERTLOOKUP (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 8 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_BROKERDSH (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 8 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_BROKERKEK (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 8 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_BROKERTBLACS (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 128 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_STACKFRAMES (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 0 KB<nl/> MultiPage Allocator = 8 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_XMLDBATTRIBUTE (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 8 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_XMLDBELEMENT (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 8 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_XMLDBTYPE (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 8 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_VIEWDEFINITIONS (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 16 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_NOTIF (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 16 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_TEMPTABLES (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 16 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_XPROC (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 16 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_PHDR (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 88 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_SQLCP (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 24 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,CACHESTORE_OBJCP (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 8 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,MEMORYCLERK_SQLSERVICEBROKERTRANSPORT (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 24 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,MEMORYCLERK_SOSNODE (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 2920 KB<nl/> MultiPage Allocator = 5672 KB
    03/22/2006 15:45:27,spid67,Unknown,MEMORYCLERK_HOST (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 64 KB<nl/> MultiPage Allocator = 16 KB
    03/22/2006 15:45:27,spid67,Unknown,MEMORYCLERK_BHF (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 24 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,MEMORYCLERK_SQLXP (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 16 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,MEMORYCLERK_FULLTEXT (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 16 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,MEMORYCLERK_SNI (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 32 KB<nl/> MultiPage Allocator = 16 KB
    03/22/2006 15:45:27,spid67,Unknown,MEMORYCLERK_SQLHTTP (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 8 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,MEMORYCLERK_SQLSERVICEBROKER (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 96 KB<nl/> MultiPage Allocator = 192 KB
    03/22/2006 15:45:27,spid67,Unknown,MEMORYCLERK_SQLCLR (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 8 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,MEMORYCLERK_SQLCONNECTIONPOOL (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 320 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,MEMORYCLERK_SQLSTORENG (Total) <nl/> VM Reserved = 6720 KB <nl/> VM Committed = 6720 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 1624 KB<nl/> MultiPage Allocator = 168 KB
    03/22/2006 15:45:27,spid67,Unknown,MEMORYCLERK_SQLUTILITIES (Total) <nl/> VM Reserved = 240 KB <nl/> VM Committed = 240 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 168 KB<nl/> MultiPage Allocator = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,MEMORYCLERK_SQLOPTIMIZER (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 536 KB<nl/> MultiPage Allocator = 72 KB
    03/22/2006 15:45:27,spid67,Unknown,MEMORYCLERK_SQLBUFFERPOOL (Total) <nl/> VM Reserved = 1635440 KB <nl/> VM Committed = 1635440 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 0 KB<nl/> MultiPage Allocator = 400 KB
    03/22/2006 15:45:27,spid67,Unknown,MEMORYCLERK_SQLGENERAL (Total) <nl/> VM Reserved = 0 KB <nl/> VM Committed = 0 KB <nl/> AWE Allocated = 0 KB <nl/> SM Reserved = 0 KB <nl/> SM Committed = 0 KB<nl/> SinglePage Allocator = 1664 KB<nl/> MultiPage Allocator = 1872 KB
    03/22/2006 15:45:27,spid67,Unknown,Memory node Id = 0 <nl/> VM Reserved = 1656096 KB <nl/> VM Committed = 1655368 KB <nl/> AWE Allocated = 0 KB <nl/> SinglePage Allocator = 21912 KB<nl/> MultiPage Allocator = 8592 KB
    03/22/2006 15:45:27,spid67,Unknown,Memory Manager <nl/> VM Reserved = 1660192 KB<nl/> VM Committed = 1659312 KB <nl/> AWE Allocated = 0 KB <nl/> Reserved Memory = 1024 KB <nl/> Reserved Memory In Use = 0 KB
    03/22/2006 15:45:27,spid67,Unknown,Failed Virtual Allocate Bytes: FAIL_VIRTUAL_RESERVE 131072
    03/22/2006 14:46:06,Backup,Unknown,Database was restored: Database: [DatabaseName]<c/> creation date(time): 2006/03/17(12:41:32)<c/> first LSN: 1738:64:37<c/> last LSN: 1738:93:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\SQLDATA\MSSQL.1\MSSQL\Backup\[DatabaseName].bak'}). Informational message. No user action required.
    03/22/2006 14:46:06,spid56,Unknown,Starting up database '[DatabaseName]'.
    03/22/2006 14:46:06,spid56,Unknown,Downgraded restore buffers from 4096K to 2048K
    03/22/2006 14:46:01,spid56,Unknown,The database '[DatabaseName]' is marked RESTORING and is in a state that does not allow recovery to be run.
    03/22/2006 14:46:01,spid56,Unknown,Starting up database '[DatabaseName]'.
    03/22/2006 14:42:06,spid56,Unknown,The database '[DatabaseName]' is marked RESTORING and is in a state that does not allow recovery to be run.
    03/22/2006 14:42:06,spid56,Unknown,Starting up database '[DatabaseName]'.
    03/22/2006 14:38:15,Backup,Unknown,Database backed up. Database: [DatabaseName]<c/> creation date(time): 2006/03/17(12:41:32)<c/> pages dumped: 204347<c/> first LSN: 1738:64:37<c/> last LSN: 1738:93:1<c/> number of dump devices: 1<c/> device information: (FILE=1<c/> TYPE=DISK: {'D:\SQLDATA\MSSQL.1\MSSQL\Backup\[DatabaseName].bak'}). This is an informational message only. No user action is required.

  • ldc555

    Slava0: The issue for me is that I'm not running any SP's that create objects, nor have we registered any new DLL's on SQL Server. The core system is the basic SQL Server install plus service pack 1 (both installed together only 2 months ago). The memory leak, if this is what's causing it, is coming from a native SQL Server component or from the Informix ODBC drivers also installed on the server, however the error and stack dump messages give no mention of ODBC errors.

    So far there has been no recurrence of the error, I will update again if it happens a second time.

    Sam




  • David Friesen

    We're encountering the same problem, we have a sproc that is creating and destroying objects with sp_OACreate and sp_OADestroy.

    I don't know if this is the culprit, but that is a similarity.

    We're faced with resources drying up and having to stop and restart sql server. not good.

  • Rincewind60

    csi_hugh wrote:

    spid54 CImageHelper::Init () Version-specific dbghelp.dll is not used
    spid54 CImageHelper::Init () Failed load of dbghelp.dll - Not enough storage is available to process this command.

    (down a little bit...)
    spid54 * Exception Address = 627C4C17 Module(UNKNOWN+00000000)
    spid54 * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
    spid54 * Access Violation occurred writing address 00000000

    This is from the exception log

    spid 54 Exception 0xc0000005 EXCEPTION_ACCESS_VIOLATION writing address 00000000 at 0x627C4C17

    This one's going to be pretty difficult to track down via postings. The fact that you are running com DLL's in the server adds complexity, and the exception address is far out of range of anything shipped with SQL. I'd suggest gathering up the mdmp file created for this and getting a case open with product support.

    This error likely has little, if anything, to do with the out of memory errors you are seeing



  • PaulTheSoftwareDeveloper

    (Please keep in mind that above mentioned workaround might not apply to you - first we need to understand the cause of the problem)

    What objects do you create using sp_OACreate

    The problem you are facing is Virtual Address Space leak. In order to confirm that this is indeed a problem you might set up a view, described here http://blogs.msdn.com/slavao/archive/2005/01/26/360759.aspx, and collect output every 5min. (Please post the outputs from the original, one in a mid, and the last one when you hit the problem)

    Now we need to ping down who is leaking - it will be harder, though base on experience it could be several possibilities:

    A. sp_OACreate/sp_ODestroy code leaks VAS - I will do quick code review to make sure this is not happening

    B. Object that you create using sp_OACreate doesn't get really destroy due to refcounting issues. This usually happens due to incorrect refcount implementation by an implementer of the COM object. If the COM object is implemented by you please review the lifetime management semantics of the object.

    C. sp_OACreate/sp_OADestroy forces constant dll load/unload - COM dll leaves allocated VAS behind. This usually happens due to a leak in dll that SQL Server process ends up loading and unloading. If you own the dll please make sure that you allocated/deallocate correctly all process global and per thread allocated memory. Please also make sure that you destroy all Windows heaps that you create during the time of dll load

  • charlv

    Tim Please post the full message from your sql server errorlog. Out of memory errors simply indicate that a new request cannot be satisfied, to determine the cause of the problem one must determine what is currenlty holding memory resources.



  • Paul_IRET

    Please keep in mind that it is not necessary for the misbehaving component to show up in the report. HavinIg said that it appears that people are hitting two types of problems resulting in the same effect - out of Virtual Address Space, VAS.

    Problem 1

    - Applications using sp_OACreate (Mark.Stockton, Mister2zx3)

    Problem 2

    - Applications using linked servers (csi_hugh, Sam Vella)

    These problems most likely are completely independent and should be viewed separately.

    In order for us to diagnose the issues we need:

    A. Set of outputs from the view I pointed you to in my previous reply to this posts

    B. Description of your applications, specifically:

    - Type of objects you create using sp_OACreate

    - Type of linked server you use, including OLEDB over ODBC

    - Version of third party dlls you are using, i.e Informix ODBC driver

    C. Output from sys.dm_os_loaded_modules
  • Strange out of memory error on 2005
Answer this question