How Do I Get sqlservr.exe Up & Running? - SQL Server Forums

Home | Weblogs | Forums

Site Sponsored By: SQLDSC - SQL Server Desired State Configuration

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

All Forums

SQL Server 2008 Forums

SQL Server Administration (2008)

How Do I Get sqlservr.exe Up & Running?

Author

Topic

mikebird
Aged Yak Warrior

529 Posts

Posted - 2009-07-30 : 07:54:36

Is there a documented guide to follow to set up

SQL Server Services ?

I've never known this service to fail before. I've tried using just shared memory protocol on a local machine, parameters -m -f
to keep it all simple.

It just fails to kick off with no information of any use at all. It has an instance to run with and I want to import some other databases. SSMS is ready to connect...

mikebird
Aged Yak Warrior

529 Posts

Posted - 2009-07-30 : 10:10:57

The simple error is: Could not start the SQL Server (SQLEXPRESS) service on Local Computer.
Error 1067: The process terminated unexpectedly.

Tried initially as default user NT AUTHORITY\NETWORK SERVICE

blindman
Master Smack Fu Yak Hacker

2365 Posts

Posted - 2009-07-31 : 11:35:14

Are you running on Vista?

________________________________________________
If it is not practically useful, then it is practically useless.
________________________________________________

mikebird
Aged Yak Warrior

529 Posts

Posted - 2009-07-31 : 11:40:02

XP, sp3

jezemine
Master Smack Fu Yak Hacker

2886 Posts

Posted - 2009-07-31 : 12:38:23

check NT eventlog, and SQL Server log file for errors?

mikebird
Aged Yak Warrior

529 Posts

Posted - 2009-07-31 : 13:00:37

Can you tell me where to find these?

jezemine
Master Smack Fu Yak Hacker

2886 Posts

Posted - 2009-08-01 : 02:28:44

NT eventlog: right click on "my computer", choose manage, then choose event viewer.

SQL log: by default somewhere like this: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG, see the ERRORLOG file in your favorite large text file viewer.

mikebird
Aged Yak Warrior

529 Posts

Posted - 2009-08-01 : 16:26:26

This is what I get every time. I've set the falure to retry. No reason given. Nothing in the SQL log yet, as the service has never started. I had the Enterprise evaluation running for a year but this has expired. Perhaps The EXPRESS service is blocked by an Enterprise lock of some kind

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Date: 8/1/2009
Time: 9:08:27 PM
User: N/A
Computer: HOMEUSER
Description:
The SQL Server (SQLEXPRESS) service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

mikebird
Aged Yak Warrior

529 Posts

Posted - 2009-08-01 : 17:11:17

I think I was wrong about non-startup of the service meaning no SQL log kept; maybe there was a chance to do so before it terminated. I checked it as you advised, from a recent date, hoping it was the relevant instance. Can someone make any more sense of what's in there than I can?

It's huge and I can only post a little bit. Is it a standard default message? I've never seen it. Because the service has always worked.

2009-07-28 00:41:45.60 Server Microsoft SQL Server 2008 (SP1) - 10.0.2531.0 (Intel X86)
Mar 29 2009 10:27:29
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition on Windows NT 5.1 <X86> (Build 2600: Service Pack 3)

2009-07-28 00:41:45.60 Server (c) 2005 Microsoft Corporation.
2009-07-28 00:41:45.60 Server All rights reserved.
2009-07-28 00:41:45.61 Server Server process ID is 3836.
2009-07-28 00:41:45.61 Server Authentication mode is WINDOWS-ONLY.
2009-07-28 00:41:45.61 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2009-07-28 00:41:45.61 Server This instance of SQL Server last reported using a process ID of 1812 at 7/28/2009 12:41:44 AM (local) 7/27/2009 11:41:44 PM (UTC). This is an informational message only; no user action is required.
2009-07-28 00:41:45.62 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
2009-07-28 00:41:45.62 Server Command Line Startup Parameters:
-m SqlSetup
-f
-Q
-q SQL_Latin1_General_CP1_CI_AS
-T 4022
-T 4010
-T 3659
-T 3610
2009-07-28 00:41:45.64 Server Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically. After the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
2009-07-28 00:41:45.64 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-07-28 00:41:45.64 Server Detected 1 CPUs. This is an informational message; no user action is required.
2009-07-28 00:41:45.94 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2009-07-28 00:41:45.94 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-07-28 00:41:46.14 Server Node configuration: node 0: CPU mask: 0x00000001 Active CPU mask: 0x00000001. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2009-07-28 00:41:46.17 Server Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action is required.
2009-07-28 00:41:46.20 spid7s Warning ******************
2009-07-28 00:41:46.21 spid7s SQL Server started in single-user mode. This an informational message only. No user action is required.
2009-07-28 00:41:46.23 spid7s Starting up database 'master'.
2009-07-28 00:41:46.34 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2009-07-28 00:41:46.42 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2009-07-28 00:41:46.43 spid7s Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
2009-07-28 00:41:46.43 spid7s Starting up database 'mssqlsystemresource'.
2009-07-28 00:41:46.45 spid7s The resource database build version is 10.00.2531. This is an informational message only. No user action is required.
2009-07-28 00:41:47.07 spid7s Server name is 'HOMEUSER\SQLEXPRESS'. This is an informational message only. No user action is required.
2009-07-28 00:41:47.08 spid8s Starting up database 'model'.
2009-07-28 00:41:48.32 spid7s Informational: No full-text supported languages found.
2009-07-28 00:41:48.35 Server A self-generated certificate was successfully loaded for encryption.
2009-07-28 00:41:48.35 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2009-07-28 00:41:48.36 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.
2009-07-28 00:41:48.37 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.
2009-07-28 00:41:48.38 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2009-07-28 00:41:48.53 spid8s Clearing tempdb database.
2009-07-28 00:41:49.09 spid8s Starting up database 'tempdb'.
2009-07-28 00:41:49.41 spid7s Database 'master' is upgrading script 'msdb_upgrade_discovery.sql' from level 167773760 to level 167774691.
2009-07-28 00:41:49.44 spid7s
2009-07-28 00:41:49.44 spid7s ----------------------------------------------------------------
2009-07-28 00:41:49.44 spid7s msdb_upgrade_discovery starting
2009-07-28 00:41:49.45 spid7s Starting up database 'msdb'.
2009-07-28 00:41:49.92 spid7s MSDB format is: SQL Server 2008
2009-07-28 00:41:50.09 spid7s User 'sa' is changing database script level entry 4 to a value of 2.
2009-07-28 00:41:50.10 spid7s User 'sa' is changing database script level entry 5 to a value of 2.
2009-07-28 00:41:50.10 spid7s User 'sa' is changing database script level entry 6 to a value of 2.
2009-07-28 00:41:50.10 spid7s User 'sa' is changing database script level entry 6 to a value of 0.
2009-07-28 00:41:50.10 spid7s Running SQL Server 2005 SP2 to SQL Server 2008 upgrade script
2009-07-28 00:41:50.10 spid7s ----------------------------------------------------------------
2009-07-28 00:41:50.10 spid7s
2009-07-28 00:41:53.70 spid7s Database 'master' is upgrading script 'sqlagent100_msdb_upgrade.sql' from level 0 to level 2.
2009-07-28 00:41:53.70 spid7s ----------------------------------------
2009-07-28 00:41:53.70 spid7s Starting execution of PREINSTMSDB100.SQL
2009-07-28 00:41:53.70 spid7s ----------------------------------------
2009-07-28 00:41:54.18 spid7s Setting database option COMPATIBILITY_LEVEL to 100 for database msdb.
2009-07-28 00:41:54.46 spid7s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2009-07-28 00:41:54.46 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2009-07-28 00:42:00.91 spid7s Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2009-07-28 00:42:00.95 spid7s Using 'xpstar.dll' version '2007.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2009-07-28 00:42:01.00 spid7s DBCC TRACEOFF 1717, server process ID (SPID) 7. This is an informational message only; no user action is required.
2009-07-28 00:42:01.00 spid7s DBCC execution completed. If DBCC printed error messages, contact your system administrator.
2009-07-28 00:42:01.03 spid7s
2009-07-28 00:42:01.03 spid7s Creating table temp_sysjobschedules
2009-07-28 00:42:01.75 spid7s
2009-07-28 00:42:01.75 spid7s Alter table sysdownloadlist...
2009-07-28 00:42:01.76 spid7s
2009-07-28 00:42:01.76 spid7s Alter table sysjobhistory...
2009-07-28 00:42:01.84 spid7s
2009-07-28 00:42:01.84 spid7s Alter table systargetservers...
2009-07-28 00:42:02.62 spid7s Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install.
2009-07-28 00:42:02.62 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2009-07-28 00:42:02.72 spid7s DMF pre-upgrade steps...
2009-07-28 00:42:02.81 spid7s DC pre-upgrade steps...
2009-07-28 00:42:03.23 spid7s Deleting cached auto-generated T-SQL Data Collection packages from msdb...
2009-07-28 00:42:03.24 spid7s End of DC pre-upgrade steps.
2009-07-28 00:42:03.24 spid7s
2009-07-28 00:42:03.24 spid7s ----------------------------------------
2009-07-28 00:42:03.24 spid7s Execution of PREINSTMSDB100.SQL complete
2009-07-28 00:42:03.24 spid7s ----------------------------------------
2009-07-28 00:42:03.24 spid7s ----------------------------------
2009-07-28 00:42:03.24 spid7s Starting execution of INSTMSDB.SQL
2009-07-28 00:42:03.24 spid7s ----------------------------------
2009-07-28 00:42:03.52 spid7s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2009-07-28 00:42:03.52 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS'.
2009-07-28 00:42:03.84 spid7s Checking the size of MSDB...
2009-07-28 00:42:04.69 spid7s
2009-07-28 00:42:04.69 spid7s Setting database option TRUSTWORTHY to ON for database msdb.
2009-07-28 00:42:04.71 spid7s Setting database option RECOVERY to SIMPLE for database msdb.

This is about 10% of the log

Final line of the log is this:

2009-07-28 00:43:11.99 spid7s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2009-08-02 : 03:23:37

Why are you using the -m -f switches? That starts SQL in minimal config, single user mode. That combination of switches is for fixing problems with the system databases and will only allow a single connection.

Remove the switches and try to start SQL from the services app. Make sure that the account that you're using has the correct password.

--
Gail Shaw
SQL Server MVP

mikebird
Aged Yak Warrior

529 Posts

Posted - 2009-08-02 : 04:19:54

When looking at the item in Services, the parameters field is completely bare. Starting it that way gives the plain termination immediately. The -m -f was some advice I found in MSDN.

The SQL Server Config Manager is unexpectedly completely different from the Services window. The startup parameters here are:

-dc:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\master.mdf;-ec:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\Log\ERRORLOG;-lc:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS\MSSQL\DATA\mastlog.ldf

mikebird
Aged Yak Warrior

529 Posts

Posted - 2009-08-02 : 05:32:27

The one service which seems to be running OK is SQL Server Browser, with the lovely green play icon next to it in Config Manager. Trying to apply the same login setting (blank password) should be key to this. When making any changes to the Services window, it's this where the problems are - no changes are stored - this is why the parameters field is blank, while I've set these before. When you OK changes in a window it's hard to realise they're ignored. Config Manager shows that I cannot make the changes - setting the login gives 'invalid parameter' whatever I set - a found existing user or a jumble of characters or blank password, anything in there at all. Maybe I'm not so stupid as it seems. I think these tiny config windows are seriously corrupted somehow?

mikebird
Aged Yak Warrior

529 Posts

Posted - 2009-08-02 : 13:24:58

I think this mess may have been caused due to a Web Platform Installer. I used it because I couldn't find a SSMS 2008 to install anywhere else. My experience says stay clear of this platform. The instance it set up has not been usable by the Database Engine service, as above, neither removable now! By using the downloadable 2008 Express installation with tools (which I did try before and didn't work), the fresh instance is now in action and let me attach the old crumbly archives I wanted back, too.

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources