SQL Express 2019 Install Failure of Database Engine Component error code: 0x851A001A on Windows 11.

Question

I have a brand new HP computer with 1 GIG SSD drive running windows 11 and keep getting the error below on install. I have googled and tried several solutions and nothing has worked. Here is what I have also found but none of this

My observations so far after reading many threads:

1. In the above environment, SQL Server 2019 will install properly on a second hard drive
2. If the Primary Hard Drive is less than 1TB, then also there is no problem (SQL Server 2019 installs properly) but this options is also not available to me
3. If you partition the 1TB SSD, the problem persists because the partition is still recognised internally as “One Single Hard Drive”
4. The issue is that Windows 11 is verifying the sector size is not over 4K and SQL Server installation fails when the hard drive sector is larger then 4096

Can anyone help get this installed. I did confirm my sector size is 512.

Detailed results:
Feature: Database Engine Services
Status: Failed
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.

Answer 1

Here is the log. I can tell you there is no D: drive on the computer
2022-02-03 14:06:20.40 Server Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64)
Sep 24 2019 13:48:23
Copyright (C) 2019 Microsoft Corporation
Express Edition (64-bit) on Windows 10 Home 10.0 <X64> (Build 22000: )

2022-02-03 14:06:20.40 Server UTC adjustment: -8:00
2022-02-03 14:06:20.40 Server (c) Microsoft Corporation.
2022-02-03 14:06:20.40 Server All rights reserved.
2022-02-03 14:06:20.40 Server Server process ID is 8840.
2022-02-03 14:06:20.40 Server System Manufacturer: 'HP', System Model: 'HP Pavilion All-in-One 27-d0xxx'.
2022-02-03 14:06:20.40 Server Authentication mode is WINDOWS-ONLY.
2022-02-03 14:06:20.40 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL15.TRACSSE\MSSQL\Log\ERRORLOG'.
2022-02-03 14:06:20.40 Server The service account is 'WORKGROUP\FIVESTAR$'. This is an informational message; no user action is required.
2022-02-03 14:06:20.40 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL15.TRACSSE\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL15.TRACSSE\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL15.TRACSSE\MSSQL\DATA\mastlog.ldf
2022-02-03 14:06:20.40 Server Command Line Startup Parameters:
-s "TRACSSE"
-m "SqlSetup"
-T 4022
-T 4010
-T 1905
-T 3701
-T 8015
2022-02-03 14:06:20.40 Server SQL Server detected 1 sockets with 8 cores per socket and 16 logical processors per socket, 16 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2022-02-03 14:06:20.40 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2022-02-03 14:06:20.40 Server Detected 16208 MB of RAM. This is an informational message; no user action is required.
2022-02-03 14:06:20.40 Server Using conventional memory in the memory manager.
2022-02-03 14:06:20.40 Server Page exclusion bitmap is enabled.
2022-02-03 14:06:20.50 Server Buffer Pool: Allocating 4194304 bytes for 2223760 hashPages.
2022-02-03 14:06:20.50 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2022-02-03 14:06:20.51 Server Buffer pool extension is already disabled. No action is necessary.
2022-02-03 14:06:20.53 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2022-02-03 14:06:20.54 Server Query Store settings initialized with enabled = 1,
2022-02-03 14:06:20.54 Server The maximum number of dedicated administrator connections for this instance is '1'
2022-02-03 14:06:20.54 Server This instance of SQL Server last reported using a process ID of 13916 at 2/3/2022 2:03:19 PM (local) 2/3/2022 10:03:19 PM (UTC). This is an informational message only; no user action is required.
2022-02-03 14:06:20.54 Server Node configuration: node 0: 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.
2022-02-03 14:06:20.55 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.
2022-02-03 14:06:20.55 Server Lock partitioning is enabled. This is an informational message only. No user action is required.
2022-02-03 14:06:20.55 Server In-Memory OLTP initialized on standard machine.
2022-02-03 14:06:20.56 Server [INFO] Created Extended Events session 'hkenginexesession'

2022-02-03 14:06:20.56 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.
2022-02-03 14:06:20.57 Server Total Log Writer threads: 2. This is an informational message; no user action is required.
2022-02-03 14:06:20.58 Server Database Mirroring Transport is disabled in the endpoint configuration.
2022-02-03 14:06:20.58 Server clflushopt is selected for pmem flush operation.
2022-02-03 14:06:20.58 Server Software Usage Metrics is disabled.
2022-02-03 14:06:20.58 spid9s Warning ******************
2022-02-03 14:06:20.58 spid9s SQL Server started in single-user mode. This an informational message only. No user action is required.
2022-02-03 14:06:20.58 spid9s Starting up database 'master'.
2022-02-03 14:06:20.60 spid9s 15 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2022-02-03 14:06:20.60 spid9s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2022-02-03 14:06:20.64 spid9s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2022-02-03 14:06:20.65 spid9s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2022-02-03 14:06:20.66 Server CLR version v4.0.30319 loaded.
2022-02-03 14:06:20.66 spid9s SQL Trace ID 1 was started by login "sa".
2022-02-03 14:06:20.66 spid9s Server name is 'FIVESTAR\TRACSSE'. This is an informational message only. No user action is required.
2022-02-03 14:06:20.67 spid9s Starting up database 'msdb'.
2022-02-03 14:06:20.67 spid14s Starting up database 'mssqlsystemresource'.
2022-02-03 14:06:20.67 spid9s Error: 17204, Severity: 16, State: 1.
2022-02-03 14:06:20.67 spid9s FCB::Open failed: Could not open file d:\dbs\sh\s19s\0924_133725\cmd\2\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\MSDBData.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2022-02-03 14:06:20.67 spid9s Error: 5120, Severity: 16, State: 101.
2022-02-03 14:06:20.67 spid9s Unable to open the physical file "d:\dbs\sh\s19s\0924_133725\cmd\2\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\MSDBData.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2022-02-03 14:06:20.67 spid9s Error: 17207, Severity: 16, State: 1.
2022-02-03 14:06:20.67 spid9s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'd:\dbs\sh\s19s\0924_133725\cmd\2\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2022-02-03 14:06:20.67 spid9s File activation failure. The physical file name "d:\dbs\sh\s19s\0924_133725\cmd\2\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\MSDBLog.ldf" may be incorrect.
2022-02-03 14:06:20.67 spid14s The resource database build version is 15.00.2000. This is an informational message only. No user action is required.
2022-02-03 14:06:20.69 spid14s Starting up database 'model'.
2022-02-03 14:06:20.69 spid14s Error: 17204, Severity: 16, State: 1.
2022-02-03 14:06:20.69 spid14s FCB::Open failed: Could not open file d:\dbs\sh\s19s\0924_133725\cmd\2\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\model.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2022-02-03 14:06:20.69 spid14s Error: 5120, Severity: 16, State: 101.
2022-02-03 14:06:20.69 spid14s Unable to open the physical file "d:\dbs\sh\s19s\0924_133725\cmd\2\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\model.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2022-02-03 14:06:20.69 spid14s Error: 17207, Severity: 16, State: 1.
2022-02-03 14:06:20.69 spid14s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'd:\dbs\sh\s19s\0924_133725\cmd\2\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2022-02-03 14:06:20.69 spid14s File activation failure. The physical file name "d:\dbs\sh\s19s\0924_133725\cmd\2\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\modellog.ldf" may be incorrect.
2022-02-03 14:06:20.69 spid14s Error: 945, Severity: 14, State: 2.
2022-02-03 14:06:20.69 spid14s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2022-02-03 14:06:20.69 spid14s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Answer 2

I note that trace flag 1800 is not present:

2022-02-03 14:06:20.40 Server Command Line Startup Parameters:
-s "TRACSSE"
-m "SqlSetup"
-T 4022
-T 4010
-T 1905
-T 3701
-T 8015

There should be a -T 1800 here, I think.
However, things here go wrong before you come to the point where things start to matter. Here is a sample:

2022-02-03 14:06:20.67 spid9s File activation failure. The physical file name "d:\dbs\sh\s19s\0924_133725\cmd\2\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\MSDBLog.ldf" may be incorrect.

I have seen this type of error in these forums more than once, but unfortunately, I have never been able to figure out what the cause is. The file path should be a path on your system, which this clearly is not.

Then again, hm, what if Setup tried to write these name earlier and failed because of the disk-sector issue?

Excuse me for thinking aloud, but I have never battled these issues myself, and so far I'm staying away from Windows 11. But I try to contribute with the little I know.

PS In the future, it is better to attach long files like these than including them in a post.

Answer 3

I did remove the -T1800 trying different things. I completely removed SQL server and reinstalled with the registry entry added before installation and then added the startup parameter. The problem is that path. Does anyone have a clue where that path is stored or how it gets written? What should be my next step?

2022-02-03 14:06:20.67 spid9s File activation failure. The physical file name "d:\dbs\sh\s19s\0924_133725\cmd\2\obj\x64retail\sql\mkmastr\databases\mkmastr.proj\MSDBLog.ldf" may be incorrect.

Answer 4

I actually got it to work. I copied the data folder on a working machine and replace it on the other machine C:\Program Files\Microsoft SQL Server\MSSQL15.TRACSSE\MSSQL\DATA and the Instance started. I suspect something with Windows 11 and the 2019 install is corrupting the master db.

Answer 5

Well I can get the instance to start but cannot do anything else once logged in with Management Studio. Is there a way to recreate the master.db. That seems to be the issue with the install.