SQLServer 2012 consistently requires reboot

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 2012 Forums

SQL Server Administration (2012)

SQLServer 2012 consistently requires reboot

Author

Topic

Zhetoman
Starting Member

5 Posts

Posted - 2015-02-05 : 09:56:19

I have Windows 7 and am running Avast anti-virus software. Avast is configured to ignore the executables related to SQLServer.

3 or 4 days a week after booting up my workstation/server computer, SQLServer fails. Error message says it is not running. I am unable to start/restart the services from the Services panel.

I have to reboot the computer to get SQLServer running. Rather annoying to have to reboot the computer 3 or 4 times a week.

Is anyone else having this issue and how can I determine what is interfering with SQLServer startup during the bootup process?

gbritton
Master Smack Fu Yak Hacker

2780 Posts

Posted - 2015-02-05 : 10:52:51

What version of SQL Server are you running?

Why are you running it on Windows 7 and not on Windows Server (2008 or 2012)?

Zhetoman
Starting Member

5 Posts

Posted - 2015-02-05 : 11:59:06

SQLServer 2012 Express, SQL Server Native Client 11.0

I am running SQLServer on a Windows 7 Pro desktop because it is installed as a local instance for prototype development and testing.

gbritton
Master Smack Fu Yak Hacker

2780 Posts

Posted - 2015-02-05 : 12:24:50

Up to date on Service Packs and CUs?

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2015-02-05 : 12:38:34

What does the event log show when the service fails? Most likely errors are in the application log. Also check the SQL Server Error Log.

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

Zhetoman
Starting Member

5 Posts

Posted - 2015-02-05 : 13:49:06

Here are entries from the first boot-up when SQLServer failed to startup.

*** Windows System Log

8:27:30 AM - Error
The SQL Server (SQLEXPRESS) service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

8:27:28 AM - Error
A timeout was reached (30000 milliseconds) while waiting for the SQL Server (SQLEXPRESS) service to connect.

*** Windows Application Log

8:27:28 AM - Warning
Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.

1 user registry handles leaked from \Registry\User\S-1-5-80-3880006512-4290199581-1648723128-3569869737-3631323133: Process 1204 (\Device\HarddiskVolume3\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Binn\sqlservr.exe) has opened key \REGISTRY\USER\S-1-5-80-3880006512-4290199581-1648723128-3569869737-3631323133\Control Panel\International

8:27:36 AM - Warning
The configuration of the SQL instance MSSQLSERVER is not valid.

8:27:45 AM - Error
Event 19011, MSSQLServer
SuperSocket info: FillAddress(MSAFD Tcpip [TCP/IPv6]) : Error 0.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2015-02-05 : 14:03:07

I would disable Avast to see if it's the culprit. Excluding the SQL Server executables is not enough. There's over 50 file extensions that should be ignored. Microsoft has an article on it which I don't have handy.

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

Zhetoman
Starting Member

5 Posts

Posted - 2015-02-05 : 14:03:30

Follow - Up

There are no entries in the SQL Server Error Log for the first time the computer was booted up.

The entries in today's log begin at the time of the re-boot.

I checked the folder at C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Logs. All log files are time stamped with times starting at the re-boot. No logs or history exists for the original boot-up that failed.

Zhetoman
Starting Member

5 Posts

Posted - 2015-02-05 : 14:05:57

I will consider disabling Avast. That is a little worrisome as there are times when the computer can go 3 or 4 days without SQLServer failing. The failure is sporadic. Not certain I want to run with Avast disabled that long.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2015-02-05 : 14:16:10

Then find the article I am referring to that shows what Microsoft says is crucial to exclude from anti-virus software.

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

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources