Error 1814 when starting SQL Server 2008 R2

If space is OK, perhaps the antivirus locking your mdf/ldf

Looks like some database (probably tempdb) cannot be created. Ensure that SA (SQL authentication) user or your domain user (Windows Authentication) has modify permissions on a folder where databases are stored or SQL installed.

Message states that there might be non-sufficient disk space but it's also for not enough permission for user.

So, check if Windows Authentication on your or DOmain Admin account would help. And check if those accounts have modify permission in NTFS properties of that folder with DBs.

Regards,
Krzysztof

Thanks guys.

- I have disabled our Anti Virus and still have the same problem.
- Disk space is not an issue
- The relevant Windows users have Full Control to the folder where the SQL databases exist. (Also the tempdb directory).

?

Can you try to start service again and look into Event Log, maybe there will be also something more about that than this one entry?

Krzysztof

Following links should be helpful:-
http://social.msdn.microsoft.com/Forums/en/sqlsetupandupgrade/thread/d5af60d4-84e3-4b03-a8cc-ec5ddbdb8c74

Besides the errorId is generally associated with the failure of creation of tempdb database. Check for the space in the disk which holds tempdb files and also check whether the associated disk is present there or not. May be some reference problem.

Guys,

Getting this error message from the ERRORLOG within SQL:

2011-09-26 13:13:22.60 Server      Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
                Apr  2 2010 15:48:46
                Copyright (c) Microsoft Corporation
                Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )

2011-09-26 13:13:22.60 Server      (c) Microsoft Corporation.
2011-09-26 13:13:22.60 Server      All rights reserved.
2011-09-26 13:13:22.60 Server      Server process ID is 3332.
2011-09-26 13:13:22.60 Server      System Manufacturer: 'Dell Inc.', System Model: 'PowerEdge T710'.
2011-09-26 13:13:22.60 Server      Authentication mode is MIXED.
2011-09-26 13:13:22.60 Server      Logging SQL Server messages in file 'E:\SQL\SQL_SYSTEM_DATA\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2011-09-26 13:13:22.60 Server      This instance of SQL Server last reported using a process ID of 3240 at 26/09/2011 12:47:36 (local) 26/09/2011 11:47:36 (UTC). This is an informational message only; no user action is required.
2011-09-26 13:13:22.60 Server      Registry startup parameters:
                 -d E:\SQL\SQL_SYSTEM_DATA\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
                -e E:\SQL\SQL_SYSTEM_DATA\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
                -l E:\SQL\SQL_SYSTEM_DATA\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2011-09-26 13:13:22.60 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2011-09-26 13:13:22.60 Server      Detected 16 CPUs. This is an informational message; no user action is required.
2011-09-26 13:13:22.92 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.
2011-09-26 13:13:22.92 Server      Lock partitioning is enabled.  This is an informational message only. No user action is required.
2011-09-26 13:13:22.94 Server      Node configuration: node 0: CPU mask: 0x000000000000ff00:0 Active CPU mask: 0x000000000000ff00:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2011-09-26 13:13:22.94 Server      Node configuration: node 1: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2011-09-26 13:13:22.97 spid8s      Starting up database 'master'.
2011-09-26 13:13:23.00 spid8s      CHECKDB for database 'master' finished without errors on 2011-09-13 22:26:52.057 (local time). This is an informational message only; no user action is required.
2011-09-26 13:13:23.01 spid8s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2011-09-26 13:13:23.02 spid8s      SQL Trace ID 1 was started by login "sa".
2011-09-26 13:13:23.03 spid8s      Starting up database 'mssqlsystemresource'.
2011-09-26 13:13:23.03 spid8s      The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2011-09-26 13:13:23.15 spid8s      Server name is 'XXXX'. This is an informational message only. No user action is required.
2011-09-26 13:13:23.15 spid12s     Starting up database 'model'.
2011-09-26 13:13:23.19 spid12s     The database 'model' is marked RESTORING and is in a state that does not allow recovery to be run.
2011-09-26 13:13:23.19 spid12s     Error: 927, Severity: 14, State: 2.
2011-09-26 13:13:23.19 spid12s     Database 'model' cannot be opened. It is in the middle of a restore.
2011-09-26 13:13:23.19 spid12s     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.
2011-09-26 13:13:23.19 spid12s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

2011-09-26 13:13:23.19 spid12s     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.
2011-09-26 13:13:23.19 spid12s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

So, as I posted, looks like permissions problem :) SQL cannot create tempdb database
Check permissions to that folder again :)
Krzysztof

Hi Krzysztof,

The NTFS permissions on the 'tempdb' directory are set as FULL CONTROL for the Administrators group.

Thanks.
D

I would like to repeat again: how much space is left for tempdb drive? Is it sufficient? Please make more room.

Its a 900GB volume with approx 500GB of free space.

Thanks.
D

And is it a separate drive? Are there any other database residing on the same drive?

This is the E drive on the server.

There are various databases on the E drive.

Thanks.
D

Thanks ill check

Partially assisted resolution.