Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Edit 3 & 4 Added

Although the SQL Server instance is set to run automatically and TCP also is enabled in its Network Configuration, the SQL Server is stopped after each system restart. I have to go into the configuration and start it again manually.

Edit : It's default account is "Network Service"

What is the cause of this, and what solutions are available?

Edit 5 - Repost

The Event Log :


Edit 4 : (Expired Link)

Here is the Last Error Log of today

Edit3 : - Part 2/2

Seems that this error doesn't appear on every start cause It's started after my last restart, the time that I wanted to clear and refresh the Logs and probing the error :D

I think in the Event Log as other experts mentioned there are good informative points and I hope we could find the real problem e.g some errors are saying Network Service couldn't login ... but after a minute or so it seems that It logged on !

share|improve this question

migrated from Mar 9 '12 at 14:25

This question came from our site for professional and enthusiast programmers.

How is the SQL Server service configured? – Oded Mar 9 '12 at 14:21
What does the event log say? (Also, this should really be on Database Administrators SE – Thomas Stringer Mar 9 '12 at 14:24
I'll check the Event Log , I posted about it's configuration, What else should I say ? – Sypress Mar 9 '12 at 14:29
@Shark , this could be the way I should observe similar errors but unfortunately I'm not accustomed to the Event Logs, Where Should I check windows Event viewer ? – Sypress Mar 9 '12 at 14:34
@Oded if any other info should I provide please tell me – Sypress Mar 9 '12 at 14:37

Is it possible that you have storage that is coming online after the SQL Server starts? For instance, if your master database is on SAN storage that is not being attached to the server until after SQL Server tries to start up. This will cause SQL Server to appear in a Stopped state after a restart, but work when you manually start it. You can create a dependency for the SQL Server service to prevent this.

Do you have a copy of the error log AFTER the start up? The one you provided appears that it is after you manually started it and then had it shutdown.

share|improve this answer
master seems to be on local from the sql logs. – tony roth Mar 9 '12 at 15:31
Thanks for your response, sorry being late at that time I couldn't give the needed reply, Now everything seems up-to-time and accurate, If any other info is needed I'll provide, the SQL Server is in local as said, thanks in advance – Sypress Mar 10 '12 at 10:53
Looking at your last error log - it says that NetworkService is unable to open a specified database. Your service account should have master set as it's default database. I am wondering if it is set to a different database that has not yet gone through startup recovery some of the time. Ensure the default database is master. – Brian Knight Mar 10 '12 at 19:14
@Brian sorry Mr.Brian I didn't see your comment, maybe no notification, anyway yes it's "master", seems that the result happens not every time. any suggestions ? – Sypress Mar 12 '12 at 20:38
In addition seems that there are 2 "Network Service" and "sa" accounts : one is "NT SERVICE\MSSQL$PROSERVER", the other "NT AUTHORITY\NETWORK SERVICE", it wasn't something I decide, maybe that happened during installation unintentionally is it good ? or could it be the cause of some errors ? – Sypress Mar 12 '12 at 20:47

This is a named instance, that I'm guessing was setup to support another piece of software. Check the dependencies of the SQL Server service and see if it's dependent on another service which isn't being started for some reason.

share|improve this answer
I'm trying to get it's Event Log, As I remember it wasn't related to Some other Server programs such as sharepoint, in my previous installations of Sql Server I never experienced this, I think in this setup I added some credentials with granted permissions for ease of access, further than that I couldn't remember anything to be dependant, e.g could it be dependant to sa Account ?? shoul agent be run this way ? – Sypress Mar 9 '12 at 20:46
Look in the services applet in Admin tools to see if the MSSQL$PROSERVER service is dependent on any other drivers or services. If the service isn't starting there should be something listed in the Application or System log which says why the service wasn't started or why it failed. If the service isn't starting odds are there won't be anything in the SQL ERRORLOG file. The SQL Instance isn't dependent on the sa account. – mrdenny Mar 10 '12 at 1:47
No Sir, It's not dependent to anything, Just as expected sa is dependent to it nothing else, Now I can see a weird change, It's started automatically ! I'll add a piece of info to my first post – Sypress Mar 10 '12 at 8:07
Can you repost the errorlog info? The links aren't working. – mrdenny Mar 12 '12 at 4:07
Reposted the Event Log : – Sypress Mar 12 '12 at 10:11

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.