Cannot install SQL Server 2019

Question

I'm trying to install SSIS (https://learn.microsoft.com/en-us/sql/integration-services/install-windows/install-integration-services?view=sql-server-ver15). I need SQL Server and download the developer free edition. At around 90% progress bar I am greeted with this error:

Wait on Database Engine recovery handle failed. Check the SQL server error log for potential causes.   

I tried to uninstall SQL Server 2019 and re-install 3x times and I get the same error each time.

@Olaf Helper , thanks for repsonse. I did follow the instructions, however it simply referred to what I already tried, that is, uninstalling and re-installing. I looked at the log files as suggested in the article if uninstall/re-install didn't work, and this is the error section:

Server local connection provider failed to listen on [ \.\pipe\sql\query ]. Error: 0x50
2020-12-17 09:00:50.77 spid31s Error: 17182, Severity: 16, State: 1.
2020-12-17 09:00:50.77 spid31s TDSSNIClient initialization failed with error 0x50, status code 0x50. Reason: Unable to initialize the Named Pipes listener. The file exists.
2020-12-17 09:00:50.77 spid31s Error: 17182, Severity: 16, State: 1.
2020-12-17 09:00:50.77 spid31s TDSSNIClient initialization failed with error 0x50, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The file exists.
2020-12-17 09:00:50.78 spid31s Error: 17826, Severity: 18, State: 3.
2020-12-17 09:00:50.78 spid31s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2020-12-17 09:00:50.78 spid31s Error: 17120, Severity: 16, State: 1.
2020-12-17 09:00:50.78 spid31s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the operating system error log for information about possible related problems.

I found this website (https://blog.sqlauthority.com/2016/05/11/sql-server-unable-to-start-sql-server-tdssniclient-initialization-failed-with-error-0xd/) and 'Enabled TCP/IP' in Configuration Manager, but it still doesn't work. Anything else I should try? Greatly appreciate your response. Thanks.

Answer 1

Hi @Spencer Trinh ,

Server local connection provider failed to listen on [ .\pipe\sql\query ]. Error: 0x50

You can try to modify the pipe name in the SQL Server Configuration Manager-> SQL Server Network Configuration->Protocols for instance->Named Pipes Properties->Pipe name. For example, you can try to modify to \.\pipe\sql\query1.

And try to change the SQL Server Service account to Local system in the SQL Server Configuration Manager->SQL Server Services->SQL Server instance properties->log on tab.

Please refer to this article which could help.
Best Regards,
Amelia

---

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Wait on Database Engine recovery handle failed. Check the SQL server error log for potential causes.

See Microsoft Wiki: SQL Server Troubleshooting: Could Not Find Database Engine Startup Handle Error During installation

And do what the error message suggest: View and Read SQL Server Setup Log Files

Answer 3

Often these errors indicates a problem with default profile in Windows, but I don't think this is the case here. After all it says:

Unable to initialize the Named Pipes listener. The file exists.

Why the named pipe would already exist, I don't know. Do you have any other SQL Server instances on this machine?

The blog post you found on Pinal's site relates to a different error code, so it is not applicable.

I found this blog post: https://techcommunity.microsoft.com/t5/sql-server/tdssniclient-initialization-failed-with-error-0x50-status-code/ba-p/383222 I am not sure how helpful it is, but have a look at it.

Answer 4

Hi @Erland Sommarskog , there actually is a SQL Server 2017 running due to another software requirement (Hamilton Venus). The PipeName for that instance is .\pipe\sql\query. So I'm guessing there is a PipeName conflict? How can I change it for 2019?

I would try to simply stop the SQL 2017 instance, or at least disable named pipes for that instance. (A restart is needed for it to take effect.) Once SQL 2019 is installed, you can make sure that named pipes are not active for SQL 2019, and you can restore it for SQL 2017. This is some special case where named pipes are needed during the installation.

Amelia suggested changing the name of the named pipe in SQL Server Configuration Manager, and that could work for the SQL 2017 instance. I am not sure if this would work with the SQL 2019 instance, though, since this occurs during Setup. I am not sure that the setting in SSCM would be respected. But this is a situation I've never been in, so I don't know.

Amelia also suggested changing the service account. Don't do that, but keep the default suggested by Setup.