Please start any new threads on our new site at http://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 SQL Service won't start
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Clothahump
Starting Member

USA
18 Posts

Posted - 08/03/2011 :  16:36:17  Show Profile  Reply with Quote
Server has been running smoothly. No updates have been applied. Suddenly, it hung up solidly and I rebooted it. Now the SQL Server service will not start. My error log shows everything chugging along until we get here:

2011-08-03 15:03:14.19 spid11s Starting up database 'model'.
2011-08-03 15:03:14.20 Server Error: 17182, Severity: 16, State: 1.
2011-08-03 15:03:14.20 Server TDSSNIClient initialization failed with error 0x2, status code 0x38.
2011-08-03 15:03:14.20 Server Error: 17182, Severity: 16, State: 1.
2011-08-03 15:03:14.20 Server TDSSNIClient initialization failed with error 0x2, status code 0x1.
2011-08-03 15:03:14.20 Server Error: 17826, Severity: 18, State: 3.
2011-08-03 15:03:14.20 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2011-08-03 15:03:14.20 Server Error: 17120, Severity: 16, State: 1.
2011-08-03 15:03:14.20 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

The TDSSNIClient error indicates that there is a problem with an SSL certificate, but we aren't encrypting anything.

Any suggestions?


jeffw8713
Aged Yak Warrior

USA
819 Posts

Posted - 08/03/2011 :  19:49:12  Show Profile  Reply with Quote
Check out this blog - http://blogs.msdn.com/b/sql_protocols/archive/2006/04/28/585835.aspx

They show that this is probably due to the ForceEncryption setting. Check that out, as well as make sure the VIA protocol is disabled.

Jeff
Go to Top of Page

Clothahump
Starting Member

USA
18 Posts

Posted - 08/04/2011 :  17:00:10  Show Profile  Reply with Quote
I found the solution:

1. added our domain login account for the SQL service to the local group SQLServer2005MSSQLUser$HSPCSVR03$MSSQLSERVER
2. added the domain login account for the Agent service to SQLServer2005SQLAgentUser$HSPCSVR03$MSSQLSERVER
3. added both accounts to the local computer Administrators group.
4. deleted C:\Documents and Settings\<user>\Application Data\Microsoft\Microsoft SQL Server\90\Tools\Shell\mru.dat.
Go to Top of Page

jeffw8713
Aged Yak Warrior

USA
819 Posts

Posted - 08/05/2011 :  23:43:18  Show Profile  Reply with Quote
Item 3 should not be necessary - in fact, it is not best practice to add the service account to the local administrators group. I would remove it from that group and see if everything starts back up again. If not, then you need more work to figure out the permission issues.

Item 4 doesn't make any sense - that wouldn't have any effect on whether or not SQL Server starts. That is strictly a client tool setting.

Jeff
Go to Top of Page
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.03 seconds. Powered By: Snitz Forums 2000