SQl Server went down

Question

SQl Server went down

Krasavita

SSC-Insane

Points: 23138
More actions
April 4, 2011 at 7:43 am

#145066

Guys,
My production server goes down every 2-3 weeks. I can't figure out why?
1.How can I put alerts to find out when it when down? I want to get email SQL agent went down or SQL Server went down or running low memory.
2.What should I check for why it is going down, we just added more RAM and we have plenty of memory on the drives.
Thank you

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

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

Shawn Melton SSC-Insane Points: 24685 More actions · Answer 1

I would worry about number 2 before I address number 1. The SQL Server error logs and Windows Application Event Logs should give you some information on what or why the service is going down.

When you say it is going down, is SQL Server services shutting down, is the server itself rebooting, ???

Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton

Krasavita SSC-Insane Points: 23138 More actions · Answer 2

SQL agent went down and I have to re started.

This is erroe from sql logs:

SQL Server is terminating because of fatal exception e06d7363. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).

2011-04-02 06:02:59.20 Server CImageHelper::Init () Version-specific dbghelp.dll is not used

2011-04-02 06:02:59.20 Server CImageHelper::Init () Failed load of dbghelp.dll - Not enough storage is available to process this command.

steveb. SSC-Forever Points: 46733 More actions · Answer 3

one of the errors relates to storage, have you checked this?

Krasavita SSC-Insane Points: 23138 More actions · Answer 4

Windows log:

Event Log: Application Event Type: Error Event Source: MSSQLSERVER Event Category: Server Event ID: 18056 Date: 4/2/2011 3:00:04 AM User: Ccc\ccc_YYYY Computer: Database1 Description: The client was unable to reuse a session with SPID 222, which had been reset for connection pooling. This error may have been caused by an earlier operation failing. Check the error logs for failed operations immediately before this error message.