Ad:

MS SQL Discussion Thread
Unsolved
Views: 9325

Jun 20th, 2006

SQL 2005 won't start after critical update reboot

Expand Post »

I'm not sure if this is a Server 2003 issue or an MSSQL issue, so pardon the cross-post.

I have created a local user called "sql-daemon" to run MSSQL 2005. At the onset, everything works fine: I can reboot the server and all SQL processes start as expected.

Then, one day, I discover that SQL is not running. I check the server and find messages in the event logs stating that various SQL services couldn't start because of an authentication issue. The solution: from Services, I track down the SQL items and retype the (unchanged) password for my sql-daemon user. The first of these returns a message that "sql-daemon has been allowed to Run as Service." Peachy.

So, my question is: What is causing my sql-daemon user to be denied permission to Run as Service?

This has happened twice since the server was brought online back in March. The first time was by complete surprise and thought a fluke. The second time was June 16 - we caught the server as it was rebooting after a critical Windows update. After it rebooted, SQL would not start as described above. We have since fixed the auto-update settings to avoid rebooting without our knowledge, but we really want to be sure that SQL will be able to start successfully next time.

Thanks for your ideas!
~ Aaron

Similar Threads

SQL 2005 upgrade questions in MS SQL
sql 2005 to sql 2000 in MS SQL

abahmer

Reputation Points: 10

Solved Threads: 0

Newbie Poster

Offline

4 posts
since Jun 2006

Permalink

Jul 14th, 2006

Re: SQL 2005 won't start after critical update reboot

This problem was also happening to my SQL server and I was seeing the same error in the Event Viewer after a reboot; Event ID 7041 - The MSSQLSERVER service was unable to log on as BCB\sqladmin with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.

I found that the account trying to start the services was added to the local computer policy "logon as a service", but was not in the default domain policy. If you have the rights, check in there. I am not able to reboot the server at this point to test this, but will reply back next week.

Hope this helps.

nworbm

Reputation Points: 10

Solved Threads: 0

Newbie Poster

Offline

2 posts
since Jul 2006

Permalink

Jul 16th, 2006

Re: SQL 2005 won't start after critical update reboot

Aaron, adding the user to the default domain policy "login as service" corrected my issue.

nworbm

Reputation Points: 10

Solved Threads: 0

Newbie Poster

Offline

2 posts
since Jul 2006

Permalink

Jul 19th, 2006

Re: SQL 2005 won't start after critical update reboot

nworbm,

Wow! Glad to hear this is the solution. Now I just have to talk to the right(s) people and get my user added to the policy. Thanks for helping with this mystery.

~ Aaron

abahmer

Reputation Points: 10

Solved Threads: 0

Newbie Poster

Offline

4 posts
since Jun 2006

This thread is more than three months old

No one has posted to this discussion for at least three months. Please let old threads die and do not reply to them unless you feel you have something new and valuable to contribute that absolutely must be added to make the discussion complete. Otherwise, please start a new thread in this forum instead.

Previous Thread in MS SQL Forum Timeline: Hi,Need help on sql select statement structure

Next Thread in MS SQL Forum Timeline: Help Me Please - Restore Problems

DaniWeb Message

Cancel Changes

User Name
Password