Unable to install SQL Server(setup.exe). Exit Code(Decimal: 2061893606Error description. Wait on the Database Engine recovery handle failed

Obehi 41 Reputation points
2022-01-30T05:25:54.72+00:00

169510-image.png

SQL Server Other
{count} votes

13 answers

Sort by: Most helpful
  1. YufeiShao-msft 7,146 Reputation points
    2022-01-31T02:08:53.613+00:00

    Hi @Obehi ,

    This thread mentions a similar error, of course some of them are obsolete, in the official doc, win11 has been already list as supported SQL Server 2019.
    At the same time, at lease one problem still exists as mentioned in the thread above, this issue seems to be due to a change in how Windows handles the reported sector size for certain NVMe SSDs but the investigation is still ongoing.
    If you find you have the same error after you check your error log, there is a possible solution:
    Install SQL on a secondary drive(if able) that is separate physical disk from the system's C: drive, creating a VHD to use for the SQL Server installation, or enabling TF1800. There are additional documentation updates planned to provide more information regarding this scenario.

    -------------

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.

  2. Obehi 41 Reputation points
    2022-02-02T03:34:19.35+00:00

    Hello, this is getting frustrating. I have been trying to install the SQL server for over 3 days to no avail.

    What am I supposed to do with this link below?

    Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
    Error help link: https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=15.0.4013.40&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026

    Please I need someone to help me resolve this.

    @YufeiShao-msft
    Can you please put me through on how to do this: "If you find you have the same error after you check your error log, there is a possible solution:
    Install SQL on a secondary drive(if able) that is separate physical disk from the system's C: drive, creating a VHD to use for the SQL Server installation, or enabling TF1800. There are additional documentation updates planned to provide more information regarding this scenario."

    1 person found this answer helpful.

  3. LPI 6 Reputation points
    2022-05-22T15:24:43.237+00:00

    I have the same error and until now i cann't resolve the issue ....please help me !!!

    1 person found this answer helpful.

  4. Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator
    2022-01-30T11:19:34.49+00:00

    This error means that SQL Server did not start when Setup wanted to run installation scripts.

    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, assuming a default installation.

    Which operating system do you have?


  5. Erland Sommarskog 121.4K Reputation points MVP Volunteer Moderator
    2022-01-30T19:16:54.973+00:00

    Yes, you should make a second attempt to install to inspect the erorlog. If you see message about falling back to synchronous I/O after misaligned reads, there is no need to come back. There is a known issue with Windows 11 reporting incorrect sector sizes for some disks, and this article from Microsoft discusses how to deal with this: https://learn.microsoft.com/troubleshoot/sql/admin/troubleshoot-os-4kb-disk-sector-size.

    If you don't see anything about misaligned reads, share the errorlog here.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.