Windows could not start the SQL Server service on local computer 17051: A network-related or instance-specific error occurred while establishing a connection to SQL Server

In this article, we shall learn how to resolve “Windows could not start the SQL Server service on local computer 17051: A network-related or instance-specific error occurred while establishing a connection to SQL Server”. The SQL Server is a relational database management system from Microsoft. The system is designed and built is to manage and store information. Please see how to download and install Microsoft SQL Server 2019 Express edition and SSMS.

The system supports various business intelligence operations, analytics operations, and transaction processing. Also, see “BitLocker behavior when MBAM agent is removed: No Uninstall Option in Control Panel“.

Kindly refer to these related guides: How to use Software Licensing Management Tool (slmgr) to install and uninstall Windows product key, What are the differences between various Editions of Microsoft SQL Server, and how to install MSSQL Server 2019 Developer Edition and SSMS on Windows, and

Review SQL Server Services via Services Manager

The error originates from issues within the SQL Server service on the local computer. When you try to start the SQL Server service, the following error below will be prompted “Windows could not start the SQL Server service on local computer 17051”.

The SQL Server service on the local computer couldn’t start due to the expiration of the SQL Server Evaluation period.

Encountering an error while connecting to an SQL Instance via SSMS (SQL Server Management Studio)? If you face the message “SQL Server service on local computer” during this process, read on for solutions. 

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.

Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

We have been directed to also take a look at the Event Viewer. As you can see below, the error message from the Event Viewer with event ID 17051. This shows SQL Server Evaluation period has expired under the General section.

Here is the fix for “the server was not found or was not accessible: A network-related or instance-specific error occurred while establishing a connection to SQL Server“.

Solution

However, I’ve set up SQL Server service on the local computer in my lab using the 180-day Evaluation. As no Product Key was applied.

So, now how can you make it live again? Nonetheless, All you need is a Product key of SQL Server now.

See this guide for the fix “Microsoft SQL Evaluation period has expired: How to upgrade SQL Server instance“. Please refer to this guide on “how to upgrade MS SQL server instance edition”.

Since we are aware that the evaluation period has expired, please refer to these links {1} and {2} on how to upgrade your evaluation software.

Note: If this is not the case, to fix the “network-related or instance-specific error” when connecting to SQL Server. Ensure that the correct server name and database are specified in the connection string, and that SQL Server is running and accessible over the network. This was the case for SSMS v21 and not the services not running or the above error.

I hope you found this blogpost on “Windows could not start the SQL Server service on local computer 17051: A network-related or instance-specific error occurred while establishing a connection to SQL Server” helpful. Feel free to ask questions in the comments.