Error installing SQL Server: Exit code(Decimal):-2061893606 Error description: Wait on the database Engine recoveryhandle failed SQL installation failed

Question

I'm having the same problem installing SQL server 2022. I checked the error logs at I see it says

Unable to create stack dump file due to stack shortage

what should i do?

error log

2023-06-02 20:54:23.10 Server      Microsoft SQL Server 2022 (RTM) - 16.0.1000.6 (X64) 
	Oct  8 2022 05:58:25 
	Copyright (C) 2022 Microsoft Corporation
	Developer Edition (64-bit) on Windows 10 Home 10.0 <X64> (Build 22621: ) (Hypervisor)

2023-06-02 20:54:23.10 Server      UTC adjustment: -4:00
2023-06-02 20:54:23.10 Server      (c) Microsoft Corporation.
2023-06-02 20:54:23.10 Server      All rights reserved.
2023-06-02 20:54:23.10 Server      Server process ID is 7132.
2023-06-02 20:54:23.10 Server      System Manufacturer: 'ASUSTeK COMPUTER INC.', System Model: 'ROG Zephyrus G14 GA401QM_GA401QM'.
2023-06-02 20:54:23.11 Server      Authentication mode is WINDOWS-ONLY.
2023-06-02 20:54:23.11 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2023-06-02 20:54:23.11 Server      The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.
2023-06-02 20:54:23.11 Server      Registry startup parameters: 
	 -d C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\DATA\master.mdf
	 -e C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\Log\ERRORLOG
	 -l C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2023-06-02 20:54:23.11 Server      Command Line Startup Parameters:
	 -s "MSSQLSERVER"
	 -m "SqlSetup"
	 -Q
	 -q "SQL_Latin1_General_CP1_CI_AS"
	 -T 4022
	 -T 4010
	 -T 3659
	 -T 3610
	 -T 8015
2023-06-02 20:54:23.11 Server      SQL Server detected 1 sockets with 8 cores per socket and 16 logical processors per socket, 16 total logical processors; using 16 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2023-06-02 20:54:23.11 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2023-06-02 20:54:23.11 Server      Detected 15776 MB of RAM. This is an informational message; no user action is required.
2023-06-02 20:54:23.11 Server      Using conventional memory in the memory manager.
2023-06-02 20:54:23.11 Server      Detected pause instruction latency: 33 cycles.
2023-06-02 20:54:23.11 Server      Page exclusion bitmap is enabled.
2023-06-02 20:54:23.26 Server      Buffer Pool: Allocating 2097152 bytes for 1271385 hashPages.
2023-06-02 20:54:23.27 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2023-06-02 20:54:23.28 Server      Buffer pool extension is already disabled. No action is necessary.
2023-06-02 20:54:23.30 Server      CPU vectorization level(s) detected:  SSE SSE2 SSE3 SSSE3 SSE41 SSE42 AVX AVX2 POPCNT BMI1 BMI2
2023-06-02 20:54:23.31 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2023-06-02 20:54:23.32 Server      Query Store settings initialized with enabled = 1, 
2023-06-02 20:54:23.32 Server      The maximum number of dedicated administrator connections for this instance is '1'
2023-06-02 20:54:23.33 Server      This instance of SQL Server last reported using a process ID of 17756 at 02/06/2023 8:54:20 pm (local) 03/06/2023 12:54:20 am (UTC). This is an informational message only; no user action is required.
2023-06-02 20:54:23.33 Server      Node configuration: node 0: CPU mask: 0x000000000000ffff:0 Active CPU mask: 0x000000000000ffff: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-06-02 20:54:23.34 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-06-02 20:54:23.34 Server      Lock partitioning is enabled.  This is an informational message only. No user action is required.
2023-06-02 20:54:23.34 Server      In-Memory OLTP initialized on lowend machine.
2023-06-02 20:54:23.35 Server      [INFO] Created Extended Events session 'hkenginexesession'
2023-06-02 20:54:23.35 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-06-02 20:54:23.35 Server      Total Log Writer threads: 2, Node CPUs: 8, Nodes: 1, Log Writer threads per CPU: 1, Log Writer threads per Node: 2
2023-06-02 20:54:23.36 Server      Database Mirroring Transport is disabled in the endpoint configuration.
2023-06-02 20:54:23.36 Server      clwb is selected for pmem flush operation.
2023-06-02 20:54:23.37 spid42s     Warning ******************
2023-06-02 20:54:23.37 spid42s     SQL Server started in single-user mode. This an informational message only. No user action is required.
2023-06-02 20:54:23.37 Server      Software Usage Metrics is disabled.
2023-06-02 20:54:23.37 spid42s     Starting up database 'master'.
2023-06-02 20:54:23.38 spid42s     There have been 256 misaligned log IOs which required falling back to synchronous IO.  The current IO is on file C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\DATA\master.mdf.
2023-06-02 20:54:23.38 spid42s     Unable to create stack dump file due to stack shortage (ex_terminator - Last chance exception handling)
2023-06-02 20:54:23.38 spid42s     Stack Signature for the dump is 0x0000000000000000
2023-06-02 20:54:23.38 spid42s     CDmpClient::ExecuteAllCallbacks started.
2023-06-02 20:54:23.38 spid42s     XE_DumpCallbacks is executing...
2023-06-02 20:54:23.40 spid42s     DumpCallbackSOS is executing...
2023-06-02 20:54:23.40 spid42s     DumpCallbackEE is executing...
2023-06-02 20:54:23.40 spid42s     DumpCallbackSE is executing...
2023-06-02 20:54:23.40 spid42s     DumpCallbackSEAM is executing...
2023-06-02 20:54:23.41 spid42s     DumpCallbackSSB is executing...
2023-06-02 20:54:23.44 spid42s     DumpCallbackQE is executing...
2023-06-02 20:54:23.44 spid42s     DumpCallbackFullText is executing...
2023-06-02 20:54:23.44 spid42s     DumpCallbackSQLCLR is executing...
2023-06-02 20:54:23.44 spid42s     DumpCallbackHk is executing...
2023-06-02 20:54:23.44 Server      CLR version v4.0.30319 loaded.
2023-06-02 20:54:23.44 spid42s     DumpCallbackRepl is executing...
2023-06-02 20:54:23.44 spid42s     DumpCallbackPolyBase is executing...
2023-06-02 20:54:23.44 spid42s     CDmpClient::ExecuteAllCallbacks completed. Time elapsed: 0 seconds.
2023-06-02 20:54:23.49 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2023-06-02 20:54:23.53 spid42s     External dump process return code 0x20000011.
Error - Failed while writing mini dump.

Answer 1

You are running into a known issue where Windows 11 for certain disk drives reports a disk-sector size that SQL Server cannot cope with. Microsoft has published this article with workarounds: https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size.

Answer 2

Hi @johvahn

Thanks for the question.

Please look for a similar discussion and a potential solution for the error you are experiencing below.

Hopefully, it will help resolve your issue with the provided workaround.

https://learn.microsoft.com/en-us/answers/questions/1150619/sql-server-2022-installation-failing-with-error-wa

Thank you!