Resolving “No Process is on the Other End of the Pipe” Error in SQL Server

While connecting to SQL Server 2008, you may encounter the error “Named Pipes Provider: No process is on the other end of the pipe.”

A common reason for this error is possibly that named pipes are not enabled on your server or the Named Pipes protocol is listed before TCP as shown below (Observe the Order):

To resolve this error, you can change the order in the Client Protocol Order as shown below:

Go to Start > All programs > SQL Server 2005/2008 > Configuration Tools > SQL Server Configuration Manager. Expand the SQL Native Client Configuration Node > Client Protocols

Now right click on the TCP/IP protocol > choose ‘Order’ and bring TCP/IP up in the client protocol order as shown below:

If the error still does not get resolved, use the same Configuration Management tool to make sure that the named pipes protocol is enabled.

Did you like this post?

	subscribe via rss		subscribe via e-mail
	print this post		follow me on twitter

Feedback: