Solution to SQL Server request failure problem

SQL2005 Unable to start SQL Server request failed or service not responding in time

Deactivate the VIA protocol to resolve the problem. Via protocol Deactivation Method: Start-> program->microsoft SQL Server 2005-> Configuration Tool->sql Server Configuration Manager-> to find SQL Server 2005 Network Configuration->mssqlserver the protocol in the right property box to disable the VIA protocol!

Why the request failed to start SQL Server Configuration Manager or the service did not respond in a timely manner

Solution:

Deactivate the VIA protocol to resolve the problem. Via protocol Deactivation Method: Start-> program->microsoft SQL Server 2005-> Configuration Tool->sql Server Configuration Manager-> to find SQL Server 2005 Network Configuration->mssqlserver the protocol in the right property box to disable the VIA protocol!

You check its log to see if there is such a word in the middle,

The file "C:Program FilesMicrosoft SQL servermssql.1mssqldatamastlog.ldf" has been compressed, but it does not reside in a read-only database or filegroup. This file must be uncompressed.

If so, you will be the right key to the SQL folder properties, select Advanced, in the appearance of the interface "compressed content in order to save disk space" option, OK on the line

Resolving SQL Server does not allow remote connectivity issues

The database system just installed, by default, is likely to be a remote connection times wrong, usually error: "When connecting to SQL Server 2005, the default setting for SQL Server to disallow remote connections may cause this failure." (provider: Named pipe provider, error:40-cannot open a connection to SQL Server) , now summarize the issue as follows:

Understand that SQL Server is a network database can be solved, simple to be divided into the following several situations.

1. The database engine did not start. There are two ways to start:

(1) Start-> program->microsoft SQL Server 2005->SQL Server 2005 peripheral configuration, click on the "Perimeter of Service Connection Configuration" in an open interface, and locate the database in an open interface Engine, click Services, see if it is started on the right, or click "Start" if it is not started, and make sure the "Startup Type" is automatic, not manual, otherwise start manually on the next boot;

(2) Open: Start-> program->microsoft SQL Server 2005-> Configuration Tool->sql Server Configuration Manager, select SQL Server 2005 Service Server (MSSQLServer) and click the "Start Service" button in the toolbar to change the service status to start;

When you use both of these methods, sometimes you may get an error at startup, and you will need to see if via is enabled in the SQL Server 2005 Network Configuration->mssqlserver protocol in SQL Server 2005 Configuration Manager. If enabled, disable it. And then do one of these things.

2. Whether remote connections have been allowed. This section can be easily divided into 4 areas, namely, enabling remote connections on SQL Server, enabling SQL Server Browsing service, creating exceptions for SQL Server 2005 in Windows Firewall, and "SQLBrowser" in Windows Firewall Create an exception. Here are a few specific ways to operate:

Enable remote connections on a SQL Server instance

1. Point to start-> program->microsoft SQL Server 2005-> Configuration tool->sql Server perimeter Application Configurator

2. On the SQL Server 2005 Perimeter Configuration page, click the perimeter application configurator for services and connections

3. Then click to expand Database engine, select remote connections, and on the right, select local and remote connections.

Then select the protocol you want to use (this place should enable TCP/IP and named pipe services!) Click Apply, and you will see the following message:

"The changes to the connection settings will not take effect until the Database engine service is restarted. ", click OK to return

4. Expand the database engine, select Services, click Stop on the right, and wait until the MSSQLServer service stops,

Then click Start to restart the MSSQLServer service.

Enable SQL Server Browser service

1. Point to start-> program->microsoft SQL Server 2005-> Configuration tool->sql Server perimeter Application Configurator

2. On the SQL Server 2005 Perimeter Configuration page, click the perimeter application configurator for services and connections

3. Then click Expand SQL Server Browser, select Services, and on the right "startup type" select "Automatic",

Click Start, and then click OK to return

Create an exception for SQL Server 2005 in Windows Firewall

1. In the Windows firewall settings interface, select the Exceptions tab, and then click Add Program

2. In the Add Program window, click Browse

3. Then find "C:programfilesmicrosoft filesmicrosoft SQL Server mssql.1 MSSQLBinnsqlservr.exe",

Click OK to return to the

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

4. Repeat steps 1 through 3 for each instance of SQL Server 2005 that requires open remote access.

Create an exception for "SQLBrowser" in Windows Firewall

1. In the Windows firewall settings interface, select the Exceptions tab, and then click Add Program

2. In the Add Program window, click Browse

3. Then find "C:programfilesmicrosoft filesmicrosoft SQL Server90Sharedsqlbrowser.exe",

Click OK to return to the

Note: The path may vary depending on the SQL Server 2005 installation. In use. NET development, you will encounter using a connection string to connect to a SQL Server 2005 database using both machine name and localhost, but you cannot connect using an IP address, the workaround is to enable local and remote connections on the SQL Server instance. And can be resolved using TCP/IP and named pipe services when choosing a protocol.

When you try to connect to a Microsoft SQL Server 2005 instance from a remote computer, you may receive an error message. This problem may occur when you connect to SQL Server using any program. For example, when you use the SQLCMD utility to connect to SQL Server, you receive the following error message:

Sqlcmd: Error: Microsoft SQL Native Client: An error occurred while establishing a connection to the server. When connecting to SQL Server 2005, default settings SQL Server does not allow remote connections This fact may cause failure.

This problem may occur if SQL Server 2005 is not configured to accept remote connections. By default, remote connections are not allowed by SQL Server Edition Express and SQL Server Developer Edition. To configure SQL Server 2005 to allow remote connections, complete the following steps:

· Enable remote connections on the instance of SQL Server to which you want to connect from a remote computer.

· Open the SQL Server Browser service.

· Configure the firewall to allow network traffic associated with SQL Server and SQL Server Browser services.

This article describes how to complete each step of these steps.

To enable remote connections on a SQL Server 2005 instance and open the SQL Server Browser service, use the SQL Server 2005 perimeter Configuration tool. The Perimeter Application Configurator tool is installed when SQL Server 2005 is installed. Enable remote connections for SQL Server Edition Express or SQL Server Developer Edition

You must enable remote connections for each instance of SQL Server 2005 that you want to connect to from a remote computer. To do this, follow these steps:

1. Click Start, point to Programs, Microsoft SQL Server 2005, and configure tools, and then click SQL Server Perimeter Application configurator.

2. On the SQL Server 2005 Perimeter Configuration page, click the perimeter application configurator for services and connections.

3. On the perimeter application configurator for services and Connections page, expand Database engine, click Remote Connections and then connect to local and remote connections, click the appropriate protocol for your environment, and then click Apply.

Note: Please click OK when you receive the following message:

Changes to connection settings do not take effect until the Database engine service is restarted.

4. On the perimeter application configurator for services and Connections page, expand Database engine, click Services and stop, wait for the MSSQLServer service to stop, and then click Start to restart the MSSQLServer service.

Enable SQL Server Browser Service

If you are running SQL Server 2005 by using an instance name and you do not use a specific TCP/IP port number in the connection string, you must enable the SQL Server Browser service to allow remote connections. For example, SQL Server Express is installed using the default instance name of the < computer name >sqlexpress. No matter how many instances of SQL Server 2005 you are running, you only need to enable the SQL Server Browser service once. To enable the SQL Server Browser service, follow these steps.

When you connect to SQL Server 2005, this failure may be caused by SQL Server not allowing remote connections under the default settings. (provider: Named pipe provider, error:40-cannot open a connection to SQL Server)

SQL Server 2005 does not allow remote connection resolution

Many students encountered this problem when they were doing the course design. Write the solution here for your reference.

The database system just installed, by default, is likely to be a remote connection times wrong, usually error: "When connecting to SQL Server 2005, the default setting for SQL Server to disallow remote connections may cause this failure." (provider: Named pipe provider, error:40-cannot open a connection to SQL Server) "Search MSDN, there is a machine translation of the article, is difficult to understand, now summed up as follows:" Understand that SQL Server is a network database can be solved, simple to be divided into the following concentration.

1. The database engine did not start.

There are two ways to start:

(1) Start-> program->microsoft SQL Server 2005->SQL Server 2005 peripheral configuration, click on the "Perimeter of Service Connection Configuration" in an open interface, and locate the database in an open interface Engine, click Services, see if it is started on the right, or click "Start" if it is not started, and make sure the "Startup Type" is automatic, not manual, otherwise start manually on the next boot;

(2) Open: Start-> program->microsoft SQL Server 2005-> Configuration Tool->sql Server Configuration Manager, select SQL Server 2005 Service Server (MSSQLServer) and click the "Start Service" button in the toolbar to change the service status to start;

When you use both of these methods, sometimes you may get an error at startup, and you will need to see if via is enabled in the SQL Server 2005 Network Configuration->mssqlserver protocol in SQL Server 2005 Configuration Manager. If enabled, disable it. And then do one of these things.

2. Whether remote connections have been allowed.

This section can be easily divided into 4 areas, namely, enabling remote connections on SQL Server, enabling SQL Server Browsing service, creating exceptions for SQL Server 2005 in Windows Firewall, and "SQLBrowser" in Windows Firewall Create an exception. Here are a few specific ways to do this, excerpted from MSDN, and personally feel that the bold part of the article should be special together with our attention.

Enable remote connections on a SQL Server instance

1. Point to start-> program->microsoft SQL Server 2005-> Configuration tool->sql Server perimeter Application Configurator

2. On the SQL Server 2005 Perimeter Configuration page, click the perimeter application configurator for services and connections

3. Then click to expand Database engine, select remote connections, and on the right, select local and remote connections.

Then select the protocol you want to use (this place should enable TCP/IP and named pipe services!) Click Apply, and you will see the following message:

"The changes to the connection settings will not take effect until the Database engine service is restarted. ", click OK to return

4. Expand the database engine, select Services, click Stop on the right, and wait until the MSSQLServer service stops,

Then click Start to restart the MSSQLServer service.

Enable SQL Server Browser service

1. Point to start-> program->microsoft SQL Server 2005-> Configuration tool->sql Server perimeter Application Configurator

2. On the SQL Server 2005 Perimeter Configuration page, click the perimeter application configurator for services and connections

3. Then click Expand SQL Server Browser, select Services, and on the right "startup type" select "Automatic",

Click Start, and then click OK to return

Create an exception for SQL Server 2005 in Windows Firewall

1. In the Windows firewall settings interface, select the Exceptions tab, and then click Add Program

2. In the Add Program window, click Browse

3. Then locate the C:programfilesmicrosoft filesmicrosoft SQL Server MSSQL.1 Mssqlbinn