SQL service terminated due to ran out of memory

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2005 Forums

SQL Server Administration (2005)

SQL service terminated due to ran out of memory

Author

Topic

litudeb
Starting Member

1 Post

Posted - 2014-04-04 : 07:44:15

The SQL Server service terminated with the following error:
Ran out of memory.Please help to fix this..

OS details: windows 2008 enterprise
SQL Vesrion: sqlserver 2005 standered edition
Service pack: sp4

The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.
Error: 17138, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
Error: 1204, Severity: 19, State: 4.
The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.
Error: 1204, Severity: 19, State: 4.
The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.
Error: 1204, Severity: 19, State: 4.
The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time. Rerun your statement when there are fewer active users. Ask the database administrator to check the lock and memory configuration for this instance, or to check for long-running transactions.
Error: 19032, Severity: 10, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.
Error: 701, Severity: 17, State: 123.
There is insufficient system memory to run this query.
Error: 17188, Severity: 16, State: 1.
SQL Server cannot accept new connections, because it is shutting down. The connection has been closed. [CLIENT: <local machine>]

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2014-04-04 : 16:29:59

Looks like you've got a hardware resource issue. You need to take a look at your queries as well as your hardware.

Tara Kizer
SQL Server MVP since 2007
http://weblogs.sqlteam.com/tarad/

jackv
Master Smack Fu Yak Hacker

2179 Posts

Posted - 2014-04-09 : 01:47:12

To find the cause requires to search for a memoryclerk or cachestore which consumes the highest memory.

First step is to identify which memoryclerk or cachestore is consuming the highest memory.When you inspect the Error Logs , there is normally the DBCC memorystatus output.
There is some more information on :http://www.sqlserver-dba.com/2012/11/sql-server-error-701-there-is-insufficient-system-memory.html
for troubleshooting error 701

Jack Vamvas
--------------------
http://www.sqlserver-dba.com

Shanky
Yak Posting Veteran

84 Posts

Posted - 2014-07-09 : 07:28:19

Hi,
This seems to me like resource contention issue. What was the query running when you got this message. Can you post output of DBCC MEMORYSTATUS command for analysis. IMO this error occured because there are not enough system locks to complete the current command and this could be because system had very low memory. Locks require memory and every lock has some memory associated with it.

Regards
Shanky
http://social.technet.microsoft.com/wiki/contents/articles/24253.list-of-articles-by-shanky.aspx

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources