Error code: 2061893606

Question

Error code: 2061893606

aaron urrutia 20

I've been stuck on installing and uninstalling the application sql server 2019 and everytime it just shows an error. SO... I went ahead and hard reset my laptop twice. Still no luck, I've been stuck on this for about a month and I am time mangaged to turn in some schoolwork. I can't turn it in because I need this application up and running. The error occurs the moment it is trying to install the product. I've spoken to my IT tech center, I've gone to best buy, I've followed all the steps to get this to work and nothing. Can y'all please just help me? Screenshot 2023-08-06 102748

ZoeHui-MSFT 41,491 Reputation points

2023-08-25T06:59:14.68+00:00

Hi @aaron urrutia,

Check the error log for details so that we could narrow down the issue.
aaron urrutia 20 Reputation points

2023-08-25T15:00:01.5466667+00:00

this is stuff I get
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2023-08-25T15:18:43.8566667+00:00

Seems like you tried a Repair after the failed install. But you did not come far enough with the install for the Repair to work.

Have you checked the SQL Server errorlog yet? (See my Answer below.)
aaron urrutia 20 Reputation points

2023-08-25T16:14:49.67+00:00

I've tried everything. I've uninstalled and reinstalled this application
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2023-08-25T21:09:06.85+00:00

You posted the errorlog. The message about 256 misliagned reads is there, and thus you should check the article that I linked to.
aaron urrutia 20 Reputation points

2023-08-27T00:35:12.1966667+00:00

@Erland Sommarskog I have followed the steps on the article, still no help. May you guide me on exactly what I need to do. I am unaware on fixing this issue. Sorry to ask and bother, I'm just stuck and frustrating on what needs to be repaired or removed.
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2023-08-27T08:26:58.13+00:00

I'm sorry, but I can't help further. I never had to battle this error myself. But my impression is that most people who have encountered this problem have been able to work from the article. I've noticed that some people have said that rather setting a value to 4096, they got things to work by setting this value to 4095 instead. (Which sounds funny to me.)

Accepted answer

0 additional answers

Your answer

ZoeHui-MSFT 41,491 Reputation points

2023-08-25T06:59:14.68+00:00

Hi @aaron urrutia,

Check the error log for details so that we could narrow down the issue.
aaron urrutia 20 Reputation points

2023-08-25T15:00:01.5466667+00:00

this is stuff I get
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2023-08-25T15:18:43.8566667+00:00

Seems like you tried a Repair after the failed install. But you did not come far enough with the install for the Repair to work.

Have you checked the SQL Server errorlog yet? (See my Answer below.)
aaron urrutia 20 Reputation points

2023-08-25T16:14:49.67+00:00

I've tried everything. I've uninstalled and reinstalled this application
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2023-08-25T21:09:06.85+00:00

You posted the errorlog. The message about 256 misliagned reads is there, and thus you should check the article that I linked to.
aaron urrutia 20 Reputation points

2023-08-27T00:35:12.1966667+00:00

@Erland Sommarskog I have followed the steps on the article, still no help. May you guide me on exactly what I need to do. I am unaware on fixing this issue. Sorry to ask and bother, I'm just stuck and frustrating on what needs to be repaired or removed.
Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator

2023-08-27T08:26:58.13+00:00

I'm sorry, but I can't help further. I never had to battle this error myself. But my impression is that most people who have encountered this problem have been able to work from the article. I've noticed that some people have said that rather setting a value to 4096, they got things to work by setting this value to 4095 instead. (Which sounds funny to me.)

Answer 1

Erland Sommarskog 121.4K MVP Volunteer Moderator

The message Wait on the Database Engine recovery handle failed is a generic error that means that SQL Server did not start when Setup wanted to run configuration steps. To understand why it did not start, you need to look in the SQL Server errorlog, which you find in C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\LOG\ERRORLOG.

If you see a message about 256 misaligned reads, you are running into a known issue where Windows 11 for some disk drives reports a sector size that SQL Server does not cope with. Microsoft has published an article with workarounds for the problem.

If you don't see the message about misaligned reads, feel free to upload the errorlog here, so we can look at it. You will need to rename to ERRORLOG.txt for the forum software to accept it.

aaron urrutia 20

2023-08-25 09:22:02.66 Server      Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64) 
	Sep 24 2019 13:48:23 
	Copyright (C) 2019 Microsoft Corporation
	Enterprise Evaluation Edition (64-bit) on Windows 10 Home 10.0 <X64> (Build 22621: ) (Hypervisor)

2023-08-25 09:22:02.66 Server      UTC adjustment: -6:00
2023-08-25 09:22:02.66 Server      (c) Microsoft Corporation.
2023-08-25 09:22:02.70 Server      All rights reserved.
2023-08-25 09:22:02.70 Server      Server process ID is 17708.
2023-08-25 09:22:02.70 Server      System Manufacturer: 'LENOVO', System Model: '82RK'.
2023-08-25 09:22:02.70 Server      Authentication mode is WINDOWS-ONLY.
2023-08-25 09:22:02.70 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER01\MSSQL\Log\ERRORLOG'.
2023-08-25 09:22:02.70 Server      The service account is 'NT Service\MSSQL$MSSQLSERVER01'. This is an informational message; no user action is required.
2023-08-25 09:22:02.70 Server      Registry startup parameters: 
	 -d C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER01\MSSQL\DATA\master.mdf
	 -e C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER01\MSSQL\Log\ERRORLOG
	 -l C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER01\MSSQL\DATA\mastlog.ldf
2023-08-25 09:22:02.70 Server      Command Line Startup Parameters:
	 -s "MSSQLSERVER01"
	 -m "SqlSetup"
	 -Q
	 -q "SQL_Latin1_General_CP1_CI_AS"
	 -T 4022
	 -T 4010
	 -T 3659
	 -T 3610
	 -T 8015
2023-08-25 09:22:02.70 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.
2023-08-25 09:22:02.70 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2023-08-25 09:22:02.70 Server      Detected 7916 MB of RAM. This is an informational message; no user action is required.
2023-08-25 09:22:02.70 Server      Using conventional memory in the memory manager.
2023-08-25 09:22:02.70 Server      Page exclusion bitmap is enabled.
2023-08-25 09:22:02.81 Server      Buffer Pool: Allocating 524288 bytes for 416525 hashPages.
2023-08-25 09:22:02.82 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2023-08-25 09:22:02.84 Server      Buffer pool extension is already disabled. No action is necessary.
2023-08-25 09:22:02.86 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2023-08-25 09:22:02.88 Server      Query Store settings initialized with enabled = 1, 
2023-08-25 09:22:02.88 Server      The maximum number of dedicated administrator connections for this instance is '1'
2023-08-25 09:22:02.88 Server      This instance of SQL Server last reported using a process ID of 18068 at 8/25/2023 9:22:00 AM (local) 8/25/2023 3:22:00 PM (UTC). This is an informational message only; no user action is required.
2023-08-25 09:22:02.88 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.
2023-08-25 09:22:02.88 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-08-25 09:22:02.89 Server      In-Memory OLTP initialized on lowend machine.
2023-08-25 09:22:02.93 Server      [INFO] Created Extended Events session 'hkenginexesession'

2023-08-25 09:22:02.93 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-08-25 09:22:02.94 Server      Total Log Writer threads: 2. This is an informational message; no user action is required.
2023-08-25 09:22:02.94 Server      Database Mirroring Transport is disabled in the endpoint configuration.
2023-08-25 09:22:02.94 Server      clwb is selected for pmem flush operation.
2023-08-25 09:22:02.94 spid10s     Warning ******************
2023-08-25 09:22:02.94 Server      Software Usage Metrics is disabled.
2023-08-25 09:22:02.94 spid10s     SQL Server started in single-user mode. This an informational message only. No user action is required.
2023-08-25 09:22:02.95 spid10s     Starting up database 'master'.
2023-08-25 09:22:02.96 spid10s     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\MSSQL15.MSSQLSERVER01\MSSQL\DATA\master.mdf.
2023-08-25 09:22:03.01 Server      CLR version v4.0.30319 loaded.
2023-08-25 09:22:03.09 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.

Share via

Error code: 2061893606

0 additional answers

Your answer