The SQL Server service terminated

Question

The SQL Server service terminated

Alone

Right there with Babe

Points: 783
More actions
April 1, 2014 at 4:53 am

#285044

The SQL Server service terminated with the following error:
Ran out of memory
OS details: windows 2008 enterprise
SQL Vesrion: sqlserver 2005 standered edition
Service pack: sp4
how to troubleshoot the issue?

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

Start with the latest error log and any relevant-looking messages from the Windows event log, system and application logs.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

SQLBuddy123 One Orange Chip Points: 28294 More actions · Answer 2

Also check if you had any memory dump files created by SQL Server in it's log folder.

--

SQLBuddy

Alone Right there with Babe Points: 783 More actions · Answer 3

Before terminating sql services I got below error message in sqlserver error logs:

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>]