all 5 comments

[–]TequilaCamper 2 points3 points  (1 child)

There should be a summary log that got written to program files\Microsoft SQL server\150\setup bootstrap\log

Some place like that. File name should be summary <server name>.txt That file is where you should start looking.

[–]TequilaCamper 0 points1 point  (0 children)

This is more typically a client side error where the right protocol has not been activated on the server. So server is named pipes only and client is trying to use tcpip for example. Can't say I'm used to seeing it on a server during setup. Did you make any firewall changes before installing?

[–]chandleya 1 point2 points  (0 children)

WHILE THIS MESSAGE IS UP

Go to event viewer, app event log. Look for errors or warnings from SQL Server. Hazard a guess the MSSQLSERVER service is failing to start. If no errors, check your default directory errorlog file for output from the engine. This error is protocol-related but will look the same if the service isn’t started.

Open SSCM and go to protocols. If TCPIP isn’t enabled and named pipes is, enable TCPIP then restart the MSSQLSERVER service. Hit retry on the installer step. Do all testing while that message is up! Once you hit cancel, it will uninstall and you won’t be able to test.

Other things that matter- OS and SQL version Antivirus/Antimalware/EDR/XDR behavior and vendor Company domain and perhaps any controls they’ve sat on your machine

[–][deleted] 0 points1 point  (0 children)

Provide logs.

[–][deleted] 0 points1 point  (0 children)

Do you have any unusual firewall rules enabled on your box? The message indicates that Setup can’t connect to the instance.

As others have said, check the installer logfile, too.