Getting SQL Server to start
Chris
I am completely new to SQL Server. I just installed SQL Server on my
desktop machine yesterday. I was able to connect and setup a database.
After than, I ran aspnet_regsql on this database - everything seemed
to be working fine.
Today I cannot get SQL Server to start. I go to SQL Configuration
Manager -> SQL Server 2005 Services -> SQLServer (MSQLServer) and
rightclick Start.
I get an error message saying that the request failed or the service
did not launch in a timely manner. Refer to the error log for details.
I am not sure where to find the error log.
As far as I can tell, I have set everything to be enabled.
I appreciate any help in fixing this problem. Thanks
Chirs
Rick Byham, MSFT
Studio. It's under Management.
Also try starting SQL Server by using the Windows services applet. On the
Start menu click Run. Type services.msc and then click OK. Never change the
user account here, but by starting here, you can sometimes get more errors
to give you a clue what's going on.
--
Rick Byham, MSFT
(Implies no warranty or rights)
"Chris" <cnat...@yahoo.com> wrote in message
news:e775a715-75b9-44a9...@s31g2000yqs.googlegroups.com...
Chris
Thanks for your quick response. I did the following:
I went into the error log and saw that I had the following message:
---------------------------------------------------------------------------------------------------------------------------
2009-11-02 10:54:43.81 Server (c) 2005 Microsoft Corporation.
2009-11-02 10:54:43.81 Server All rights reserved.
2009-11-02 10:54:43.81 Server Server process ID is 3004.
2009-11-02 10:54:43.81 Server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2009-11-02 10:54:43.81 Server This instance of SQL Server last
reported using a process ID of 1328 at 11/2/2009 10:54:36 AM (local)
11/2/2009 4:54:36 PM (UTC). This is an informational message only; no
user action is required.
2009-11-02 10:54:43.81 Server Registry startup parameters:
2009-11-02 10:54:43.81 Server -d C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\master.mdf
2009-11-02 10:54:43.81 Server -e C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2009-11-02 10:54:43.81 Server -l C:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2009-11-02 10:54:43.84 Server SQL Server is starting at normal
priority base (=7). This is an informational message only. No user
action is required.
2009-11-02 10:54:43.84 Server Detected 1 CPUs. This is an
informational message; no user action is required.
2009-11-02 10:54:43.90 Server Set AWE Enabled to 1 in the
configuration parameters to allow use of more memory.
2009-11-02 10:54:44.06 Server Using dynamic lock allocation.
Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per
node. This is an informational message only. No user action is
required.
2009-11-02 10:54:44.07 Server Attempting to initialize Microsoft
Distributed Transaction Coordinator (MS DTC). This is an informational
message only. No user action is required.
2009-11-02 10:54:45.10 Server Attempting to recover in-doubt
distributed transactions involving Microsoft Distributed Transaction
Coordinator (MS DTC). This is an informational message only. No user
action is required.
2009-11-02 10:54:45.10 Server Database Mirroring Transport is
disabled in the endpoint configuration.
2009-11-02 10:54:45.10 spid5s Starting up database 'master'.
2009-11-02 10:54:45.21 spid5s SQL Trace ID 1 was started by login
"sa".
2009-11-02 10:54:45.23 spid5s Starting up database
'mssqlsystemresource'.
2009-11-02 10:54:45.43 spid5s Server name is 'JAMES'. This is an
informational message only. No user action is required.
2009-11-02 10:54:46.00 Server A self-generated certificate was
successfully loaded for encryption.
2009-11-02 10:54:46.01 Server Error: 17182, Severity: 16, State:
1.
2009-11-02 10:54:46.01 Server TDSSNIClient initialization failed
with error 0x7e, status code 0x60.
2009-11-02 10:54:46.01 Server Error: 17182, Severity: 16, State:
1.
2009-11-02 10:54:46.01 Server TDSSNIClient initialization failed
with error 0x7e, status code 0x1.
2009-11-02 10:54:46.01 Server Error: 17826, Severity: 18, State:
3.
2009-11-02 10:54:46.01 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.
2009-11-02 10:54:46.01 Server Error: 17120, Severity: 16, State:
1.
2009-11-02 10:54:46.01 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.
----------------------------------------------------------------------------------------------------------------------------------------
I am not sure what this means, but I appreciate your help in getting
this fixed.
Thanks
Chris
Chris
I was able to get it to work. I had to disable the Via protocol. I am
not sure what it means or why, but I will get to it eventually.
Thanks for your help in getting me started.
Best wishes.
Chris
Tom Cooper
that if you don't have VIA hardware. Check to see if it is enabled, if it
is, disable it. Then stop and restart SQL Server if it is running (or
reboot your server). See if that fixes your problem. To enable or disable
a protocol, run the SQL Server Configuration Manager and then follow the
instructions in
http://msdn.microsoft.com/en-us/library/ms191294%28SQL.90%29.aspx
Tom
"Chris" <cnat...@yahoo.com> wrote in message
news:49efc39e-6f62-4d0e...@l2g2000yqd.googlegroups.com...
Chris
> It's possible you have the VIA network protocol enabled. You don't want
> that if you don't have VIA hardware. Check to see if it is enabled, if it
> is, disable it. Then stop and restart SQL Server if it is running (or
> reboot your server). See if that fixes your problem. To enable or disable
> a protocol, run the SQL Server Configuration Manager and then follow the
> instructions in
>
> http://msdn.microsoft.com/en-us/library/ms191294%28SQL.90%29.aspx
>
> Tom
>
Tom,
Thanks for your help in getting this problem fixed. Best regards
Chris