SQL Server is not starting

Question

Hi All,

I installed SQL 2008 developer edition on a server. After that I changed the start up parameter. But noe the SQL server is not getting started and giving the following error:

The request failed or the Service did not repond in a timely fashion.


I checked everything...its fine..



Plz suggest sumthing

---

Rahul Soni SQL DBA

Answer 1

Please revert back to your original startup parameters and try to start.
If that doesn't work , Post your startup parameter here .

---

Thanks, Leks

Answer 2

its not working

---

Rahul Soni SQL DBA

Answer 3

Can you check your errorlog? Startup errors will be updated there.

---

Vidhya Sagar. Mark as Answer if it helps!

Answer 4

What does the SQL Server Log show?

---

Phil Brammer | http://www.ssistalk.com | Twitter: http://twitter.com/PhilBrammer

Answer 5

2009-11-04 20:50:27.99 Server      Registry startup parameters:
  -d O:\MSSQL\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf
  -e O:\MSSQL\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG
  -l O:\MSSQL\MSSQL10.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2009-11-04 20:50:28.00 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-11-04 20:50:28.00 Server      Detected 1 CPUs. This is an informational message; no user action is required.
2009-11-04 20:50:28.13 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-04 20:50:28.16 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-11-04 20:50:28.19 spid7s      Starting up database 'master'.
2009-11-04 20:50:28.36 spid7s      Resource governor reconfiguration succeeded.
2009-11-04 20:50:28.37 spid7s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2009-11-04 20:50:28.37 spid7s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2009-11-04 20:50:28.39 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2009-11-04 20:50:28.44 spid7s      SQL Trace ID 1 was started by login "sa".
2009-11-04 20:50:28.45 spid7s      Starting up database 'mssqlsystemresource'.
2009-11-04 20:50:28.46 spid7s      The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
2009-11-04 20:50:28.88 spid7s      Server name is 'GH-VDISTLSV246'. This is an informational message only. No user action is required.
2009-11-04 20:50:28.89 spid10s     Starting up database 'model'.
2009-11-04 20:50:28.90 spid10s     Error: 17204, Severity: 16, State: 1.
2009-11-04 20:50:28.90 spid10s     FCB::Open failed: Could not open file F:\DataFiles\model.mdf for file number 1.  OS error: 5(Access is denied.).
2009-11-04 20:50:28.90 spid10s     Error: 5120, Severity: 16, State: 101.
2009-11-04 20:50:28.90 spid10s     Unable to open the physical file "F:\DataFiles\model.mdf". Operating system error 5: "5(Access is denied.)".
2009-11-04 20:50:28.90 spid10s     Error: 17204, Severity: 16, State: 1.
2009-11-04 20:50:28.90 spid10s     FCB::Open failed: Could not open file J:\LogFiles\modellog.ldf for file number 2.  OS error: 5(Access is denied.).
2009-11-04 20:50:28.90 spid10s     Error: 5120, Severity: 16, State: 101.
2009-11-04 20:50:28.90 spid10s     Unable to open the physical file "J:\LogFiles\modellog.ldf". Operating system error 5: "5(Access is denied.)".
2009-11-04 20:50:28.90 spid10s     Error: 5105, Severity: 16, State: 1.
2009-11-04 20:50:28.90 spid10s     A file activation error occurred. The physical file name 'J:\LogFiles\modellog.ldf' may be incorrect. Diagnose and correct additional errors, and retry the operation.
2009-11-04 20:50:28.90 spid10s     Error: 945, Severity: 14, State: 2.
2009-11-04 20:50:28.90 spid10s     Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
2009-11-04 20:50:28.90 spid10s     Could not create tempdb. You may not have enough disk space available. Free additional disk space by deleting other files on the tempdb drive and then restart SQL Server. Check for additional errors in the event log that may indicate why the tempdb files could not be initialized.
2009-11-04 20:50:28.90 spid10s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.




Log shows the above

---

Rahul Soni SQL DBA

Answer 6

two things; startup is looking for model where the files are located at F:\DataFiles\model.mdf AND J:\LogFiles\modellog.ldf; check that the account used to startup SQL Server has access to these areas (easiest way is to add the account used to the local admins group).

Second thing is it cannot create tempdb; how much space is there on F:\ and J:\ (assuming that these are the drives where the tempdb files are located); if there is plenty of room on the Drives then you may need to resize them: -

<!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman"; mso-fareast-language:EN-US;} @page Section1 {size:612.0pt 792.0pt; margin:72.0pt 90.0pt 72.0pt 90.0pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-paper-source:0;} div.Section1 {page:Section1;} -->

Note the logical file names for the data and log files for TempDB. Open a command prompt; then start SQL Server by typing sqlservr -c –f (from the directory containing sqlservr.exe). Launch Management Studio, then click “New Query” and connect to the instance (do not open any other connection!!). Run the following Script: - ALTER DATABASE tempdb MODIFY FILE    (NAME = 'tempdev', SIZE = 1)      ALTER DATABASE tempdb MODIFY FILE    (NAME = 'templog', SIZE = 1)   Stop SQL Server at the command prompt by typing <CTRL> C and then restart SQL Server.

---

Tony C

Answer 7

If F and J are mapped network drives, SQL Server won't be able to connect to them.  If they are local drives, ensure that the service account has permissions to them.

A windows service (which SQL Server is) cannot access "mapped" network drives, because the drive letter associated to mapped network drives is a user-scope issue.  Since the service account runs as a different user account, and doesn't interact with the desktop, it cannot see mapped network drives.  Instead you will have to use UNC notation: \\server\share\etc...

Phil

---

Phil Brammer | http://www.ssistalk.com | Twitter: http://twitter.com/PhilBrammer

Answer 8

As has already been mentioned, use SQL Server Configuration Manager to verify that the account specified to start the SQL Server service has full rights on the F:\DataFiles drive and folder and J:\LogFiles drive and folder as these rights have either changed or the account used to start SQL has been modified outside of the Configuration Manager.

But the tempdb problem is a red herring. Tempdb is recreated on startup, and like all new dbs will be based on the model db. If SQL can't find model, it can't (re)create tempdb, so fix the model db access issue and the tempdb error messages will also disappear.

---

ajmer dhariwal || eraofdata.com