SQL Server does not allow remote connection Solution

For the database system that has just been installed, if it is installed by default, it is likely that an error is reported during remote connection. Generally, the error occurs: When you connect to SQLServer2005, by default, SQLServer does not allow remote connection, which may cause this failure. (Provider: named pipeline provider, error: 40

For the database system that has just been installed, if it is installed by default, it is likely that an error is reported during remote connection. This is usually an error: "When connecting to SQL Server 2005, this failure may occur if SQL Server does not allow remote connection by default. (Provider: named pipeline provider, error: 40-unable to open SQL

The database system that has just been installed is installed by default.ProceedRemoteConnectionAn error is reported. It is usually an error: "InConnectionTo SQL Server 2005, SQL Server does notAllowProceedRemoteConnectionThis failure may occur.

(Provider: named pipeline provider, error: 40-unable to open to SQL ServerConnection) ", Which is summarized as follows:

I understand that SQL Server is a network database and can be easily solved. It is simply divided into the following situations.

◆ 1. The database engine is not started. There are two startup methods:

(1) Start-> Program-> Microsoft SQL Server 2005-> SQL Server 2005 peripheral application configurator, click "ServiceConnectionIn the left-side Navigation Pane, find the Database Engine on the displayed page, and click "service" to check whether the service has been started. If not, click "start ", make sure that the "Start type" is automatic and not manual. Otherwise, you need to manually start the instance the next time you start the instance;

(2) You can choose Start> program> Microsoft SQL Server 2005> Configuration tool> SQL Server Configuration Manager, and select SQL Server (MSSQLSERVER) in SQL Server 2005 ), click "Start Service" in the toolbar to change the service status to start;

When using the above two methods, sometimes an error may occur during startup, and cannot be started, in this case, check whether the VIA in SQL Server 2005 network configuration> MSSQLSERVER protocol is enabled in "SQL Server 2005 Configuration Manager". If yes, disable it. then, execute the preceding operation.

◆ 2. whether it has beenAllowRemoteConnection. This part can be simply divided into four aspects: Enabling on SQL ServerRemoteConnectionEnable the SQL Server browsing service, create exceptions for SQL Server 2005 in Windows Firewall, and create exceptions for "SQLBrowser" in Windows Firewall. The following are some specific operations:

Enable on SQLServer instanceRemoteConnection

◆ 1. Point to "start-> Program-> Microsoft SQL Server 2005-> Configuration tool-> SQL Server peripheral application configurator"

◆ 2. On the "SQL Server 2005 peripheral application configurator" page, click "service andConnectionPeripheral application configurator"

◆ 3. Click to expand "Database Engine" and select"RemoteConnection", Select" local "on the rightConnectionAndRemoteConnection",

Select the Protocol to use (TCP/IP and named pipe service should be enabled here !) Click "application" and you will see the following message:

"Until the Database Engine service is restartedConnectionThe changes made by the settings take effect .", Click OK to return

◆ 4. Expand "Database Engine", select "service", click "stop" on the right side, and wait until the MSSQLSERVER service is stopped,

Click Start to restart the MSSQLSERVER service.

Enable SQLServer Browser Service

◆ 1. Point to "start-> Program-> Microsoft SQL Server 2005-> Configuration tool-> SQL Server peripheral application configurator"

◆ 2. On the "SQL Server 2005 peripheral application configurator" page, click "service andConnectionPeripheral application configurator"

◆ 3. Click to expand "SQL Server Browser", select "service", and select "automatic" in "Startup Type" on the right ",

Click Start and then click OK to return

Create an exception for "SQL Server 2005" in Windows Firewall

◆ 1. on the Windows Firewall settings page, select the "exceptions" tab and click "add program"

◆ 2. In the "add program window", click "Browse"

◆ 3. Then find "C: \ ProgramFiles \ Microsoft Files \ Microsoft SQL Server \ MSSQL.1 \ MSSQL \ Binn \ sqlservr.exe ",

Click OK to return

Note: the path may vary depending on SQL Server 2005 installation. MSSQL.1 is a placeholder that corresponds to the database instance ID.

◆ 4. Open eachRemoteTo access the SQL Server 2005 instance, repeat steps 1 to 3.

Create an exception for "SQLBrowser" in Windows Firewall

◆ 1. on the Windows Firewall settings page, select the "exceptions" tab and click "add program"

◆ 2. In the "add program window", click "Browse"

◆ 3. Then find "C: \ ProgramFiles \ Microsoft Files \ Microsoft SQL Server \ 90 \ Shared \ sqlbrowser.exe ",

Click OK to return

Note: the path may vary depending on SQL Server 2005 installation. Developing with. NETProceedInConnectionStringConnectionSQL Server 2005 databases can use both the machine name and localhostConnectionBut the IP address cannot be used.ConnectionProblems,SolutionOfSolutionEnable local andRemoteConnectionAnd use the TCP/IP and named pipe service when selecting the protocol.Solution

Author: