Unable to install SQL Server (setup.exe).

Akanksha Pandey 0

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.

LiHongMSFT-4306 29,441 Reputation points

2024-12-20T09:03:22.3533333+00:00

Hi @Akanksha Pandey

Please attach the error logs: Summary.txt file and Detail.txt file.

View and Read SQL Server Setup Log Files - SQL Server | Microsoft Learn
Akanksha Pandey 0 Reputation points

2024-12-20T10:50:40.8633333+00:00

please find the error log file here
Akanksha Pandey 0 Reputation points

2024-12-20T10:51:26.25+00:00
2024-12-20 14:03:43.45 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 <X64> (Build 26100: ) (Hypervisor)

2024-12-20 14:03:43.45 Server UTC adjustment: 5:30

2024-12-20 14:03:43.45 Server (c) Microsoft Corporation.

2024-12-20 14:03:43.45 Server All rights reserved.

2024-12-20 14:03:43.45 Server Server process ID is 15708.

2024-12-20 14:03:43.45 Server System Manufacturer: 'HP', System Model: 'HP Pavilion Laptop 14-ec1xxx'.

2024-12-20 14:03:43.45 Server Authentication mode is WINDOWS-ONLY.

2024-12-20 14:03:43.45 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\Log\ERRORLOG'.

2024-12-20 14:03:43.46 Server The service account is 'NT Service\MSSQLSERVER'. This is an informational message; no user action is required.

2024-12-20 14:03:43.46 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

2024-12-20 14:03:43.46 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

2024-12-20 14:03:43.46 Server SQL Server detected 1 sockets with 6 cores per socket and 12 logical processors per socket, 12 total logical processors; using 12 logical processors based on SQL Server licensing. This is an informational message; no user action is required.

2024-12-20 14:03:43.46 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2024-12-20 14:03:43.46 Server Detected 7520 MB of RAM. This is an informational message; no user action is required.

2024-12-20 14:03:43.46 Server Using conventional memory in the memory manager.

2024-12-20 14:03:43.46 Server Detected pause instruction latency: 23 cycles.

2024-12-20 14:03:43.46 Server Page exclusion bitmap is enabled.

2024-12-20 14:03:43.53 Server Buffer Pool: Allocating 2097152 bytes for 1203291 hashPages.

2024-12-20 14:03:43.54 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)

2024-12-20 14:03:43.55 Server Buffer pool extension is already disabled. No action is necessary.

2024-12-20 14:03:43.57 Server CPU vectorization level(s) detected: SSE SSE2 SSE3 SSSE3 SSE41 SSE42 AVX AVX2 POPCNT BMI1 BMI2

2024-12-20 14:03:43.58 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.

2024-12-20 14:03:43.59 Server Query Store settings initialized with enabled = 1,

2024-12-20 14:03:43.59 Server The maximum number of dedicated administrator connections for this instance is '1'

2024-12-20 14:03:43.59 Server This instance of SQL Server last reported using a process ID of 20000 at 20-12-2024 14:03:41 (local) 20-12-2024 08:33:41 (UTC). This is an informational message only; no user action is required.

2024-12-20 14:03:43.59 Server Node configuration: node 0: CPU mask: 0x0000000000000fff:0 Active CPU mask: 0x0000000000000fff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

2024-12-20 14:03:43.60 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.

2024-12-20 14:03:43.61 Server In-Memory OLTP initialized on lowend machine.

2024-12-20 14:03:43.61 Server [INFO] Created Extended Events session 'hkenginexesession'

2024-12-20 14:03:43.61 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.

2024-12-20 14:03:43.62 Server Total Log Writer threads: 2, Node CPUs: 6, Nodes: 1, Log Writer threads per CPU: 1, Log Writer threads per Node: 2

2024-12-20 14:03:43.62 Server Database Mirroring Transport is disabled in the endpoint configuration.

2024-12-20 14:03:43.62 Server clwb is selected for pmem flush operation.

2024-12-20 14:03:43.62 spid34s Warning ******************

2024-12-20 14:03:43.62 Server Software Usage Metrics is disabled.

2024-12-20 14:03:43.62 spid34s SQL Server started in single-user mode. This an informational message only. No user action is required.

2024-12-20 14:03:43.62 spid34s Starting up database 'master'.

2024-12-20 14:03:43.63 spid34s 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.

2024-12-20 14:03:43.71 spid34s Unable to create stack dump file due to stack shortage (ex_terminator - Last chance exception handling)

2024-12-20 14:03:43.72 spid34s Stack Signature for the dump is 0x0000000000000000

2024-12-20 14:03:43.72 spid34s CDmpClient::ExecuteAllCallbacks started.

2024-12-20 14:03:43.72 spid34s XE_DumpCallbacks is executing...

2024-12-20 14:03:43.74 spid34s DumpCallbackSOS is executing...

2024-12-20 14:03:43.74 spid34s DumpCallbackEE is executing...

2024-12-20 14:03:43.74 spid34s DumpCallbackSE is executing...

2024-12-20 14:03:43.74 spid34s DumpCallbackSEAM is executing...

2024-12-20 14:03:43.74 Server CLR version v4.0.30319 loaded.

2024-12-20 14:03:43.74 spid34s DumpCallbackSSB is executing...

2024-12-20 14:03:43.77 spid34s DumpCallbackQE is executing...

2024-12-20 14:03:43.77 spid34s DumpCallbackFullText is executing...

2024-12-20 14:03:43.77 spid34s DumpCallbackSQLCLR is executing...

2024-12-20 14:03:43.77 spid34s DumpCallbackHk is executing...

2024-12-20 14:03:43.78 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319.

2024-12-20 14:03:43.78 spid34s DumpCallbackRepl is executing...

2024-12-20 14:03:43.78 spid34s DumpCallbackPolyBase is executing...

2024-12-20 14:03:43.78 spid34s CDmpClient::ExecuteAllCallbacks completed. Time elapsed: 0 seconds.

2024-12-20 14:03:44.59 spid34s External dump process return code 0x20000001.

External dump process returned no errors.

1 answer

Erland Sommarskog 114.2K Reputation points MVP

2024-12-20T22:38:48.8233333+00:00

2024-12-20 14:03:43.63 spid34s 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.

You are running into a known issue where Windows 11 for some disk drives report a disk sector size that SQL Server is not able to handle. Microsoft has published an article with workarounds for the problem.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Unable to install SQL Server (setup.exe).

1 answer

Your answer