Network-related or instance-specific errors when establishing a connection to SQL Server

Tag: SQL Server establishes a connection when the network-specific instance of error 40

Error message:

Title: Connecting to the server------------------------------cannot connect to (local). ------------------------------Additional information: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or could not be accessed. Verify that the instance name is correct, and that SQL Server is configured to allow remote connections. (provider: Named pipe provider, ERROR:40-Unable to open connection to SQL Server) (Microsoft SQL Server, Error: 2) For help information, click: Http://go.microsoft.com/fwlink? prodname=microsoft+sql+server&evtsrc=mssqlserver&evtid=2&linkid=20476----------------------------- -Button: OK------------------------------

Background:

Today open SQL Server 2008 SQL Server Management Studio, enter the password discovery for SA, unable to log on to the database, prompting information such as:

Solution:

1. Open SQL Server Management Configurator

or enter at the command line: sqlservermanager10.msc

2. Click on the MSSQLSERVER protocol and select the TCP/IP protocol on the right page.

3, right click on the TCP/IP protocol, select "Properties", you need to modify the port address of the connection database

4, jump out of the dialog box, there are many TCP/IP ports, find "IP3", change the IP address for their own computer's IP address (or 127.0.0.1) on the TCP port add 1433, and then click Apply

5, modify the "IPALL" all the ports to "1433" (or this interface, pull down the scroll bar)

6. Restart the service

7, through the above 1-6 steps to set up a good port, reopen SQL Server Management Studio, the server name input: (local) or 127.0.0.1, you can log into the database.