Hello, SQL Server doesn't start after move the tempdb to a different drive.

Here is the Error Log:

2015-08-03 14:13:17.97 spid6s      Starting up database 'model'.
2015-08-03 14:13:18.06 spid6s      Clearing tempdb database.
2015-08-03 14:13:18.08 spid6s      Error: 5123, Severity: 16, State: 1.
2015-08-03 14:13:18.08 spid6s      CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file 'T:\tempdb.mdf'.
2015-08-03 14:13:18.11 spid6s      Error: 17204, Severity: 16, State: 1.
2015-08-03 14:13:18.11 spid6s      FCB::Open failed: Could not open file T:\tempdb.mdf for file number 1.  OS error: 5(Access is denied.).
2015-08-03 14:13:18.11 spid6s      Error: 5120, Severity: 16, State: 101.
2015-08-03 14:13:18.11 spid6s      Unable to open the physical file "T:\tempdb.mdf". Operating system error 5: "5(Access is denied.)".
2015-08-03 14:13:18.11 spid6s      Error: 1802, Severity: 16, State: 4.
2015-08-03 14:13:18.11 spid6s      CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
2015-08-03 14:13:18.11 spid6s      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.
2015-08-03 14:13:18.11 spid6s      SQL Server shutdown has been initiated
2015-08-03 14:13:18.11 spid6s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2015-08-03 14:13:18.39 Logon       Error: 18451, Severity: 14, State: 1.
2015-08-03 14:13:18.39 Logon       Login failed for user 'domain\user'. Only administrators may connect at this time. [CLIENT: 00.00.00.00]
2015-08-03 14:13:19.15 spid6s      Error: 25725, Severity: 16, State: 1.
2015-08-03 14:13:19.15 spid6s      An error occurred while trying to flush all running Extended Event sessions.  Some events may be lost.
2015-08-03 14:13:19.16 Logon       Error: 18456, Severity: 14, State: 38.
2015-08-03 14:13:19.16 Logon       Login failed for user 'domain\User2T'. Reason: Failed to open the explicitly specified database 'DatabaseName'. [CLIENT: 00.00.00.00]
2015-08-03 14:13:19.16 Logon       Error: 18456, Severity: 14, State: 38.
2015-08-03 14:13:19.16 Logon       Login failed for user 'domain\user'. Reason: Failed to open the explicitly specified database 'DatabaseName'. [CLIENT: 00.00.00.00]
2015-08-03 14:13:19.16 Logon       Error: 18456, Severity: 14, State: 38.
2015-08-03 14:13:19.16 Logon       Login failed for user 'domain\user'. Reason: Failed to open the explicitly specified database 'DatabaseName'. [CLIENT: 00.00.00.00]
2015-08-03 14:13:19.16 Logon       Error: 18456, Severity: 14, State: 38.
2015-08-03 14:13:19.16 Logon       Login failed for user 'domain\User3'. Reason: Failed to open the explicitly specified database 'DatabaseName'. [CLIENT: 00.00.00.00]
2015-08-03 14:13:19.16 spid10s     The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ MSSQLS/server.es.wcorp.xxx.com ] for the SQL Server service. Error: 0x2af9, state: 61. Administrator should deregister this SPN manually to avoid client authentication errors.
2015-08-03 14:13:19.16 Logon       Error: 18456, Severity: 14, State: 38.
2015-08-03 14:13:19.16 Logon       Login failed for user 'domain\User3'. Reason: Failed to open the explicitly specified database 'DatabaseName'. [CLIENT: 00.00.00.00]
2015-08-03 14:13:19.16 spid10s     The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [ MSSQLS/server.es.wcorp.xxx.com:1433 ] for the SQL Server service. Error: 0x2af9, state: 61. Administrator should deregister this SPN manually to avoid client authentication errors.
Cannot close event log because there are still event handle users active.

Is there enough space on T: drive?

The issue could be because you are attempting to create a file on the Root Directory T:\ and the domain Administrators and/or the Operating System do not allow this.  Is the account that is starting the Database Engine a member of the Server's local Administrat

What kind of drive is T:?

Does the SQL Server service has sufficient NTFS permissions on it? Or is the drive not available, when your SQL Server service starts?

• Proposed as answer by Alberto MorilloMVP, Moderator Monday, August 03, 2015 1:21 PM
• Marked as answer by Jeff Papiez - MSFTMicrosoft employee, Moderator Monday, August 03, 2015 7:10 PM

Check your permissions on T drive. Also error states there are not enough room  to create TEMPDB.

Thank you!! yep the problem is solved

The sql service account hasn't got acces to T Drive .. :(

I restarted the services with a different account and it worked fine. Then, I moved back the temp db to the original drive and update the service account to the original one

Thanks a lot!!

Hello, SQL Server doesn't start after move the tempdb to a different drive.

Here is the Error Log:

2015-08-03 14:13:17.97 spid6s      Starting up database 'model'.
2015-08-03 14:13:18.06 spid6s      Clearing tempdb database.
2015-08-03 14:13:18.08 spid6s      Error: 5123, Severity: 16, State: 1.
2015-08-03 14:13:18.08 spid6s      CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file 'T:\tempdb.mdf'.
2015-08-03 14:13:18.11 spid6s      Error: 17204, Severity: 16, State: 1.
2015-08-03 14:13:18.11 spid6s      FCB::Open failed: Could not open file T:\tempdb.mdf for file number 1.  OS error: 5(Access is denied.).
2015-08-03 14:13:18.11 spid6s      Error: 5120, Severity: 16, State: 101.
2015-08-03 14:13:18.11 spid6s      Unable to open the physical file "T:\tempdb.mdf". Operating system error 5: "5(Access is denied.)".
2015-08-03 14:13:18.11 spid6s      Error: 1802, Severity: 16, State: 4.
2015-08-03 14:13:18.11 spid6s      CREATE DATABASE failed. Some file names listed could not be created. Check related errors..

A very important point missed here, yes we can clearly see that the message is access denied but we must also note that OP is trying to create tempdb files on root of directly in that case SQl Server might not be able to set ACL permissions properly on root of drive and thus failing.

Creating any files or dumping any files on root of a drive is very bad