SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,689 questions
Has anyone resolved the "Database Engine recovery handle failed" and "firewall warrnig" error during SQL Server installation on Windows 11?
Yogendra Dwivedi
20
Reputation points
I am encountering critical issues with installing both SQL Server 2017 or SQL Server 2022 on my Windows 11 Home (x64) machine. Below is a summary of the problems and the steps I have taken to resolve them:
Issue Summary:
- Warning: Firewall warning appeared in the initial phase of installation.
- Error: "Wait on the Database Engine recovery handle failed." - Component error code: 0x851A001A
- Failure: Database Engine Services failed to install.
- Occurrence: Same issues with SQL Server 2017 and SQL Server 2022.
Steps Taken to Resolve:
- Checked SQL Server Logs for more error details.
- Verified Permissions for NT Service\MSSQLSERVER to ensure directory access.
- Updated Windows to the latest version.
- Checked for Port Conflicts: Ensured no applications were using the default SQL Server port (1433).
- Cleaned Previous Installations: Uninstalled previous versions, deleted residual files, and cleaned registry entries.
- Disabled Antivirus and Firewall temporarily during installation.
- Re-downloaded SQL Server setups to ensure fresh, non-corrupted files.
- Contacted Microsoft Support twice: They suggested performing an in-place upgrade, which did not resolve the issue.
- Tried Registry Edit: Followed the process of setting
ForcedPhysicalSectorSizeInBytesin the registry, but the error persisted.
Solution from Microsoft Community:
- Repairing SQL Server Installation through the SQL Server Installation Center.
- Running
sfc /scannowto check for corrupted system files. - Manually Configuring the SQL Instance: Reinstall SQL Server with manual configuration to avoid port conflicts.
For more details, I have referred to their official troubleshooting guide: Microsoft SQL Server Troubleshooting Guide.
Despite these efforts, the issue persists. Given that this is a SQL Server-specific problem, I kindly request that this issue be escalated to a SQL Server expert or the relevant team who can provide further assistance.
{count} votes
-
Erland Sommarskog 110.4K Reputation points MVP2024-09-18T21:06:14.86+00:00 Given that this is a SQL Server-specific problem, I kindly request that this issue be escalated to a SQL Server expert or the relevant team who can provide further assistance.
I'm afraid that this is not the place where you can expect escalation. This is a peer-to-peer forum.
Warning: Firewall warning appeared in the initial phase of installation.
This is something you should ignore, particularly if you are installing on your home machine. The firewall can cause you trouble if you are trying to connect to the SQL Server instance from another machine. If you are only going to use SQL Server locally, the firewall will not matter.
Given that you are on Windows 11, my guess is that the root cause is the disk-sector issue which you tried to fix with the registry-edit. But if you have made many installation attempts and tried to clean up in between, you may have messed up your machine, so that it now fails on a different problem.
In any case, in the folder C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log, you find one folder per each installation attempt of SQL Server. The files of most interest are Summary.txt and detail.txt. Feel free to attach them here.
-
Yogendra Dwivedi 20 Reputation points
2024-09-19T08:39:49.3866667+00:00 please let me know what else with i can help you sir?
-
Yogendra Dwivedi 20 Reputation points
2024-09-19T11:48:57.33+00:00 thank you so much for the reply sir, i have attachted the summary.txt file please have a look and help to solve this. Also it's a request to please tell where should i go to find my solution which community will help me with this.
-
Erland Sommarskog 110.4K Reputation points MVP
2024-09-19T13:36:48.46+00:00 I can't see any file attached. Also, don't forget detail.txt. That is the most important file.
Unfortunately, it is difficult to get help with these install problems. We do our best, but since we don't have access to your machine, it is difficult to troubleshoot and understand why you get a certain error. But we'll see when get the log files.
Sign in to comment
Sign in to answer