Cannot restart SQL Server service
in [Server Configuration]
|
From: Kalen Delaney on 28 Dec 2008 17:18 Have you verified that the folder c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ actually exists? -- HTH Kalen Delaney, SQL Server MVP www.InsideSQLServer.com www.SQLTuners.com "goldenthroat via SQLMonster.com" <u48443(a)uwe> wrote in message news:8f5a6a44c69cb(a)uwe... > Thanks for telling me that. I put them back the way they were. Do you > have > any other ideas? Thanks again for your help. > > Jeffrey Williams wrote: >>No - they are correct as is. The -e parameter includes the 'c' drive so >>it >>looks like -ec... >> >>> Thanks for your response. I went to Books Online and found out about >>> the >>> Startup Parameters. Thanks for telling me about them! Here is what >>> they >>[quoted text clipped - 20 lines] >>>>>>> >>>>>>> Please help. > > -- > Message posted via SQLMonster.com > http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200812/1 >
From: goldenthroat via SQLMonster.com on 28 Dec 2008 18:55 Yes. This is the path copied from the Windows Explorer window: C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log. There is no log file in it from today, however. Kalen Delaney wrote: >Have you verified that the folder c:\Program Files\Microsoft SQL >Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ >actually exists? >> Thanks for telling me that. I put them back the way they were. Do you >> have >[quoted text clipped - 11 lines] >>>>>>>> >>>>>>>> Please help. -- Message posted via http://www.sqlmonster.com
From: goldenthroat via SQLMonster.com on 28 Dec 2008 20:39 Thanks, John. That worked. Here is the output in the errorlog.txt file: 2008-12-28 20:34:32.53 Server Microsoft SQL Server 2008 (RTM) - 10.0. 1600.22 (Intel X86) Jul 9 2008 14:43:34 Copyright (c) 1988-2008 Microsoft Corporation Express Edition with Advanced Services on Windows NT 5.1 <X86> (Build 2600: Service Pack 2) 2008-12-28 20:34:32.54 Server (c) 2005 Microsoft Corporation. 2008-12-28 20:34:32.54 Server All rights reserved. 2008-12-28 20:34:32.54 Server Server process ID is 2252. 2008-12-28 20:34:32.54 Server Authentication mode is WINDOWS-ONLY. 2008-12-28 20:34:32.54 Server Logging SQL Server messages in file 'C:\ temp\errorlog.txt'. 2008-12-28 20:34:32.70 Server This instance of SQL Server last reported using a process ID of 1292 at 12/28/2008 6:59:41 PM (local) 12/28/2008 11:59: 41 PM (UTC). This is an informational message only; no user action is required. 2008-12-28 20:34:32.71 Server Registry startup parameters: -d c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\ master.mdf -e c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ ERRORLOG -l c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\ mastlog.ldf 2008-12-28 20:34:32.71 Server Command Line Startup Parameters: -s SQLEXPRESS SQLEXPRESS -e C:\temp\errorlog.txt 2008-12-28 20:34:32.87 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2008-12-28 20:34:32.89 Server Detected 2 CPUs. This is an informational message; no user action is required. 2008-12-28 20:34:34.20 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. 2008-12-28 20:34:35.68 Server Node configuration: node 0: CPU mask: 0x00000003 Active CPU mask: 0x00000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required. 2008-12-28 20:34:36.98 spid7s Starting up database 'master'. 2008-12-28 20:34:37.56 spid7s 9 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required. 2008-12-28 20:34:37.71 spid7s 0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required. 2008-12-28 20:34:37.71 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required. <{39B75A24-0837-4CEC-AFDF-B960027AE07E}>RsFxNso initialized. InstanceId = 00000001 <{50080099-5EC4-4EAF-A2A2-63C3DA97F8EB}>FsAgent is initialized <{09C4480B-DBA4-49B7-956F-68A8B8B2445D}>FsAgent is up and running 2008-12-28 20:34:38.99 spid7s FILESTREAM: effective level = 3, configured level = 3, file system access share name = 'SQLEXPRESS'. 2008-12-28 20:34:39.60 spid7s SQL Trace ID 1 was started by login "sa". 2008-12-28 20:34:39.71 spid7s Starting up database 'mssqlsystemresource'. 2008-12-28 20:34:39.76 spid7s The resource database build version is 10. 00.1600. This is an informational message only. No user action is required. 2008-12-28 20:34:40.23 spid15s Starting up database 'model'. 2008-12-28 20:34:40.25 spid7s Server name is 'ICHIBAN\SQLEXPRESS'. This is an informational message only. No user action is required. 2008-12-28 20:34:40.73 spid15s Clearing tempdb database. 2008-12-28 20:34:42.37 spid15s Starting up database 'tempdb'. 2008-12-28 20:34:43.17 spid18s The Service Broker protocol transport is disabled or not configured. 2008-12-28 20:34:43.17 spid18s The Database Mirroring protocol transport is disabled or not configured. 2008-12-28 20:34:43.26 Server A self-generated certificate was successfully loaded for encryption. 2008-12-28 20:34:43.34 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ]. 2008-12-28 20:34:43.34 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ]. 2008-12-28 20:34:43.34 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required. 2008-12-28 20:34:43.45 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies. 2008-12-28 20:34:43.46 Server SQL Server is now ready for client connections. This is an informational message; no user action is required. 2008-12-28 20:34:43.56 spid18s Service Broker manager has started. 2008-12-28 20:34:44.06 spid24s A new instance of the full-text filter daemon host process has been successfully started. 2008-12-28 20:34:44.35 spid7s Starting up database 'msdb'. 2008-12-28 20:34:44.46 spid7s 1 transactions rolled forward in database 'msdb' (4). This is an informational message only. No user action is required. 2008-12-28 20:34:44.48 spid7s 0 transactions rolled back in database 'msdb' (4). This is an informational message only. No user action is required. 2008-12-28 20:34:44.48 spid7s Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required. 2008-12-28 20:34:44.57 spid7s Recovery is complete. This is an informational message only. No user action is required. 2008-12-28 20:34:46.65 spid51 Starting up database 'ReportServer $SQLEXPRESS'. 2008-12-28 20:34:46.79 spid51 1 transactions rolled forward in database 'ReportServer$SQLEXPRESS' (5). This is an informational message only. No user action is required. 2008-12-28 20:34:46.81 spid51 0 transactions rolled back in database 'ReportServer$SQLEXPRESS' (5). This is an informational message only. No user action is required. 2008-12-28 20:34:46.81 spid51 Recovery is writing a checkpoint in database 'ReportServer$SQLEXPRESS' (5). This is an informational message only. No user action is required. 2008-12-28 20:37:46.09 spid7s SQL Server shutdown due to Ctrl-C or Ctrl- Break signal. This is an informational message only. No user action is required. 2008-12-28 20:37:46.64 spid7s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required. John Bell wrote: >> Thanks for your question and interest in my problem. >> >[quoted text clipped - 24 lines] >>> >>>John > >Hi > >You may want to try starting SQL Server from a command prompt rather than >using the service see http://msdn.microsoft.com/en-us/library/ms180965.aspx >as you will see the startup messages. >On the command line you can also specify the flags as per the previous posts >and change the log file using the -e flag. > >e.g > >Change your directory to > >C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\BINN > >then run: > >SQLSERVR -S "SQLEXPRESS" -eC:\temp\errorlog.txt > >The startup messages will also be in C:\temp\errorlog.txt > >John -- Message posted via http://www.sqlmonster.com
From: John Bell on 29 Dec 2008 05:55 Hi The start up looks ok. I assume you shut the server down? Did you try to connect? What happens if you connect using: SQLCMD -E -S ".\SQLEXPRESS" For the SPN message see http://blogs.msdn.com/sql_protocols/archive/2008/04/02/service-principal-name-spn.aspx http://blogs.msdn.com/sql_protocols/archive/2005/10/12/479871.aspx http://support.microsoft.com/kb/909801/en-us but that should not be an issue. John "goldenthroat via SQLMonster.com" <u48443(a)uwe> wrote in message news:8f5d089d71401(a)uwe... > Thanks, John. That worked. Here is the output in the errorlog.txt file: > > 2008-12-28 20:34:32.53 Server Microsoft SQL Server 2008 (RTM) - 10.0. > 1600.22 (Intel X86) > Jul 9 2008 14:43:34 > Copyright (c) 1988-2008 Microsoft Corporation > Express Edition with Advanced Services on Windows NT 5.1 <X86> (Build > 2600: > Service Pack 2) > > 2008-12-28 20:34:32.54 Server (c) 2005 Microsoft Corporation. > 2008-12-28 20:34:32.54 Server All rights reserved. > 2008-12-28 20:34:32.54 Server Server process ID is 2252. > 2008-12-28 20:34:32.54 Server Authentication mode is WINDOWS-ONLY. > 2008-12-28 20:34:32.54 Server Logging SQL Server messages in file > 'C:\ > temp\errorlog.txt'. > 2008-12-28 20:34:32.70 Server This instance of SQL Server last > reported > using a process ID of 1292 at 12/28/2008 6:59:41 PM (local) 12/28/2008 > 11:59: > 41 PM (UTC). This is an informational message only; no user action is > required. > 2008-12-28 20:34:32.71 Server Registry startup parameters: > -d c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\ > master.mdf > -e c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ > ERRORLOG > -l c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\ > mastlog.ldf > 2008-12-28 20:34:32.71 Server Command Line Startup Parameters: > -s SQLEXPRESS > SQLEXPRESS > -e C:\temp\errorlog.txt > 2008-12-28 20:34:32.87 Server SQL Server is starting at normal > priority > base (=7). This is an informational message only. No user action is > required. > 2008-12-28 20:34:32.89 Server Detected 2 CPUs. This is an > informational > message; no user action is required. > 2008-12-28 20:34:34.20 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. > 2008-12-28 20:34:35.68 Server Node configuration: node 0: CPU mask: > 0x00000003 Active CPU mask: 0x00000003. This message provides a > description > of the NUMA configuration for this computer. This is an informational > message > only. No user action is required. > 2008-12-28 20:34:36.98 spid7s Starting up database 'master'. > 2008-12-28 20:34:37.56 spid7s 9 transactions rolled forward in > database > 'master' (1). This is an informational message only. No user action is > required. > 2008-12-28 20:34:37.71 spid7s 0 transactions rolled back in database > 'master' (1). This is an informational message only. No user action is > required. > 2008-12-28 20:34:37.71 spid7s Recovery is writing a checkpoint in > database 'master' (1). This is an informational message only. No user > action > is required. > <{39B75A24-0837-4CEC-AFDF-B960027AE07E}>RsFxNso initialized. InstanceId = > 00000001 > <{50080099-5EC4-4EAF-A2A2-63C3DA97F8EB}>FsAgent is initialized > <{09C4480B-DBA4-49B7-956F-68A8B8B2445D}>FsAgent is up and running > 2008-12-28 20:34:38.99 spid7s FILESTREAM: effective level = 3, > configured level = 3, file system access share name = 'SQLEXPRESS'. > 2008-12-28 20:34:39.60 spid7s SQL Trace ID 1 was started by login > "sa". > 2008-12-28 20:34:39.71 spid7s Starting up database > 'mssqlsystemresource'. > > 2008-12-28 20:34:39.76 spid7s The resource database build version is > 10. > 00.1600. This is an informational message only. No user action is > required. > 2008-12-28 20:34:40.23 spid15s Starting up database 'model'. > 2008-12-28 20:34:40.25 spid7s Server name is 'ICHIBAN\SQLEXPRESS'. > This > is an informational message only. No user action is required. > 2008-12-28 20:34:40.73 spid15s Clearing tempdb database. > 2008-12-28 20:34:42.37 spid15s Starting up database 'tempdb'. > 2008-12-28 20:34:43.17 spid18s The Service Broker protocol transport > is > disabled or not configured. > 2008-12-28 20:34:43.17 spid18s The Database Mirroring protocol > transport > is disabled or not configured. > 2008-12-28 20:34:43.26 Server A self-generated certificate was > successfully loaded for encryption. > 2008-12-28 20:34:43.34 Server Server local connection provider is > ready > to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ]. > 2008-12-28 20:34:43.34 Server Server local connection provider is > ready > to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ]. > 2008-12-28 20:34:43.34 Server Dedicated administrator connection > support > was not started because it is disabled on this edition of SQL Server. If > you > want to use a dedicated administrator connection, restart SQL Server using > the trace flag 7806. This is an informational message only. No user action > is > required. > 2008-12-28 20:34:43.45 Server The SQL Server Network Interface > library > could not register the Service Principal Name (SPN) for the SQL Server > service. Error: 0x54b, state: 3. Failure to register an SPN may cause > integrated authentication to fall back to NTLM instead of Kerberos. This > is > an informational message. Further action is only required if Kerberos > authentication is required by authentication policies. > 2008-12-28 20:34:43.46 Server SQL Server is now ready for client > connections. This is an informational message; no user action is required. > 2008-12-28 20:34:43.56 spid18s Service Broker manager has started. > 2008-12-28 20:34:44.06 spid24s A new instance of the full-text filter > daemon host process has been successfully started. > 2008-12-28 20:34:44.35 spid7s Starting up database 'msdb'. > 2008-12-28 20:34:44.46 spid7s 1 transactions rolled forward in > database > 'msdb' (4). This is an informational message only. No user action is > required. > > 2008-12-28 20:34:44.48 spid7s 0 transactions rolled back in database > 'msdb' (4). This is an informational message only. No user action is > required. > > 2008-12-28 20:34:44.48 spid7s Recovery is writing a checkpoint in > database 'msdb' (4). This is an informational message only. No user action > is > required. > 2008-12-28 20:34:44.57 spid7s Recovery is complete. This is an > informational message only. No user action is required. > 2008-12-28 20:34:46.65 spid51 Starting up database 'ReportServer > $SQLEXPRESS'. > 2008-12-28 20:34:46.79 spid51 1 transactions rolled forward in > database > 'ReportServer$SQLEXPRESS' (5). This is an informational message only. No > user > action is required. > 2008-12-28 20:34:46.81 spid51 0 transactions rolled back in database > 'ReportServer$SQLEXPRESS' (5). This is an informational message only. No > user > action is required. > 2008-12-28 20:34:46.81 spid51 Recovery is writing a checkpoint in > database 'ReportServer$SQLEXPRESS' (5). This is an informational message > only. > No user action is required. > 2008-12-28 20:37:46.09 spid7s SQL Server shutdown due to Ctrl-C or > Ctrl- > Break signal. This is an informational message only. No user action is > required. > 2008-12-28 20:37:46.64 spid7s SQL Trace was stopped due to server > shutdown. Trace ID = '1'. This is an informational message only; no user > action is required. > > > John Bell wrote: >>> Thanks for your question and interest in my problem. >>> >>[quoted text clipped - 24 lines] >>>> >>>>John >> >>Hi >> >>You may want to try starting SQL Server from a command prompt rather than >>using the service see >>http://msdn.microsoft.com/en-us/library/ms180965.aspx >>as you will see the startup messages. >>On the command line you can also specify the flags as per the previous >>posts >>and change the log file using the -e flag. >> >>e.g >> >>Change your directory to >> >>C:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\BINN >> >>then run: >> >>SQLSERVR -S "SQLEXPRESS" -eC:\temp\errorlog.txt >> >>The startup messages will also be in C:\temp\errorlog.txt >> >>John > > -- > Message posted via http://www.sqlmonster.com >
From: John Bell on 29 Dec 2008 06:04 "John Bell" <jbellnewsposts(a)hotmail.com> wrote in message news:ukqssPaaJHA.5676(a)TK2MSFTNGP03.phx.gbl... > Hi > > The start up looks ok. I assume you shut the server down? Did you try to > connect? > > What happens if you connect using: > > SQLCMD -E -S ".\SQLEXPRESS" > > For the SPN message see > > http://blogs.msdn.com/sql_protocols/archive/2008/04/02/service-principal-name-spn.aspx > http://blogs.msdn.com/sql_protocols/archive/2005/10/12/479871.aspx > http://support.microsoft.com/kb/909801/en-us > > but that should not be an issue. > > John > I forgot to say.. if this worked and you connected, then either rename the current log directory and create a new one, or rename the errorlog files so you don't have to rename/create them. John
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 5 Prev: failed to pause full-text catalog for backup Next: SQL Server 2008 and PowerShell |