Community
Showing results for 
Search instead for 
Do you mean 
Reply

SQL Server keeps stopping over night

New Member
Posts: 21
Country: United States

SQL Server keeps stopping over night

Hello All,

 

Since the beginning of the week, we have had a problem with the SQLservr.exe stopping throughout the night.  How we have fixed it is every morning we come in, someone has to go to the server and click the SQL configuration panel and it shows the SQL server stopped, we have to restart it and then everything will work fine until sometime over night.

 

Does anyone know what could be causing this issue?

 

Thanks!!

Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: SQL Server keeps stopping over night

You want to have a look in the Windows event log for a specific error that might be causing it. Also look at the SQL Logs

What version of ACT!? Different versions of ACT! use different versions of SQL. One thing I've seen cause this is a SQL update from Microsoft that's attempting to apply and failing.
New Member
Posts: 21
Country: United States

Re: SQL Server keeps stopping over night

Thanks for the info I will have a look.

 

My version of ACT! is Premium 2010 Version 12.0.409.0 Hotfix 3

 

Thanks Again!!

Platinum Elite Contributor
Posts: 14,384
Country: Australia

Re: SQL Server keeps stopping over night

You probably should update to Service Pack 1, and then the latest Hotfix (2 separate downloads). Note: If sharing a database, this needs to be done on ALL systems and sync server (if separate)
New Member
Posts: 21
Country: United States

Re: SQL Server keeps stopping over night

Good Morning All, I have tried to update ACT! and is shows that I have the most updated version. I went to the error log for the SQL server and for the last 14 Days, the SQL server has been stopping over night at 3:00 AM. Here is information from the error log that pertains to the failure (The bottom of the list shows the server shutdown): "2012-04-10 08:06:48.65 spid5s Recovery is complete. This is an informational message only. No user action is required. 2012-04-10 08:06:48.67 spid11s The Service Broker protocol transport is disabled or not configured. 2012-04-10 08:06:48.67 spid11s The Database Mirroring protocol transport is disabled or not configured. 2012-04-10 08:06:48.69 spid5s Launched startup procedure 'PRC_MASTER_AUTOSTARTUPS'. 2012-04-10 08:06:48.74 spid11s Service Broker manager has started. 2012-04-10 08:06:49.20 spid51s ISENABLED = 1 2012-04-10 08:06:49.20 spid51s NUM_DATABASES = 3 2012-04-10 08:06:49.20 spid51s NUM_DAYS = 30 2012-04-10 08:06:49.31 spid51s ************************* PJOMASTERDATABASE (2012-04-09T21:04:24) ************************* 2012-04-10 08:06:49.31 spid51s Starting up database 'PJOMASTERDATABASE'. 2012-04-10 08:06:51.31 spid51s Error: 515, Severity: 16, State: 2. 2012-04-10 08:06:51.31 spid51s Cannot insert the value NULL into column 'GRABFIELD', table 'tempdb.dbo.#TEMPTB_____________________________________________________________________________________________________________000000000005'; column does not allow nulls. INSERT fails. 2012-04-10 18:04:30.46 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event. 2012-04-10 18:49:39.05 spid1s Server resumed execution after being idle 1790 seconds. Reason: timer event. 2012-04-10 19:34:42.64 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event. 2012-04-10 20:19:46.24 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event. 2012-04-10 21:04:49.84 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event. 2012-04-10 21:49:53.44 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event. 2012-04-10 22:34:57.05 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event. 2012-04-10 23:20:00.64 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event. 2012-04-11 00:05:04.24 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event. 2012-04-11 00:50:07.84 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event. 2012-04-11 01:35:11.43 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event. 2012-04-11 02:20:15.05 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event. 2012-04-11 03:00:18.13 Server Server resumed execution after being idle 1490 seconds: user activity awakened the server. This is an informational message only. No user action is required. 2012-04-11 03:00:18.93 spid11s Service Broker manager has shut down. 2012-04-11 03:00:19.42 spid5s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required. 2012-04-11 03:00:19.42 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required." Has anyone else ran into this, if someone would like me to post the entire error log, please let me know. Currently every morning someone has to open the SQL server manager and click on the SQL Server (ACT7) and click start and then everything is running fine. Thanks!! Brent
Platinum Super Contributor
Posts: 5,275
Country: USA

Re: SQL Server keeps stopping over night

Check for any Windows updates trying to apply to SQL. The ACT7 service is password protected and the update will fail to apply - leaving the service stopped.
Greg Martin
Sage