Cannot login to SSMS suddenly something do with missing tempdb file
Hi EE,
Can't connect to a SQL server instance, network related error error 2.
I have tried all steps in the following post:
https://dba.stackexchange.com/questions/62165/i-cant-connect-to-my-servers-sql-database-via-an-ip-address
Below is the error messages in the errorlog:
2018-04-26 11:22:30.77 Server SQL Server detected 1 sockets with 4 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2018-04-26 11:22:30.77 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2018-04-26 11:22:30.77 Server Detected 32767 MB of RAM. This is an informational message; no user action is required.
2018-04-26 11:22:30.77 Server Using conventional memory in the memory manager.
2018-04-26 11:22:30.88 Server Default collation: Latin1_General_CI_AS (us_english 1033)
2018-04-26 11:22:30.91 Server Buffer pool extension is already disabled. No action is necessary.
2018-04-26 11:22:30.93 Server InitializeExternalUserGrou
2018-04-26 11:22:30.93 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2018-04-26 11:22:30.94 Server The maximum number of dedicated administrator connections for this instance is '1'
2018-04-26 11:22:30.94 Server This instance of SQL Server last reported using a process ID of 5888 at 26/04/2018 11:19:51 AM (local) 26/04/2018 1:19:51 AM (UTC). This is an informational message only; no user action is required.
2018-04-26 11:22:30.94 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2018-04-26 11:22:30.97 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.
2018-04-26 11:22:30.97 Server Database Instant File Initialization: disabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2018-04-26 11:22:31.00 Server Query Store settings initialized with enabled = 1,
2018-04-26 11:22:31.01 spid5s Starting up database 'master'.
2018-04-26 11:22:31.01 Server In-Memory OLTP initialized on lowend machine.
2018-04-26 11:22:31.04 Server CLR version v4.0.30319 loaded.
2018-04-26 11:22:31.05 spid5s 16 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2018-04-26 11:22:31.06 spid5s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2018-04-26 11:22:31.11 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\F
2018-04-26 11:22:31.13 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2018-04-26 11:22:31.14 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2018-04-26 11:22:31.17 spid5s SQL Trace ID 1 was started by login "sa".
2018-04-26 11:22:31.18 spid5s Server name is 'process-sql'. This is an informational message only. No user action is required.
2018-04-26 11:22:31.19 spid15s Starting up database 'msdb'.
2018-04-26 11:22:31.19 spid14s Starting up database 'Aurion'.
2018-04-26 11:22:31.19 spid6s Starting up database 'mssqlsystemresource'.
2018-04-26 11:22:31.20 spid6s The resource database build version is 13.00.4451. This is an informational message only. No user action is required.
2018-04-26 11:22:31.26 spid6s Starting up database 'model'.
2018-04-26 11:22:31.33 spid6s Polybase feature disabled.
2018-04-26 11:22:31.33 spid6s Clearing tempdb database.
2018-04-26 11:22:31.33 spid6s Error: 5123, Severity: 16, State: 1.
2018-04-26 11:22:31.33 spid6s CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file 'T:\tempdev.mdf'.
2018-04-26 11:22:31.34 spid6s Error: 17204, Severity: 16, State: 1.
2018-04-26 11:22:31.34 spid6s FCB::Open failed: Could not open file T:\tempdev.mdf for file number 1. OS error: 2(The system cannot find the file specified.).
2018-04-26 11:22:31.34 spid6s Error: 5120, Severity: 16, State: 101.
2018-04-26 11:22:31.34 spid6s Unable to open the physical file "T:\tempdev.mdf". Operating system error 2: "2(The system cannot find the file specified.)".
2018-04-26 11:22:31.34 spid6s Error: 1802, Severity: 16, State: 4.
2018-04-26 11:22:31.34 spid6s CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
2018-04-26 11:22:31.34 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.
2018-04-26 11:22:31.34 spid6s SQL Server shutdown has been initiated
2018-04-26 11:22:31.34 spid6s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2018-04-26 11:22:31.39 spid10s A self-generated certificate was successfully loaded for encryption.
2018-04-26 11:22:31.39 spid10s Server is listening on [ 'any' <ipv6> 1433].
2018-04-26 11:22:31.39 spid10s Server is listening on [ 'any' <ipv4> 1433].
2018-04-26 11:22:31.39 spid10s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSER
2018-04-26 11:22:31.40 spid10s Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2018-04-26 11:22:31.40 Server Server is listening on [ ::1 <ipv6> 1434].
2018-04-26 11:22:31.40 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2018-04-26 11:22:31.40 Server Dedicated admin connection support was established for listening locally on port 1434.
Checked the drive where the tempdb are meant to be stored their is 97GB free there.
Any assistance is welcome.
Thank you
Can't connect to a SQL server instance, network related error error 2.
I have tried all steps in the following post:
https://dba.stackexchange.com/questions/62165/i-cant-connect-to-my-servers-sql-database-via-an-ip-address
Below is the error messages in the errorlog:
2018-04-26 11:22:30.77 Server SQL Server detected 1 sockets with 4 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2018-04-26 11:22:30.77 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2018-04-26 11:22:30.77 Server Detected 32767 MB of RAM. This is an informational message; no user action is required.
2018-04-26 11:22:30.77 Server Using conventional memory in the memory manager.
2018-04-26 11:22:30.88 Server Default collation: Latin1_General_CI_AS (us_english 1033)
2018-04-26 11:22:30.91 Server Buffer pool extension is already disabled. No action is necessary.
2018-04-26 11:22:30.93 Server InitializeExternalUserGrou
2018-04-26 11:22:30.93 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2018-04-26 11:22:30.94 Server The maximum number of dedicated administrator connections for this instance is '1'
2018-04-26 11:22:30.94 Server This instance of SQL Server last reported using a process ID of 5888 at 26/04/2018 11:19:51 AM (local) 26/04/2018 1:19:51 AM (UTC). This is an informational message only; no user action is required.
2018-04-26 11:22:30.94 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2018-04-26 11:22:30.97 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.
2018-04-26 11:22:30.97 Server Database Instant File Initialization: disabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2018-04-26 11:22:31.00 Server Query Store settings initialized with enabled = 1,
2018-04-26 11:22:31.01 spid5s Starting up database 'master'.
2018-04-26 11:22:31.01 Server In-Memory OLTP initialized on lowend machine.
2018-04-26 11:22:31.04 Server CLR version v4.0.30319 loaded.
2018-04-26 11:22:31.05 spid5s 16 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2018-04-26 11:22:31.06 spid5s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2018-04-26 11:22:31.11 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\F
2018-04-26 11:22:31.13 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2018-04-26 11:22:31.14 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2018-04-26 11:22:31.17 spid5s SQL Trace ID 1 was started by login "sa".
2018-04-26 11:22:31.18 spid5s Server name is 'process-sql'. This is an informational message only. No user action is required.
2018-04-26 11:22:31.19 spid15s Starting up database 'msdb'.
2018-04-26 11:22:31.19 spid14s Starting up database 'Aurion'.
2018-04-26 11:22:31.19 spid6s Starting up database 'mssqlsystemresource'.
2018-04-26 11:22:31.20 spid6s The resource database build version is 13.00.4451. This is an informational message only. No user action is required.
2018-04-26 11:22:31.26 spid6s Starting up database 'model'.
2018-04-26 11:22:31.33 spid6s Polybase feature disabled.
2018-04-26 11:22:31.33 spid6s Clearing tempdb database.
2018-04-26 11:22:31.33 spid6s Error: 5123, Severity: 16, State: 1.
2018-04-26 11:22:31.33 spid6s CREATE FILE encountered operating system error 5(Access is denied.) while attempting to open or create the physical file 'T:\tempdev.mdf'.
2018-04-26 11:22:31.34 spid6s Error: 17204, Severity: 16, State: 1.
2018-04-26 11:22:31.34 spid6s FCB::Open failed: Could not open file T:\tempdev.mdf for file number 1. OS error: 2(The system cannot find the file specified.).
2018-04-26 11:22:31.34 spid6s Error: 5120, Severity: 16, State: 101.
2018-04-26 11:22:31.34 spid6s Unable to open the physical file "T:\tempdev.mdf". Operating system error 2: "2(The system cannot find the file specified.)".
2018-04-26 11:22:31.34 spid6s Error: 1802, Severity: 16, State: 4.
2018-04-26 11:22:31.34 spid6s CREATE DATABASE failed. Some file names listed could not be created. Check related errors.
2018-04-26 11:22:31.34 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.
2018-04-26 11:22:31.34 spid6s SQL Server shutdown has been initiated
2018-04-26 11:22:31.34 spid6s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2018-04-26 11:22:31.39 spid10s A self-generated certificate was successfully loaded for encryption.
2018-04-26 11:22:31.39 spid10s Server is listening on [ 'any' <ipv6> 1433].
2018-04-26 11:22:31.39 spid10s Server is listening on [ 'any' <ipv4> 1433].
2018-04-26 11:22:31.39 spid10s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSER
2018-04-26 11:22:31.40 spid10s Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2018-04-26 11:22:31.40 Server Server is listening on [ ::1 <ipv6> 1434].
2018-04-26 11:22:31.40 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2018-04-26 11:22:31.40 Server Dedicated admin connection support was established for listening locally on port 1434.
Checked the drive where the tempdb are meant to be stored their is 97GB free there.
Any assistance is welcome.
Thank you
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thanks..
ASKER