• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3839
  • Last Modified:

SQL server service keeps stopping

I run sql server 2005 for a couple of databases on a Win 2003 x64 bit terminal server. No changes made in a long itme. I use Backup exec 2010 with sql agent to back it up as well as sqlbackupandftp.com (free version) as second backup. Lately, sql db service is stopping at night. Doesnt seem to be related to backup jobs. Having trouble isolationg problem. Not sure how to even find the time this is happening in the event viewer. Any help would be appreciated!
0
M_Epstein
Asked:
M_Epstein
7 Solutions
 
Christopher GordonSenior Developer AnalystCommented:
Have you taken a look at the SQL Server ErrorLog file:

C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log.
0
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
Ok, Check for the below things:

1. If your Evaluation edition expired, then this will happen.
2. Make sure that your startup account is either LocalSystem or some other domain account with appropriate privileges.
3. Check whether you have sufficient disk space in the SQL Server folders else it can happen.
4. Do you have any DBCC CHECK statements running as a task during night every day
http://support.microsoft.com/default.aspx?scid=kb;en-us;961123

Its recommended to apply Latest Service Pack SP4 for SQL Server 2005 to fix most of the issues.
0
 
M_EpsteinAuthor Commented:
Not sure how to interpret this.

2011-05-09 21:28:28.26 Server      Microsoft SQL Server 2005 - 9.00.4053.00 (Intel X86)
      May 26 2009 14:24:20
      Copyright (c) 1988-2005 Microsoft Corporation
      Express Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

2011-05-09 21:28:28.29 Server      (c) 2005 Microsoft Corporation.
2011-05-09 21:28:28.29 Server      All rights reserved.
2011-05-09 21:28:28.29 Server      Server process ID is 36196.
2011-05-09 21:28:28.29 Server      Authentication mode is MIXED.
2011-05-09 21:28:28.29 Server      Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2011-05-09 21:28:28.29 Server      This instance of SQL Server last reported using a process ID of 2012 at 5/7/2011 3:00:35 AM (local) 5/7/2011 7:00:35 AM (UTC). This is an informational message only; no user action is required.
2011-05-09 21:28:28.30 Server      Registry startup parameters:
2011-05-09 21:28:28.32 Server             -d C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2011-05-09 21:28:28.32 Server             -e C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2011-05-09 21:28:28.32 Server             -l C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2011-05-09 21:28:28.35 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-05-09 21:28:28.35 Server      Detected 8 CPUs. This is an informational message; no user action is required.
2011-05-09 21:28:28.82 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2011-05-09 21:28:29.87 Server      Database mirroring has been enabled on this instance of SQL Server.
2011-05-09 21:28:29.98 spid4s      Starting up database 'master'.
2011-05-09 21:28:30.21 spid4s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2011-05-09 21:28:30.42 spid4s      SQL Trace ID 1 was started by login "sa".
2011-05-09 21:28:30.46 spid4s      Starting up database 'mssqlsystemresource'.
2011-05-09 21:28:30.50 spid4s      The resource database build version is 9.00.4035. This is an informational message only. No user action is required.
2011-05-09 21:28:30.72 spid8s      Starting up database 'model'.
2011-05-09 21:28:30.73 spid4s      Server name is 'METS'. This is an informational message only. No user action is required.
2011-05-09 21:28:30.74 spid4s      Starting up database 'msdb'.
2011-05-09 21:28:30.88 spid8s      Clearing tempdb database.
2011-05-09 21:28:31.28 spid8s      Starting up database 'tempdb'.
2011-05-09 21:28:31.31 Server      A self-generated certificate was successfully loaded for encryption.
2011-05-09 21:28:31.32 Server      Server is listening on [ 'any' <ipv4> 1433].
2011-05-09 21:28:31.33 spid4s      Recovery is complete. This is an informational message only. No user action is required.
2011-05-09 21:28:31.36 spid11s     The Service Broker protocol transport is disabled or not configured.
2011-05-09 21:28:31.37 spid11s     The Database Mirroring protocol transport is disabled or not configured.
2011-05-09 21:28:31.40 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2011-05-09 21:28:31.40 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2011-05-09 21:28:31.40 Server      Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2011-05-09 21:28:31.44 spid11s     Service Broker manager has started.
2011-05-09 21:28:31.78 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
M_EpsteinAuthor Commented:
The last error log may be after I restarted the service. This one may have more info

2011-05-06 18:53:56.70 Server      Microsoft SQL Server 2005 - 9.00.4053.00 (Intel X86)
      May 26 2009 14:24:20
      Copyright (c) 1988-2005 Microsoft Corporation
      Express Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

2011-05-06 18:53:56.78 Server      (c) 2005 Microsoft Corporation.
2011-05-06 18:53:56.78 Server      All rights reserved.
2011-05-06 18:53:56.78 Server      Server process ID is 2012.
2011-05-06 18:53:56.78 Server      Authentication mode is MIXED.
2011-05-06 18:53:56.79 Server      Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2011-05-06 18:53:56.79 Server      This instance of SQL Server last reported using a process ID of 2032 at 5/6/2011 6:51:00 PM (local) 5/6/2011 10:51:00 PM (UTC). This is an informational message only; no user action is required.
2011-05-06 18:53:56.81 Server      Registry startup parameters:
2011-05-06 18:53:56.84 Server             -d C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2011-05-06 18:53:56.84 Server             -e C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2011-05-06 18:53:56.84 Server             -l C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2011-05-06 18:53:56.93 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-05-06 18:53:56.93 Server      Detected 8 CPUs. This is an informational message; no user action is required.
2011-05-06 18:53:57.90 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2011-05-06 18:54:00.98 Server      Database mirroring has been enabled on this instance of SQL Server.
2011-05-06 18:54:01.12 spid5s      Starting up database 'master'.
2011-05-06 18:54:01.36 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2011-05-06 18:54:01.57 spid5s      SQL Trace ID 1 was started by login "sa".
2011-05-06 18:54:01.62 spid5s      Starting up database 'mssqlsystemresource'.
2011-05-06 18:54:01.64 spid5s      The resource database build version is 9.00.4035. This is an informational message only. No user action is required.
2011-05-06 18:54:01.83 spid8s      Starting up database 'model'.
2011-05-06 18:54:01.84 spid5s      Server name is 'METS'. This is an informational message only. No user action is required.
2011-05-06 18:54:01.84 spid5s      Starting up database 'msdb'.
2011-05-06 18:54:02.11 spid8s      Clearing tempdb database.
2011-05-06 18:54:02.92 Server      A self-generated certificate was successfully loaded for encryption.
2011-05-06 18:54:02.94 Server      Server is listening on [ 'any' <ipv4> 1433].
2011-05-06 18:54:02.95 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2011-05-06 18:54:02.95 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2011-05-06 18:54:02.95 Server      Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2011-05-06 18:54:03.20 spid8s      Starting up database 'tempdb'.
2011-05-06 18:54:03.25 spid5s      Recovery is complete. This is an informational message only. No user action is required.
2011-05-06 18:54:03.27 spid11s     The Service Broker protocol transport is disabled or not configured.
2011-05-06 18:54:03.28 spid11s     The Database Mirroring protocol transport is disabled or not configured.
2011-05-06 18:54:03.33 spid11s     Service Broker manager has started.
2011-05-06 18:54:03.80 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
2011-05-06 19:37:24.39 Server      Server resumed execution after being idle 2569 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2011-05-06 19:37:24.45 spid51      Starting up database 'Network Database'.
2011-05-06 19:37:25.07 spid51      Starting up database 'Primary Database SQL'.
2011-05-06 19:37:25.16 spid8s      SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-05-06 19:37:25.17 spid8s      SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-05-06 19:37:25.17 spid8s      SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-05-06 19:37:26.46 spid51      Starting up database 'Network Database'.
2011-05-06 19:37:26.52 spid51      Starting up database 'Primary Database SQL'.
2011-05-06 19:37:26.60 spid51      Starting up database 'Network Database'.
2011-05-06 19:37:33.22 spid52      SQL Server blocked access to procedure 'dbo.sp_get_sqlagent_properties' of component 'Agent XPs' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', see "Surface Area Configuration" in SQL Server Books Online.
2011-05-06 19:37:33.95 spid52      Starting up database 'Primary Database SQL'.
2011-05-06 19:37:34.39 spid52      Starting up database 'Primary Database SQL'.
2011-05-06 19:38:45.23 spid51      Starting up database 'Network Database'.
2011-05-06 19:38:45.29 spid51      Starting up database 'Primary Database SQL'.
2011-05-06 19:38:46.38 spid51      Starting up database 'Network Database'.
2011-05-06 19:38:46.44 spid51      Starting up database 'Primary Database SQL'.
2011-05-06 19:38:49.99 spid52      SQL Server blocked access to procedure 'dbo.sp_get_sqlagent_properties' of component 'Agent XPs' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', see "Surface Area Configuration" in SQL Server Books Online.
2011-05-06 19:38:50.59 spid52      Starting up database 'Primary Database SQL'.
2011-05-06 19:38:51.17 spid52      Starting up database 'Primary Database SQL'.
2011-05-06 20:01:25.39 Server      Server resumed execution after being idle 436 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2011-05-06 20:23:45.21 spid22s     SQL Server has encountered 12 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-05-06 20:23:45.22 spid22s     SQL Server has encountered 12 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-05-06 20:23:45.22 spid22s     SQL Server has encountered 12 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-05-06 21:04:28.39 Server      Server resumed execution after being idle 1529 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2011-05-06 21:04:28.85 spid51      Using 'xplog70.dll' version '2005.90.4035' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
2011-05-06 21:04:29.70 spid52      DBCC CHECKDB (master) WITH physical_only executed by EPS\symbackup found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.
2011-05-06 21:04:35.69 spid52      DBCC CHECKDB (mssqlsystemresource) WITH physical_only executed by EPS\symbackup found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 5 seconds.
2011-05-06 21:04:36.03 spid52      DBCC CHECKDB (model) WITH physical_only executed by EPS\symbackup found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.
2011-05-06 21:04:37.61 spid52      DBCC CHECKDB (msdb) WITH physical_only executed by EPS\symbackup found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 1 seconds.
2011-05-06 21:04:37.64 spid52      Starting up database 'Network Database'.
2011-05-06 21:04:38.61 spid52      DBCC CHECKDB (Network Database) WITH physical_only executed by EPS\symbackup found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.
2011-05-06 21:04:38.63 spid52      Starting up database 'Primary Database SQL'.
2011-05-06 21:04:38.77 spid20s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-05-06 21:04:38.77 spid20s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-05-06 21:04:38.77 spid20s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-05-06 21:04:39.25 spid52      DBCC CHECKDB (Primary Database SQL) WITH physical_only executed by EPS\symbackup found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.
2011-05-06 21:04:39.85 Backup      Database backed up. Database: master, creation date(time): 2011/05/06(18:54:01), pages dumped: 364, first LSN: 971:392:50, last LSN: 971:424:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'BACKUP{387d70f4-f470-4b85-8b69-281948496064}'}). This is an informational message only. No user action is required.
2011-05-06 21:04:40.11 spid51      Starting up database 'master4IDR'.
2011-05-06 21:04:40.12 spid51      The database 'master4IDR' is marked RESTORING and is in a state that does not allow recovery to be run.
2011-05-06 21:04:40.16 spid51      Starting up database 'master4IDR'.
2011-05-06 21:04:40.33 Backup      Database was restored: Database: master4IDR, creation date(time): 2011/05/06(18:54:01), first LSN: 971:392:50, last LSN: 971:424:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'RESTORE_restore_'}). Informational message. No user action required.
2011-05-06 21:04:43.65 Backup      Database backed up. Database: master, creation date(time): 2011/05/06(18:54:01), pages dumped: 364, first LSN: 972:88:54, last LSN: 972:120:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'master_00__960247a1_4898_4076_846f_b5c63e132cac_'}). This is an informational message only. No user action is required.
2011-05-06 21:04:43.75 Backup      Database backed up. Database: model, creation date(time): 2003/04/08(09:13:36), pages dumped: 163, first LSN: 154:288:37, last LSN: 154:312:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'BACKUP{804784f1-0962-431d-a092-3178f6723949}'}). This is an informational message only. No user action is required.
2011-05-06 21:04:43.88 spid51      Starting up database 'model4IDR'.
2011-05-06 21:04:43.90 spid51      The database 'model4IDR' is marked RESTORING and is in a state that does not allow recovery to be run.
2011-05-06 21:04:43.93 spid51      Starting up database 'model4IDR'.
2011-05-06 21:04:44.08 Backup      Database was restored: Database: model4IDR, creation date(time): 2003/04/08(09:13:36), first LSN: 154:288:37, last LSN: 154:312:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'RESTORE_restore_'}). Informational message. No user action required.
2011-05-06 21:04:47.21 Backup      Database backed up. Database: model, creation date(time): 2003/04/08(09:13:36), pages dumped: 163, first LSN: 154:352:37, last LSN: 154:376:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'model_00__481e1424_0bab_4943_a2f8_2b44cedb99b1_'}). This is an informational message only. No user action is required.
2011-05-06 21:04:49.44 Backup      Database backed up. Database: msdb, creation date(time): 2005/10/14(01:54:05), pages dumped: 1421, first LSN: 348:304:202, last LSN: 348:392:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'msdb_00__b97c2b2f_fbb6_4456_899d_04c0f6ef2f9a_'}). This is an informational message only. No user action is required.
2011-05-06 21:04:49.47 spid51      Starting up database 'Network Database'.
2011-05-06 21:04:51.92 Backup      Database backed up. Database: Network Database, creation date(time): 2009/08/12(17:09:26), pages dumped: 3507, first LSN: 139:1838:37, last LSN: 139:1854:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'Network_Database_00__28618637_97cc_4e0a_b82e_6d2054dc001e_'}). This is an informational message only. No user action is required.
2011-05-06 21:04:51.95 spid51      Starting up database 'Primary Database SQL'.
2011-05-06 21:04:54.20 Backup      Database backed up. Database: Primary Database SQL, creation date(time): 2009/08/14(10:57:01), pages dumped: 763, first LSN: 51:392:37, last LSN: 51:408:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'Primary_Database_SQL_00__39c99a18_afc6_4027_9c8f_3a30653d6cb4_'}). This is an informational message only. No user action is required.
2011-05-07 00:14:34.83 Server      Server resumed execution after being idle 10468 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2011-05-07 00:14:34.99 spid51      Starting up database 'Network Database'.
2011-05-07 00:14:35.20 spid51      Starting up database 'Primary Database SQL'.
2011-05-07 00:14:35.29 spid14s     SQL Server has encountered 12 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-05-07 00:14:35.29 spid14s     SQL Server has encountered 12 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-05-07 00:14:35.29 spid14s     SQL Server has encountered 12 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-05-07 00:14:44.20 spid51      Starting up database 'Network Database'.
2011-05-07 00:14:44.24 spid51      Starting up database 'Primary Database SQL'.
2011-05-07 01:00:03.29 spid1s      Server resumed execution after being idle 1805 seconds. Reason: timer event.
2011-05-07 01:33:31.18 Server      Server resumed execution after being idle 1095 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2011-05-07 01:33:31.30 spid51      Starting up database 'Network Database'.
2011-05-07 01:33:31.47 spid51      Starting up database 'Primary Database SQL'.
2011-05-07 01:33:31.58 spid23s     SQL Server has encountered 4 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-05-07 01:33:31.59 spid23s     SQL Server has encountered 4 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-05-07 01:33:31.59 spid23s     SQL Server has encountered 4 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2011-05-07 01:33:39.04 spid51      Starting up database 'Network Database'.
2011-05-07 01:33:39.08 spid51      Starting up database 'Primary Database SQL'.
2011-05-07 03:00:33.86 Server      Server resumed execution after being idle 4304 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2011-05-07 03:00:34.97 spid11s     Service Broker manager has shut down.
2011-05-07 03:00:35.30 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.
2011-05-07 03:00:35.31 spid5s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
0
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
>> Service Broker manager has shut down.

Seems like your Server machine is restarted which shuts down SQL Server service.
Either Windows Update or some activity is scheduled to run during that time which is causing the system shutdown thereby stopping sql server..
0
 
M_EpsteinAuthor Commented:
The server is not scheduled to restart. Win update has been running for a few years on this server with no problem. Even if server restarted, shouldnt the sql service automatically restart as it says for that service?

HOw do i pin this down further?
0
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
>> Even if server restarted, shouldnt the sql service automatically restart as it says for that service?

Yes, it should.

Check for the below things:

1. Startup of SQL Server service should be set to Start Automatically.
2. Make sure Startup account is set to Localsystem or some other Domain account with appropriate privileges.
3. Check in Windows Event viewer for list of events happening in the system when SQL Server service is stopping.
0
 
M_EpsteinAuthor Commented:
SQL server has always been set to start automatically

Account has always been Local System

How do I determine just when the service is stopping? All I know is that it is happening at night after I leave work and before I get in in the am
0
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
Check it in Windows Event viewer or in SQL Server event logs..
0
 
M_EpsteinAuthor Commented:
I looked in the windowsevent viewer. Could nto find it.

HOw do I find the latter? Sorry, not very experienced with this.
0
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
Not a problem..
1. Open SQL Server Management Studio (SSMS) and connect to your SQL Server instance.
2. Expand SQL Server Agent -> Choose Error Logs
3. Open Current log file with latest timestamp..
4. Check for any events & timestamp when SQL server service is last shutdown along with reason for shutdown.
0
 
VENKAT KOKULLASQL Server DBACommented:
Might be that the user account under which automatic updates were running wasn't a local machine admin. Automatic updates were in the queue, the machine tried to apply them to SQL 2005, was able to shut down the service but never restarted it after failing to apply the patches.

Let me know if you are still facing the issue..!

--Venkat
0
 
M_EpsteinAuthor Commented:
Actually, you are close. I just solved the problem. The SQL 2005 Express SP4 update was trying to install, but couldn't. That was stopping the service. I then did an update of MSXML6 (which did not run too smoothly) and then manually updated the SP4. That did not satisfy the win updater so I hid the update to prevent further stopping of the service.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now