SQL Server install error Wait on the Database Engine Recovery Handle Failed

Question

TITLE: Microsoft SQL Server 2022 Setup

The following error has occurred:

Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.

This is file ERRORLOG.

Please help me!

2023-05-21 11:30:29.12 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 Single Language 10.0  (Build 22621: )

2023-05-21 11:30:29.12 Server      UTC adjustment: 7:00
2023-05-21 11:30:29.12 Server      (c) Microsoft Corporation.
2023-05-21 11:30:29.13 Server      All rights reserved.
2023-05-21 11:30:29.13 Server      Server process ID is 13120.
2023-05-21 11:30:29.13 Server      System Manufacturer: 'ASUSTeK COMPUTER INC.', System Model: 'ROG Strix G513IH_G513IH'.
2023-05-21 11:30:29.13 Server      Authentication mode is MIXED.
2023-05-21 11:30:29.13 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL16.TRUNG\MSSQL\Log\ERRORLOG'.
2023-05-21 11:30:29.13 Server      The service account is 'NT Service\MSSQL$TRUNG'. This is an informational message; no user action is required.
2023-05-21 11:30:29.13 Server      Registry startup parameters: 
	 -d C:\Program Files\Microsoft SQL Server\MSSQL16.TRUNG\MSSQL\DATA\master.mdf
	 -e C:\Program Files\Microsoft SQL Server\MSSQL16.TRUNG\MSSQL\Log\ERRORLOG
	 -l C:\Program Files\Microsoft SQL Server\MSSQL16.TRUNG\MSSQL\DATA\mastlog.ldf
2023-05-21 11:30:29.13 Server      Command Line Startup Parameters:
	 -s "TRUNG"
	 -m "SqlSetup"
	 -Q
	 -q "Vietnamese_CI_AS"
	 -T 4022
	 -T 4010
	 -T 3659
	 -T 3610
	 -T 8015
2023-05-21 11:30:29.13 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-05-21 11:30:29.13 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2023-05-21 11:30:29.13 Server      Detected 7599 MB of RAM. This is an informational message; no user action is required.
2023-05-21 11:30:29.13 Server      Using conventional memory in the memory manager.
2023-05-21 11:30:29.13 Server      Detected pause instruction latency: 29 cycles.
2023-05-21 11:30:29.13 Server      Page exclusion bitmap is enabled.
2023-05-21 11:30:29.26 Server      Buffer Pool: Allocating 524288 bytes for 339578 hashPages.
2023-05-21 11:30:29.27 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2023-05-21 11:30:29.28 Server      Buffer pool extension is already disabled. No action is necessary.
2023-05-21 11:30:29.30 Server      CPU vectorization level(s) detected:  SSE SSE2 SSE3 SSSE3 SSE41 SSE42 AVX AVX2 POPCNT BMI1 BMI2
2023-05-21 11:30:29.31 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2023-05-21 11:30:29.33 Server      Query Store settings initialized with enabled = 1, 
2023-05-21 11:30:29.33 Server      The maximum number of dedicated administrator connections for this instance is '1'
2023-05-21 11:30:29.33 Server      This instance of SQL Server last reported using a process ID of 2220 at 21/05/2023 11:30:28 SA (local) 21/05/2023 4:30:28 SA (UTC). This is an informational message only; no user action is required.
2023-05-21 11:30:29.34 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-05-21 11:30:29.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-05-21 11:30:29.34 Server      Lock partitioning is enabled.  This is an informational message only. No user action is required.
2023-05-21 11:30:29.35 Server      In-Memory OLTP initialized on lowend machine.
2023-05-21 11:30:29.37 Server      [INFO] Created Extended Events session 'hkenginexesession'
2023-05-21 11:30:29.37 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.
2023-05-21 11:30:29.37 Server      Total Log Writer threads: 2, Node CPUs: 8, Nodes: 1, Log Writer threads per CPU: 1, Log Writer threads per Node: 2
2023-05-21 11:30:29.38 Server      Database Mirroring Transport is disabled in the endpoint configuration.
2023-05-21 11:30:29.38 Server      clwb is selected for pmem flush operation.
2023-05-21 11:30:29.38 spid43s     Warning ******************
2023-05-21 11:30:29.38 Server      Software Usage Metrics is disabled.
2023-05-21 11:30:29.38 spid43s     SQL Server started in single-user mode. This an informational message only. No user action is required.
2023-05-21 11:30:29.38 spid43s     Starting up database 'master'.
2023-05-21 11:30:29.40 spid43s     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.TRUNG\MSSQL\DATA\master.mdf.
2023-05-21 11:30:29.40 spid43s     05/21/23 11:30:29 Stack Overflow Dump not possible - Exception c00000fd EXCEPTION_STACK_OVERFLOW at 0x00007FFCE52EA375
2023-05-21 11:30:29.40 spid43s     SqlDumpExceptionHandler: Address=0x00007FFCE52EA375 Exception Code = c00000fd
2023-05-21 11:30:29.40 spid43s     Rax=00000000e74affd8 Rbx=0000000000000000 Rcx=000000003fb9e040 Rdx=0000000041499000
2023-05-21 11:30:29.40 spid43s     Rsi=000000003fb9e040 Rdi=0000000000004000 Rip=00000000e52ea375 Rsp=0000000053612000
2023-05-21 11:30:29.40 spid43s     Rbp=0000000053612110 EFlags=0000000000010246
2023-05-21 11:30:29.40 spid43s     cs=0000000000000033 ss=000000000000002b ds=000000000000002b
es=000000000000002b fs=0000000000000053 gs=000000000000002b
2023-05-21 11:30:29.47 Server      CLR version v4.0.30319 loaded.
2023-05-21 11:30:29.53 spid43s     Frame 0: 0x00007FFCE8625F16
2023-05-21 11:30:29.53 spid43s     Frame 1: 0x00007FFCE955D6B6
2023-05-21 11:30:29.53 spid43s     Frame 2: 0x00007FFCE86258A0
2023-05-21 11:30:29.53 spid43s     Frame 3: 0x00007FFD0F849C16
2023-05-21 11:30:29.53 spid43s     Frame 4: 0x00007FFD0F7E4BDC
2023-05-21 11:30:29.53 spid43s     Frame 5: 0x00007FFD0F7E4E5B
2023-05-21 11:30:29.53 spid43s     Frame 6: 0x00007FFD60BCEE85
2023-05-21 11:30:29.53 spid43s     Frame 7: 0x00007FFD60BC3750
2023-05-21 11:30:29.53 spid43s     Frame 8: 0x00007FFD60BC3168
2023-05-21 11:30:29.53 spid43s     Frame 9: 0x00007FFD60BC4048
2023-05-21 11:30:29.53 spid43s     Frame 10: 0x00007FFD60BCFA41
2023-05-21 11:30:29.53 spid43s     Frame 11: 0x00007FFD70393CFF
2023-05-21 11:30:29.53 spid43s     Frame 12: 0x00007FFD7030E456
2023-05-21 11:30:29.53 spid43s     Frame 13: 0x00007FFD70392CEE
2023-05-21 11:30:29.53 spid43s     Frame 14: 0x00007FFCE52EA375
2023-05-21 11:30:29.53 spid43s     Frame 15: 0x00007FFCE64BA898
2023-05-21 11:30:29.53 spid43s     
2023-05-21 11:30:29.53 spid43s     TotalPhysicalMemory = 7968247808, AvailablePhysicalMemory = 1216176128
2023-05-21 11:30:29.53 spid43s     AvailableVirtualMemory = 140715544518656, AvailablePagingFile = 1880776704
2023-05-21 11:30:29.53 spid43s     Stack Signature for the dump is 0x00000001479B9544
2023-05-21 11:30:29.65 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2023-05-21 11:30:30.19 spid43s     External dump process return code 0x20000001.
External dump process returned no errors.
2023-05-21 11:30:30.21 spid43s     Unable to create stack dump file due to stack shortage (ex_terminator - Last chance exception handling)
2023-05-21 11:30:30.21 spid43s     Stack Signature for the dump is 0x0000000000000000
2023-05-21 11:30:30.21 spid43s     CDmpClient::ExecuteAllCallbacks started.
2023-05-21 11:30:30.21 spid43s     XE_DumpCallbacks is executing...
2023-05-21 11:30:30.22 spid43s     DumpCallbackSOS is executing...
2023-05-21 11:30:30.22 spid43s     DumpCallbackEE is executing...
2023-05-21 11:30:30.22 spid43s     DumpCallbackSE is executing...
2023-05-21 11:30:30.22 spid43s     DumpCallbackSEAM is executing...
2023-05-21 11:30:30.22 spid43s     DumpCallbackSSB is executing...
2023-05-21 11:30:30.23 spid43s     DumpCallbackQE is executing...
2023-05-21 11:30:30.23 spid43s     DumpCallbackFullText is executing...
2023-05-21 11:30:30.23 spid43s     DumpCallbackSQLCLR is executing...
2023-05-21 11:30:30.23 spid43s     DumpCallbackHk is executing...
2023-05-21 11:30:30.24 spid43s     DumpCallbackRepl is executing...
2023-05-21 11:30:30.24 spid43s     DumpCallbackPolyBase is executing...
2023-05-21 11:30:30.24 spid43s     CDmpClient::ExecuteAllCallbacks completed. Time elapsed: 0 seconds.
2023-05-21 11:30:30.97 spid43s     External dump process return code 0x20000001.
External dump process returned no errors.

Answer

2023-05-21 11:30:29.40 spid43s     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.TRUNG\MSSQL\DATA\master.mdf.

You are running into a known issue where Windows 11 some disk models reports a disk sector size that SQL Server cannot cope with. Microsoft has published an article with workarounds for the problem.

Answer

Hi @Trung Đào Mạnh

Yes, as Erland said, you can refer to this document to solve the problem: https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size.

This link also provides some information about your error: https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/message-misaligned-log-ios-which-required-falling-back-to/ba-p/367796.

Best regards,

Aniya

SQL Server install error Wait on the Database Engine Recovery Handle Failed

2 answers