SQL Service stops, won't start.

[travisbrown]

So my SQL Server service stops. I try and restart it in the service console and get this message:
"The MSSQLSERVER service on Local Computer started thnd then Stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts service."

Won't start in EM either. Any idea what's going on, or how I can troubleshoot? Was working fine an hour ago, and no config changes or installations on the server. Rebooted a couple times.

Running on Win2k3

 

[travisbrown]

Might have something with being disaccociated with the Admin account? I was trying to reapply SP4 and it stalls on validating user. Possible?

 

[travisbrown]

So in the event viewer I get there four messages when trying to start the service:

Encryption requested but no valid certificate was found. SQL Server terminating.

19015 :
Encryption requested but no valid certificate was found. SQL Server terminating.

Error: 17826, Severity: 18, State: 1
Could not set up Net-Library 'SSNETLIB'.

17120 :
SQL Server could not spawn FRunCM thread.

 

[mrdenny]

Are you using IPSec on your network (you may need to check with your network admin)?

What changes were made to the SQL Server before it stopped working?

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[travisbrown]

Thanks Denny.

Nothing changed that I know of. Obviously something did, but it's nothing obvious.

I'm my own network admin, unfortunately. IPSec isn't active.

I uninstalled and reinstalled SQL and it starts fine now. Problem is, now I can't connect from another machine using EM or ADO connection. Get dreaded "Cannot create an sspi context". I double checked to make sure the SQL Server was in mixed mode. Tried changing back and forth between using a system account and Administrator account too. No luck.

 

[mrdenny]

That error generaly comes up when you have SQL Server running and the password for the account which is running SQL is either changed or disabled.

Check the security logs on the DCs, and see if anything funky is happening with the SQL account.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[travisbrown]

That's odd. I'm logged into a workstation as DC administrator. I try and register the SQL Server using windows auth (same login I use to login to DC/SQL machine). Get the SSPI message, but the security log entry corresponding to the EM registration attempt DC/SQL machine shows a successful audit for NT AUTHORITY\ANONYMOUS LOGON

Successful Network Logon:
User Name:
Domain:
Logon ID: (0x0,0x6E184D)
Logon Type: 3
Logon Process: NtLmSsp
Authentication Package: NTLM
Workstation Name: BURST-01
Logon GUID: -
Caller User Name: -
Caller Domain: -
Caller Logon ID: -
Caller Process ID: -
Transited Services: -
Source Network Address: 192.168.0.110
Source Port: 0

 

[mrdenny]

Do you have only one DC, or more than one? So SQL is installed on the DC? (I'll skip my normal rant on that; for now.)

Do you have any sort of firewall on the server? Anti-Virus firewall, windows firewall, etc? If you log onto the servers console can you log into the SQL Server?

Try removing the workstation from the domain and readding it. It might not be authenticating correctly (I've seen a machine log onto a domain, but not log inot SQL because some little piece of the machine wasn't working correctly).

Do you have another client machine you can try this from (ie. another workstation, laptop, etc)? That will allow us to narrow down the problem to a server problem or a workstation problem and tell us where to direct our efforts.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[travisbrown]

Yeah, I know and agree about SQL and DC on the same machine. It's temporary until I get a new box for the SQL.

No firewall, F-Prot antivirus, but it's been running happily with that for a few years now.

I'll try detaching the machine from the domain, disabling anti-virus, registering from another machine tomorrow and get back to you. Thanks for the help so far.

 

[mrdenny]

no problem.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[travisbrown]

Have no idea why it started working, but a week later withough any system updates or app changes, it connects.

huh.

 

[travisbrown]

And...now I get the SSPI context error again. Argh.

 

[MaffewW]

it lets you connect with sa?

does it let you do a stop/start of the service now and does this fix the SSPI context message (temporarily)

Matt

Brighton, UK

 

[travisbrown]

Can register server on client machine with SA even when unable to using Windows auth.

Intermittently can register using Windows account.

I'm always logged in as domain admin.

 

[travisbrown]

Must be the phases of the moon. No problem registering with windows auth today.

 

[mrdenny]

Typically the SSPI error is because the account that is running the SQL Server is locked, or because the SQL Server can't contact the domain controller.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[travisbrown]

Should the SS be running under the system account or the admin account? I'm guessing it is an account thing. i apparently can log in with sa even when i can't connect with the domain admin account.

How does one verify locked accounts?

 

[mrdenny]

The SQL Server should be running under it's own domain account.

You need to look in Active Directory to see if an account is disabled.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com