SQL Server 2019 installation error on windows 11 with error "Could not find the database engine startup handle"

Question

question

AbhishekSingh-6932 asked May 13, '22 ErlandSommarskog commented May 14, '22

SQL Server 2019 installation error on windows 11 with error "Could not find the database engine startup handle"

I am trying to install SQL server 2019 on windows 11. But the installation always gets stuck on SQLEngineDBStartConfigAction_install_configrc_Cpu64

Then after some time it shows an error: -

I have tried everything from completely uninstalling, to changing rights, installing in a VHD, etc. but its not getting resolved. I am in urgent need of SQL server.
Attaching log file below:-

201630-log.txt

sql-server-general

screenshot-670.png (1.2 MiB)

screenshot-671.png (1.1 MiB)

screenshot-672.png (1.1 MiB)

log.txt (11.0 KiB)

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 1 · 2022-05-13T21:15:34.753Z

ErlandSommarskog answered May 13, '22 ErlandSommarskog commented May 14, '22

That was not the file I was asking for. However, the file you attached (and which I failed to observe when I read your first post, my apologies) explains why your setup fails.

You are victim for a bug in the Setup wizard. When your Windows locale is Hindi (India), the Setup Wizard will select Indic_General_90_CI_AS as the default collation. But this collation is not valid as a server or database collation. When you run the Setup wizard and you come to the Server Configuration page, go to the the Collation tab. Click the Change button. You can exit directly. That page knows that the collation above is not permitted, and will change the collation to Indic_General_90_CI_AS_SC_UTF8 which is legal. You can also make any other selection you may prefer.

As for that file I asked you to look at - don't look for it. With this particular error, you never get that file. (Most of the time when people get the error about the start up handle, there is a file, as SQL Server starts and stops. But in this case, SQL Server refuses to start due to the bad collation.)

· 2

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AbhishekSingh-6932 · May 14 at 08:14 AM

Thank you very much, SQL server is finally installed after so much struggle. Saved me many hours. Thanks once again

0 ·

ErlandSommarskog AbhishekSingh-6932 · May 14 at 08:23 AM

By the way, I have reported this as a bug, which you can vote for here: https://feedback.azure.com/d365community/idea/b50d5511-d9c7-ec11-a81b-6045bd796569.

0 ·

Answer 2 · 2022-05-13T08:45:39.593Z

OlafHelper-2800 answered May 13, '22 AbhishekSingh-6932 commented May 13, '22

See https://social.technet.microsoft.com/wiki/contents/articles/24364.sql-server-troubleshooting-could-not-find-database-engine-startup-handle-error-during-installation.aspx for details

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AbhishekSingh-6932 · May 13 at 10:10 AM

As I told I have tried everything. I already followed the same link that you have provided with no result, still the same error.

0 ·

Answer 3 · 2022-05-13T21:01:02.453Z

ErlandSommarskog answered May 13, '22 AbhishekSingh-6932 commented May 13, '22

This error means that SQL Server did not start when Setup wanted to run installation scripts. To find out why SQL Server did not start, check the SQL Server errorlog, which you find in C:\Program Files\Micrisoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\LOG\ERRORLOG. Note that the exact path depends on your installation options, so may need to modify it.

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AbhishekSingh-6932 · May 13 at 09:07 PM

I have attached the log file in the question itself. Attaching it here also.
[201893-log.txt][1]

Can you please check and investigate the issue?
[1]: /answers/storage/attachments/201893-log.txt

0 ·

log.txt (11.0 KiB)

question