Windows could not start the SQL Server 2019

Question

Error message: "The request failed or the service did not respond in a timely fashion. Consult the event log or other applicable error logs for details" error when starting SQL Server instance

Error log file message: 2023-12-30 12:31:39.82 Server Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64) Sep 24 2019 13:48:23 Copyright (C) 2019 Microsoft Corporation Enterprise Edition (64-bit) on Windows 10 Pro 10.0 <X64> (Build 19045: )

2023-12-30 12:31:39.82 Server UTC adjustment: 5:00 2023-12-30 12:31:39.82 Server (c) Microsoft Corporation. 2023-12-30 12:31:39.82 Server All rights reserved. 2023-12-30 12:31:39.83 Server Server process ID is 16472. 2023-12-30 12:31:39.83 Server System Manufacturer: 'Dell Inc.', System Model: 'OptiPlex 990'. 2023-12-30 12:31:39.83 Server Authentication mode is MIXED. 2023-12-30 12:31:39.83 Server Logging SQL Server messages in file 'D:\MSSQL2019\MSSQL15.MSSQLSERVER\MSSQL\Log\ERRORLOG'. 2023-12-30 12:31:39.83 Server The service account is 'WORKGROUP\SAEED-PC$'. This is an informational message; no user action is required. 2023-12-30 12:31:39.83 Server Registry startup parameters: -d D:\MSSQL2019\MSSQL15.MSSQLSERVER\MSSQL\DATA\master.mdf -e D:\MSSQL2019\MSSQL15.MSSQLSERVER\MSSQL\Log\ERRORLOG -l D:\MSSQL2019\MSSQL15.MSSQLSERVER\MSSQL\DATA\mastlog.ldf 2023-12-30 12:31:39.83 Server Command Line Startup Parameters: -s "MSSQLSERVER" 2023-12-30 12:31:39.83 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. 2023-12-30 12:31:39.83 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2023-12-30 12:31:39.83 Server Detected 14293 MB of RAM. This is an informational message; no user action is required. 2023-12-30 12:31:39.83 Server Using locked pages in the memory manager. 2023-12-30 12:31:39.83 Server Page exclusion bitmap is enabled. 2023-12-30 12:31:39.85 Server Buffer Pool: Allocating 4194304 bytes for 2286881 hashPages. 2023-12-30 12:31:39.88 Server Default collation: Arabic_CI_AS (us_english 1033) 2023-12-30 12:31:39.91 Server Buffer pool extension is already disabled. No action is necessary. 2023-12-30 12:31:39.95 Server Query Store settings initialized with enabled = 1, 2023-12-30 12:31:39.95 Server The maximum number of dedicated administrator connections for this instance is '1' 2023-12-30 12:31:39.95 Server This instance of SQL Server last reported using a process ID of 12160 at 12/30/2023 12:31:33 PM (local) 12/30/2023 7:31:33 AM (UTC). This is an informational message only; no user action is required. 2023-12-30 12:31:39.95 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. 2023-12-30 12:31:39.95 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. 2023-12-30 12:31:39.96 Server In-Memory OLTP initialized on lowend machine. 2023-12-30 12:31:39.97 Server [INFO] Created Extended Events session 'hkenginexesession'

2023-12-30 12:31:39.97 Server Database Instant File Initialization: enabled. 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. 2023-12-30 12:31:39.97 Server Total Log Writer threads: 2. This is an informational message; no user action is required. 2023-12-30 12:31:39.98 Server clflush is selected for pmem flush operation. 2023-12-30 12:31:39.98 Server Software Usage Metrics is disabled. 2023-12-30 12:31:39.98 spid9s Starting up database 'master'. 2023-12-30 12:31:40.00 spid9s 2 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required. 2023-12-30 12:31:40.01 spid9s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required. 2023-12-30 12:31:40.07 spid9s Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details. 2023-12-30 12:31:40.07 spid9s An error occurred during Service Master Key initialization. SQLErrorCode=33095, State=8, LastOsError=0. 2023-12-30 12:31:40.07 Server CLR version v4.0.30319 loaded. 2023-12-30 12:31:40.08 spid9s Resource governor reconfiguration succeeded. 2023-12-30 12:31:40.08 spid9s SQL Server Audit is starting the audits. This is an informational message. No user action is required. 2023-12-30 12:31:40.08 spid9s SQL Server Audit has started the audits. This is an informational message. No user action is required. 2023-12-30 12:31:40.10 spid9s SQL Trace ID 1 was started by login "sa". 2023-12-30 12:31:40.11 spid9s Server name is 'SAEED-PC'. This is an informational message only. No user action is required. 2023-12-30 12:31:40.11 spid21s The certificate [Cert Hash(sha1) "B5958DD79DBA98452F90198F4B0CAF5270EA32DF"] was successfully loaded for encryption. 2023-12-30 12:31:40.12 spid21s Server is listening on [ 'any' <ipv6> 1433]. 2023-12-30 12:31:40.12 spid21s Server is listening on [ 'any' <ipv4> 1433]. 2023-12-30 12:31:40.13 spid21s Server local connection provider is ready to accept connection on [ \.\pipe\SQLLocal\MSSQLSERVER ]. 2023-12-30 12:31:40.13 spid21s Server named pipe provider is ready to accept connection on [ \.\pipe\sql\query ]. 2023-12-30 12:31:40.13 Server Server is listening on [ ::1 <ipv6> 1434]. 2023-12-30 12:31:40.13 Server Server is listening on [ 127.0.0.1 <ipv4> 1434]. 2023-12-30 12:31:40.13 Server Dedicated admin connection support was established for listening locally on port 1434. 2023-12-30 12:31:40.13 spid21s SQL Server is now ready for client connections. This is an informational message; no user action is required. 2023-12-30 12:31:40.13 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required. 2023-12-30 12:31:40.13 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/SAEED-PC ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. 2023-12-30 12:31:40.13 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/SAEED-PC:1433 ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered. 2023-12-30 12:31:40.14 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319. 2023-12-30 12:31:40.30 spid22s A new instance of the full-text filter daemon host process has been successfully started. 2023-12-30 12:31:40.37 spid25s Always On: The availability replica manager is starting. This is an informational message only. No user action is required. 2023-12-30 12:31:40.37 spid25s Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required. 2023-12-30 12:31:40.37 spid9s Starting up database 'msdb'. 2023-12-30 12:31:40.37 spid14s Starting up database 'mssqlsystemresource'. 2023-12-30 12:31:40.37 spid9s Error: 17204, Severity: 16, State: 1. 2023-12-30 12:31:40.37 spid9s FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\MSDBData.mdf for file number 1. OS error: 3(The system cannot find the path specified.). 2023-12-30 12:31:40.37 spid9s Error: 5120, Severity: 16, State: 101. 2023-12-30 12:31:40.37 spid9s Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\MSDBData.mdf". Operating system error 3: "3(The system cannot find the path specified.)". 2023-12-30 12:31:40.38 spid14s The resource database build version is 15.00.2000. This is an informational message only. No user action is required. 2023-12-30 12:31:40.38 spid9s Error: 17207, Severity: 16, State: 1. 2023-12-30 12:31:40.38 spid9s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation. 2023-12-30 12:31:40.38 spid9s File activation failure. The physical file name "C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\MSDBLog.ldf" may be incorrect. 2023-12-30 12:31:40.40 spid14s Starting up database 'model'. 2023-12-30 12:31:40.40 spid14s Error: 17204, Severity: 16, State: 1. 2023-12-30 12:31:40.40 spid14s FCB::Open failed: Could not open file C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\model.mdf for file number 1. OS error: 3(The system cannot find the path specified.). 2023-12-30 12:31:40.40 spid14s Error: 5120, Severity: 16, State: 101. 2023-12-30 12:31:40.40 spid14s Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\model.mdf". Operating system error 3: "3(The system cannot find the path specified.)". 2023-12-30 12:31:40.41 spid14s Error: 17207, Severity: 16, State: 1. 2023-12-30 12:31:40.41 spid14s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation. 2023-12-30 12:31:40.41 spid14s File activation failure. The physical file name "C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\modellog.ldf" may be incorrect. 2023-12-30 12:31:40.41 spid14s Error: 945, Severity: 14, State: 2. 2023-12-30 12:31:40.41 spid14s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details. 2023-12-30 12:31:40.41 spid14s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required. `

Help me, how to fix the issue and start the sql server services

Answer 1

First a little about network etiquette. You had added five tags to your post:

Just because you can add five tags, does not mean that you should. There is absolutely to relation in your post to Azure SQL Database. Or to SQL Server Integration Services or SQL Server Migration Assistant. Maybe to Windows 10, but as a moderator I deleted all tags but the relevant, SQL Server.

Now over to your problem. I see this error, and a few similar ones:

Could not open file C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\MSDBData.mdf for file number 1. OS error: 3(The system cannot find the path specified.).

I don't know what you have done on your machine, but the files are not where SQL Server expect them to be.

Now, I also observe this:

2023-12-30 12:31:39.83 Server Registry startup parameters: -d D:\MSSQL2019\MSSQL15.MSSQLSERVER\MSSQL\DATA\master.mdf -e D:\MSSQL2019\MSSQL15.MSSQLSERVER\MSSQL\Log\ERRORLOG -l D:\MSSQL2019\MSSQL15.MSSQLSERVER\MSSQL\DATA\mastlog.ldf

So it seems that you intended to have the files on D, but somehow that did not work out. If you look in D:\MSSQL2019\MSSQL15.MSSQLSERVER\MSSQL\DATA, do you see the files that are reporting missing in the errorlog?

I don't know the background. Did you have SQL Server running and it stopped working overnight? Or did you just install SQL Server?