SQL Server Error: No Process is on the Other End of the Pipe
2008-05-09 19:20
686 查看
当登录SQL Server 2005时可能碰到错误: 'No Process is on the Other End of the Pipe'。解决方法:
(1)Open up SQL Server Suraface Area Configuration tool by clicking
Start > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Suraface Area Configuration
(2)Click the Surface Area Configuration for Services and Connections link at the bottom of the window.
(3)In the View By Instance pane on the left, expand the node for the SQL Server that is giving you the error, and
click the Database Engine > Service > Remote Connections.
(4)In the setting for the Remote Connections, click the Local and Remote Connections option.
Now click the Using both TCP/IP and named pipes option and click OK.
You will be prompted to restart your Database Server for the changes to take effect. Do that.
Once you restart your Database Server, you should be able to login to the SQL Server database successfully !
No Process is on the Other End of the Pipe
错误提示:
Named Pipes Provider: No process is on the other end of the pipe.
Microsoft SQL Native Client : Communication link failure.
Microsoft SQL Native Client : An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
典型原因和解决方法:
from: http://theshiva.us/technicalblog/archive/2006/12/20/solution-fix-no-process-is-on-the-other-end-of-the-pipe-error-sql-server-2005.aspx
from: http://technet.microsoft.com/en-us/library/ms175496.aspx
(1)Open up SQL Server Suraface Area Configuration tool by clicking
Start > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Suraface Area Configuration
(2)Click the Surface Area Configuration for Services and Connections link at the bottom of the window.
(3)In the View By Instance pane on the left, expand the node for the SQL Server that is giving you the error, and
click the Database Engine > Service > Remote Connections.
(4)In the setting for the Remote Connections, click the Local and Remote Connections option.
Now click the Using both TCP/IP and named pipes option and click OK.
You will be prompted to restart your Database Server for the changes to take effect. Do that.
Once you restart your Database Server, you should be able to login to the SQL Server database successfully !
No Process is on the Other End of the Pipe
错误提示:
Named Pipes Provider: No process is on the other end of the pipe.
Microsoft SQL Native Client : Communication link failure.
Microsoft SQL Native Client : An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
典型原因和解决方法:
Cause | Resolution |
---|---|
The client is attempting to connect using named pipes, and the server is not configured to allow remote connections using named pipes. | Connect using TCP/IP, or use the Surface Area Configuration tool to enable remote connections using named pipes. |
The client protocol order is attempting to connect with the named pipes protocol before trying the TCP protocol, and named pipes are not enabled on the server. | Using SQL Server Configuration Manager on the client computer, move TCP before named pipes in the protocol order list. |
from: http://technet.microsoft.com/en-us/library/ms175496.aspx
相关文章推荐
- WCF error "No end point listening at net.pipe://server name:port/service name that could accept the message
- SQL Server数据库恢复错误 The media family on device ‘%ls’ is incorrectly formed. SQL Server cannot process this media family
- [Java]Error:No enclosing instance of type E is accessible. Must qualify the allocation with an enclo
- Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection
- Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance
- JAVA+ Proxool+ SQLserver 2008 “signer information does not match signer information of other classes in the same package”
- Login failed for user 'sa'. Reason: The account is disabled. (Microsoft SQL Server, Error: 18470)
- Unable to use SQL Server because ASP.NET version 2.0 Session State is not installed on the SQL serve
- Sharepoint Error: "This server is not the indexer of this search application"
- Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection
- Unable to start debugging on the web server. The IIS worker process for the launched URL is not currently running
- Error: The version of SQL Server in use does not support datatype 'datetime2'
- [转]How to find who is using / eating up the Virtual Address Space on your SQL Server
- The connection to adb is down, and a severe error has occured.adb server is out of date. killing...
- Steps to change the default location of SQL Server /SQL Server Agent - Error log files
- Error: The version of SQL Server in use does not support datatype 'datetime2
- Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.
- [原]openstack-kilo--issue(十九) ImportError: Could not import settings 'openstack_dashboard.settings' (Is it on sys.path? Is there an import error in the settings file?): No module named main
- sql express 2008 - Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instan
- ASP.Net DebugError解决方案[转]:Unable to start debugging on the web server.Debugging failes because integrated Windows authentication is not enabled.