Share via

SQL server: wait on the database engine recovery handle faile

Luis Fernando Gamez Gallardo 0 Reputation points
2023-05-07T16:52:38.2+00:00

Hi guys the problem its that im trying to install SQL server express, i had installed previously and at first the problem was that the installed instances didnt worked so i uninstalled everything so i could make a clear install, the problem is that theres something missing.

i uninstalled everything from control panel and from apps and features, also removed registers from regedit and removed the SQL server files from "program files", after everything i reboot.

Here is what my ERRORLOG shows.

2023-05-07 09:21:25.42 Server      Microsoft SQL Server 2022 (RTM) - 16.0.1000.6 (X64) 
	Oct  8 2022 05:58:25 
	Copyright (C) 2022 Microsoft Corporation
	Express Edition (64-bit) on Windows 10 Pro 10.0 <X64> (Build 22621: ) (Hypervisor)

2023-05-07 09:21:25.42 Server      UTC adjustment: -7:00
2023-05-07 09:21:25.42 Server      (c) Microsoft Corporation.
2023-05-07 09:21:25.42 Server      All rights reserved.
2023-05-07 09:21:25.42 Server      Server process ID is 8976.
2023-05-07 09:21:25.42 Server      System Manufacturer: 'LENOVO', System Model: '82KC'.
2023-05-07 09:21:25.42 Server      Authentication mode is WINDOWS-ONLY.
2023-05-07 09:21:25.42 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2023-05-07 09:21:25.43 Server      The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.
2023-05-07 09:21:25.43 Server      Registry startup parameters: 
	 -d C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\DATA\master.mdf
	 -e C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\Log\ERRORLOG
	 -l C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2023-05-07 09:21:25.43 Server      Command Line Startup Parameters:
	 -s "SQLEXPRESS"
	 -m "SqlSetup"
	 -Q
	 -q "Modern_Spanish_CI_AS"
	 -T 4022
	 -T 4010
	 -T 3659
	 -T 3610
	 -T 8015
	 -d "C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\Template Data\master.mdf"
	 -l "C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\Template Data\mastlog.ldf"
2023-05-07 09:21:25.43 Server      SQL Server detected 1 sockets with 6 cores per socket and 12 logical processors per socket, 12 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2023-05-07 09:21:25.43 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2023-05-07 09:21:25.43 Server      Detected 5989 MB of RAM. This is an informational message; no user action is required.
2023-05-07 09:21:25.43 Server      Using conventional memory in the memory manager.
2023-05-07 09:21:25.43 Server      Detected pause instruction latency: 63 cycles.
2023-05-07 09:21:25.43 Server      Spin divider value used: 1
2023-05-07 09:21:25.43 Server      Page exclusion bitmap is enabled.
2023-05-07 09:21:25.51 Server      Buffer Pool: Allocating 1048576 bytes for 942080 hashPages.
2023-05-07 09:21:25.53 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2023-05-07 09:21:25.56 Server      Buffer pool extension is already disabled. No action is necessary.
2023-05-07 09:21:25.60 Server      CPU vectorization level(s) detected:  SSE SSE2 SSE3 SSSE3 SSE41 SSE42 AVX AVX2 POPCNT BMI1 BMI2
2023-05-07 09:21:25.62 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2023-05-07 09:21:25.65 Server      Query Store settings initialized with enabled = 1, 
2023-05-07 09:21:25.66 Server      The maximum number of dedicated administrator connections for this instance is '1'
2023-05-07 09:21:25.66 Server      This instance of SQL Server last reported using a process ID of 14024 at 07/05/2023 09:21:22 a. m. (local) 07/05/2023 04:21:22 p. m. (UTC). This is an informational message only; no user action is required.
2023-05-07 09:21:25.66 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.
2023-05-07 09:21:25.67 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-07 09:21:25.69 Server      In-Memory OLTP initialized on lowend machine.
2023-05-07 09:21:25.71 Server      [INFO] Created Extended Events session 'hkenginexesession'
2023-05-07 09:21:25.72 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-05-07 09:21:25.72 Server      Total Log Writer threads: 2, Node CPUs: 4, Nodes: 1, Log Writer threads per CPU: 1, Log Writer threads per Node: 2
2023-05-07 09:21:25.72 Server      Database Mirroring Transport is disabled in the endpoint configuration.
2023-05-07 09:21:25.72 Server      clwb is selected for pmem flush operation.
2023-05-07 09:21:25.72 Server      Software Usage Metrics is disabled.
2023-05-07 09:21:25.72 spid26s     Warning ******************
2023-05-07 09:21:25.72 spid26s     SQL Server started in single-user mode. This an informational message only. No user action is required.
2023-05-07 09:21:25.73 spid26s     Starting up database 'master'.
2023-05-07 09:21:25.75 spid26s     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.SQLEXPRESS\MSSQL\Template Data\master.mdf.
2023-05-07 09:21:25.75 spid26s     Unable to create stack dump file due to stack shortage (ex_terminator - Last chance exception handling)
2023-05-07 09:21:25.75 spid26s     Stack Signature for the dump is 0x0000000000000000
2023-05-07 09:21:25.75 spid26s     CDmpClient::ExecuteAllCallbacks started.
2023-05-07 09:21:25.75 spid26s     XE_DumpCallbacks is executing...
2023-05-07 09:21:25.78 spid26s     DumpCallbackSOS is executing...
2023-05-07 09:21:25.78 spid26s     DumpCallbackEE is executing...
2023-05-07 09:21:25.79 Server      CLR version v4.0.30319 loaded.
2023-05-07 09:21:25.79 spid26s     DumpCallbackSE is executing...
2023-05-07 09:21:25.79 spid26s     DumpCallbackSEAM is executing...
2023-05-07 09:21:25.79 spid26s     DumpCallbackSSB is executing...
2023-05-07 09:21:25.83 spid26s     DumpCallbackQE is executing...
2023-05-07 09:21:25.83 spid26s     DumpCallbackFullText is executing...
2023-05-07 09:21:25.83 spid26s     DumpCallbackSQLCLR is executing...
2023-05-07 09:21:25.83 spid26s     DumpCallbackHk is executing...
2023-05-07 09:21:25.84 spid26s     DumpCallbackRepl is executing...
2023-05-07 09:21:25.84 spid26s     DumpCallbackPolyBase is executing...
2023-05-07 09:21:25.84 spid26s     CDmpClient::ExecuteAllCallbacks completed. Time elapsed: 0 seconds.
2023-05-07 09:21:25.88 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2023-05-07 09:21:27.23 spid26s     External dump process return code 0x20000001.
External dump process returned no errors.
SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,365 questions
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Erland Sommarskog 107.2K Reputation points
    2023-05-07T17:14:34.35+00:00

    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.SQLEXPRESS\MSSQL\Template Data\master.mdf.

    You are running into a known issue where Windows 11 for certain SSDs reports a disk-sector size that SQL Server is not able to cope with. Microsoft has published this article with workarounds.

    0 comments
  2. ZoeHui-MSFT 35,556 Reputation points
    2023-05-08T01:38:55.7633333+00:00

    Hi @Luis Fernando Gamez Gallardo,

    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.SQLEXPRESS\MSSQL\Template Data\master.mdf.

    It is a known issue, please check it out there.

    Troubleshoot errors related to system disk sector size greater than 4 KB

    Regards，

    Zoe Hui

    If the answer is helpful, please click "Accept Answer" and upvote it.