MS SQL SERVER 2022 ERROR IN INSTALLATION error code: 0x851A001A

Question

Hello ;

Windows 11 X64 installed MS 2022 Developer edition failed ?

Edisyon Windows 11 Pro

Sürüm 22H2

Yüklenme tarihi ‎27.‎02.‎2023

İS derlemesi 22621.1344

Deneyim Windows Feature Experience Pack 1000.22639.1000.0

---

Hata demeti 1361902955057764703, tür 5

Olay Adı: SQL160Exception

Yanıt: Kullanılamıyor

Kabin Kimliği: 0

Sorun imzası:

P1: SQL Server 2022@RTM@

P2: 0xD15B4EB2

P3: 0xD15B4EB2

P4: 0x4BDAF9BA@1306@26

P5: 0x4BDAF9BA@1306@26

P6: SqlEngineDBStartConfigAction_install_configrc

P7: 0x9C5770A6

P8: Unknown

P9: Unknown

P10:

İliştirilmiş dosyalar:

\?\C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log\20230305_205743\Watson_1\LogFiles.cab

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.37ff37fc-1beb-4e2e-8856-be62546458c7.tmp.WERInternalMetadata.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.83447bbc-b38b-4ef3-97e0-da7d843d4c5d.tmp.csv

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a14dbb0a-ff8b-4968-8461-ccecb597ccd5.tmp.txt

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1b17a496-f2dc-4647-938b-3ffb36602e7b.tmp.xml

Bu dosyalar burada bulunabilir:

\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_SQL Server 2022@_5452a46cca9d422895717b41badb309fb0e0f67b_00000000_818a61f9-fdbb-4bea-9f10-5c079cc4f952

Çözümleme simgesi:

Çözüm için yeniden denetleme: 0

Rapor Kimliği: 818a61f9-fdbb-4bea-9f10-5c079cc4f952

Rapor Durumu: 268435456

Karma demeti: 9c796c9d7933047fd2e673859ec5d95f

Kabin Guid'i: 0

Answer 1

I see this: " Wait on the Database Engine recovery handle failed." This is a generic message that means that SQL Server did not start when Setup needed to run configuration actions. There are multiple reasons why this can happen.

To find out why it does not start, you need to check the SQL Server errorlog, which you find in C:\Program Files\Microsoft SQL Server\MSSQL16.DATASRV\MSSQL\LOG\ERRRORLOG.

If you see a message about 256 misaligned reads, you are running into a known issue. Microsoft has published this article with workarounds.

Answer 2

the solution to the problem is here;

Registry Editor

1. Navigate to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device.
2. On the Edit menu, point to New, and then select Multi-String value. Name it ForcedPhysicalSectorSizeInBytes.
3. Modify the new value, type in * 4095. Click OK and close the Registry editor.

Command Prompt as Administrator

1. Add the key. Console
2. 1. REG ADD "HKLM\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" /v "ForcedPhysicalSectorSizeInBytes" /t REG_MULTI_SZ /d "* 4095" /f

Link :

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