Unable to install Microsoft SQL

Question

I get this message: Unable to install SQL server (setup.exe) Exit code decimal -2061893606 Error description: wait on the database engine recovery handle failed I'm attaching the SQLDUMPER_ERRORLOG.log

Answer 1

Hi There, please try the following,

1. Clean the failed SQL Server installation: Uninstall all instances of SQL Server from your system1. You can do this by going to the Control Panel, selecting “Uninstall a program”, finding “Microsoft SQL Server (64 bit)”, selecting the “Remove” option, and following the prompts to uninstall the instance. Repeat this process until all instances are uninstalled1. Change the Account Name of Database Engine Service: When you run the setup file as an administrator and reach the Server Configuration Screen, change the Account Name of the Database Engine Service to NT AUTHORITY\NETWORK SERVICE2. This should allow you to successfully install all components without any error2. Check the SQL Server error log: The error log might contain more details about what’s causing the issue2. You can find the SQL Server error log in C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\LOG\ERRORLOG, assuming a default installation2. Registry Editor: Navigate to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device. On the Edit menu, point to New, and then select Multi-String value. Name it ForcedPhysicalSectorSizeInBytes. Modify the new value, type in * 4095. Click OK and close the Registry editor3.

Answer 2

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\MSSQL16.MSSQLSERVER\MSSQL\LOG\ERRORLOG. Note that the component MSSQL16.MSSQLSERVER is for a default instance of SQL 2022. If you are trying to install an older version or a named instance, this component will have a different name.

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.