January 4, 2007 at 1:03 pm
i had SQL 2005 working fine so far but today i was trying to connect to it i found that MSSQLSERVER service is not running i tried toi run it through configuration manager and manually too but didnt work and gives me the message" the sql server(MSSQLSERVER) service started and stopped. some services automatically stop when they have no work to do "
this is wat i got and i have no idea how to fix it.
any help would be appriciated.
January 4, 2007 at 1:40 pm
I don't think that the case with SQL SERVER.
Check SQL error log and event veiwer (application log and system log) for any errors related to sql server.
MohammedU
Microsoft SQL Server MVP
January 5, 2007 at 8:51 am
Try to start SQL Server from control panel/services. If you were using a domain account for your sql services it could have lost some privileges. I’ve seen this error when there was a problem with the domain account under which SQL server was running.
January 7, 2007 at 12:01 am
yea, one way this can happen is if you are running the service under a certain domain acct, but are using the wrong password.
---------------------------------------
elsasoft.org
January 9, 2007 at 10:40 am
the Service was running under local account .when i start it from the window's service its say "service cannot be started on local computer " and when i try to start it form Configuration manager it still doesnot work and logs the error , its says now
"Error: 17113, Severity: 16, State: 1.
Error 3(The system cannot find the path specified.) occurred while opening file ' C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf' to obtain configuration information at startup. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary."
i dont know how to setup the start up options ?
January 9, 2007 at 10:46 am
they are the cmd line args you pass to sqlservr.exe. they would be defined in the properties page for the sql service in Service Control Manager.
see:
http://msdn2.microsoft.com/en-us/library/ms190737.aspx
---------------------------------------
elsasoft.org
January 9, 2007 at 10:55 am
i checked all those option they are reffering to right files in the right directories.
January 9, 2007 at 10:57 am
still if i try to reset these options through command line i get the same error
January 9, 2007 at 11:03 am
this is wat i get when i try to reset startup options
2001-01-09 00:55:14.70 Server Authentication mode is MIXED.
2001-01-09 00:55:14.71 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Int
el X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2001-01-09 00:55:14.71 Server (c) 2005 Microsoft Corporation.
2001-01-09 00:55:14.71 Server All rights reserved.
2001-01-09 00:55:14.71 Server Server process ID is 18292.
2001-01-09 00:55:14.71 Server Logging SQL Server messages in file 'C:\Progr
am Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2001-01-09 00:55:14.73 Server This instance of SQL Server last reported usi
ng a process ID of 17076 at 1/9/2001 12:53:47 AM (local) 1/9/2001 5:53:47 AM (UT
C). This is an informational message only; no user action is required.
2001-01-09 00:55:14.73 Server Registry startup parameters:
2001-01-09 00:55:14.73 Server -d C:\Program Files\Microsoft SQL Serv
er\MSSQL.1\MSSQL\DATA\master.mdf
2001-01-09 00:55:14.73 Server -e C:\Program Files\Microsoft SQL Serve
r\MSSQL.1\MSSQL\LOG\ERRORLOG
2001-01-09 00:55:14.73 Server -l C:\Program Files\Microsoft SQL Serve
r\MSSQL.1\MSSQL\DATA\mastlog.ldf
2001-01-09 00:55:14.73 Server Command Line Startup Parameters:
2001-01-09 00:55:14.73 Server -d C:\Program
2001-01-09 00:55:14.73 Server C:\Program
2001-01-09 00:55:14.75 Server Files\Microsoft
2001-01-09 00:55:14.75 Server SQL
2001-01-09 00:55:14.75 Server Server\MSSQL.1\MSSQL\DATA\master.mdf;-e
C:\Program
2001-01-09 00:55:14.75 Server Files\Microsoft
2001-01-09 00:55:14.75 Server SQL
2001-01-09 00:55:14.75 Server Server\MSSQL.1\MSSQL\LOG\ERRORLOG;-lC:
Program
2001-01-09 00:55:14.78 Server Files\Microsoft
2001-01-09 00:55:14.78 Server SQL
2001-01-09 00:55:14.78 Server Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2001-01-09 00:55:14.78 Server Error: 17113, Severity: 16, State: 1.
2001-01-09 00:55:14.78 Server Error 2(The system cannot find the file speci
fied.) occurred while opening file 'C:\Program' to obtain configuration informat
ion at startup. An invalid startup option might have caused the error. Verify yo
ur startup options, and correct or remove them if necessary.
January 9, 2007 at 12:00 pm
doesn't this give you a hint?
Error 2(The system cannot find the file specified.) occurred while opening file 'C:\Program' to obtain configuration information at startup. An invalid startup option might have caused the error. Verify your startup options, and correct or remove them if necessary.
You need to put the path to master.mdf (and all other args that have spaces in the values, like the path to the log file) in quotes.
also you need to separate each cmd line arg from the next one by a space.
---------------------------------------
elsasoft.org
January 9, 2007 at 12:15 pm
i did put that path in quotes but still getting the same error and also this is the same path that appears in the properties of the MSSQLSERVER service when i go through the sql server configuration manager.
January 9, 2007 at 12:28 pm
Based on the following thread disabling VIA protocol resolved...
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=108800&SiteID=1
Did you check your startup parameter in configuration manager?
MohammedU
Microsoft SQL Server MVP
January 9, 2007 at 12:30 pm
i guess the problem is with some where TCP/IP setting coz now i got the following as error
2001-01-09 02:18:51.51 Server Error: 26023, Severity: 16, State: 1.
2001-01-09 02:18:51.51 Server Server TCP provider failed to listen on [ 'an
y' <ipv4> 1433]. Tcp port is already in use.
2001-01-09 02:18:51.53 Server Error: 17182, Severity: 16, State: 1.
2001-01-09 02:18:51.53 Server TDSSNIClient initialization failed with error
0x2740, status code 0xa.
2001-01-09 02:18:51.53 Server Error: 17182, Severity: 16, State: 1.
2001-01-09 02:18:51.53 Server TDSSNIClient initialization failed with error
0x2740, status code 0x1.
2001-01-09 02:18:51.54 Server Error: 17826, Severity: 18, State: 3.
2001-01-09 02:18:51.54 Server Could not start the network library because o
f an internal error in the network library. To determine the cause, review the e
rrors immediately preceding this one in the error log.
2001-01-09 02:18:51.54 Server Error: 17120, Severity: 16, State: 1.
2001-01-09 02:18:51.54 Server SQL Server could not spawn FRunCM thread. Che
ck the SQL Server error log and the Windows event logs for information about pos
sible related problems.
January 9, 2007 at 12:39 pm
Try changing your PORT number from 1433 to 1434/1435...in configuration manager..
MohammedU
Microsoft SQL Server MVP
January 9, 2007 at 12:53 pm
thanks
but i can connect using sql server management studio but the service is still not running ,SQL server is runing through cmd line
Viewing 15 posts - 1 through 15 (of 24 total)
You must be logged in to reply to this topic. Login to reply