SQL Server 2022 installation Failing with error "Wait on the Database Engine recovery handle"

Srikanth Lanka 46

I've been trying to install SQL Server 2022 on Windows 11 machine; I've tried multiple times and every time ended up with the error

275855-summary-srilakshmi-20230103-215638.txt

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.

For help, click: https://go.microsoft.com/fwlink?LinkID=2209051&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=16.0.1000.6&EvtType=0xD15B4EB2%25400x4BDAF9BA%25401306%254026

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

BUTTONS:

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

Followed the instructions in the link below, figured out that the value for PhysicalBytesPerSectorForAtomicity is = 4096, but for PhysicalBytesPerSectorForPerformance (I think this is okay to have it more than PhysicalBytesPerSectorForAtomicity ) and didn't make the recommended registry entry, is that entry still required ? Should the value for both PhysicalBytesPerSector need to be same ?

https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size

![275830-image.png][2] [2]: /api/attachments/275830-image.png?platform=QnA
275903-serverlog.txt

Erland Sommarskog 111.1K Reputation points MVP

2023-01-04T22:31:04.453+00:00

Did you check the SQL Server errorlog and verified that there was an error message about 256 misaligned reads?

The error message "Wait on the Database Engine recovery handle" is a generic error message which means that SQL Server did not start when Setup wanted to run configuration. There can be multiple reasons for this, of which one is the disk-sector issue discussed in the article you linked to.

But if that is not your problem, that registry fiddling is not going to help.

The errorlog is in C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\LOG\ERRORLOG.

If you do have the disk-sector issue, I cannot answer your question about PhysicalBytesPerSector. Thankfully, I have never had to battle this problem myself.
Srikanth Lanka 46 Reputation points

2023-01-05T05:21:53.953+00:00

Hi @Erland Sommarskog - Thanks for trying to help me. I see something like this in the logs that I found on the path that you mentioned, I'm guessing this what you meant. I'm attaching the log for reference.

2023-01-03 22:18:11.66 spid35s Starting up database 'master'.
2023-01-03 22:18:11.67 spid35s 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.
2023-01-03 22:18:11.67 spid35s Unable to create stack dump file due to stack shortage (ex_terminator - Last chance exception handling)
2023-01-03 22:18:11.67 spid35s Stack Signature for the dump is 0x0000000000000000

So, do I need to adjust the PhysicalBytesPerSectorForAtomicity to match PhysicalBytesPerSectorForPerformance value i.e., to 16kb as PhysicalBytesPerSectorForAtomicity this is already 4 kb. If this is what I need to do, will the below command takes care of it

REG ADD "HKLM\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" /v "ForcedPhysicalSectorSizeInBytes" /t REG_MULTI_SZ /d "* 16384" /f. Please advise.

276353-errorlog.txt
Erland Sommarskog 111.1K Reputation points MVP

2023-01-05T21:48:40.423+00:00

Correct, you are facing the disk-sector problem.

Unfortunately, I am in position to answer your question, as I never had to deal with this myself. But I have seen more than one poster who were able to resolve their problem with help of that article.
Viet Tran 0 Reputation points

2024-03-25T10:22:52.51+00:00

TITLE: Microsoft SQL Server 2022 Setup

The following error has occurred:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.

Help me, please
Erland Sommarskog 111.1K Reputation points MVP

2024-03-25T21:49:18.9433333+00:00

Help me, please

The way to ask questions in these forums is to use the button Ask a Question in the upper right corner.

Also, when asking a question, you should include context to your question. Only dumping an error message will only result in generic answers. That is, we need to know why you don't expect to get this error message.

Accepted answer

LiHongMSFT-4306 27,016 Reputation points

2023-01-04T07:32:12.327+00:00
Hi @Srikanth Lanka

Should the value for both PhysicalBytesPerSector need to be same ?

You'd better make them to be same.

To install SQL server on windows 11. Have you tried this:

Uninstall all the SQL instances one by one. Goto--control panel - uninstall a program - Microsoft SQL server (64 bit) - select remove option, select the particular instance, and uninstall

Repeat the same process till you uninstall all instances. Goto C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER (MSSQLSERVER indicates instances). Should not have any instances like this ex: MSSQL15.MSSQLSERVER.

Restart the computer and run as administrator choose basic installation process.

Best regards,
Li Hong
Please sign in to rate this answer.

2 people found this answer helpful.
Srikanth Lanka 46 Reputation points

2023-01-05T05:22:59.953+00:00

Hi @LiHongMSFT-4306

Thanks for trying to help me.

So, do I need to adjust the PhysicalBytesPerSectorForAtomicity to match PhysicalBytesPerSectorForPerformance value i.e., to 16kb as PhysicalBytesPerSectorForAtomicity this is already 4 kb. If this is what I need to do, will the below command takes care of it

REG ADD "HKLM\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" /v "ForcedPhysicalSectorSizeInBytes" /t REG_MULTI_SZ /d "* 16384" /f. Please advise.

Srikanth Lanka 46 Reputation points

2023-01-07T03:56:40.587+00:00

@LiHongMSFT-4306 - Thanks by setting both the PhysicalBytesPerSector to 4KB my issue resolved.

Damilare Solomon 0 Reputation points

2023-07-10T21:16:51.38+00:00

My physical bytes per sector aren't still the same. SQL 2022 still not installing. I have deleted all instances, used registry editor.
Sign in to comment

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

1 additional answer

Sergio Aguirre Romero 0 Reputation points

2023-08-12T21:18:31.72+00:00

https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size

This works for me.
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

SQL Server 2022 installation Failing with error "Wait on the Database Engine recovery handle"

1 additional answer

Your answer