SQL Server Login Failure - No Process Is on the Other End of the Pipe (Microsoft SQL Server, Error:233)

You may experience login failure preventing you from connecting to SQL Server for many possible reasons. Each reason is clearly mentioned at the login failure error message at the time you try to login. (Assuming you are using SQL Server Native Client Tool)

One of such possibility is your login attempt fails with below message:

A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 – No process is on the other End of the pipe.) (Microsoft SQL Server, Error:233)


Possibility 1: The client is attempting to connect with the named pipes protocol before trying the TCP protocol (because of the protocol order from client configuration) but named pipes are not enabled on the server.

Resolution: Move TCP before named pipes in the protocol order list on the client computer using SQL Server Configuration Manager.

Possibility 2: The client is attempting to connect using named pipes intentionally but the server is not configured to allow remote connections using named pipes.

Resolution: Advise client to use TCP/IP. If there is a valid reason to use Named Pipe protocol, then use
SQL Server Configuration Manager to enable remote connections using named pipes.


Valter Popeskic said…
Very nice and helpful work, congratulations

My blog about networking http://howdoesinternetwork.com it's writing about how exactly internet is working

and about all the network fundamentals.. Including TCP and all other most important protocols of different

OSI model layer.

Hope you will enjoy learning from it and help me with some comments and maybe suggestions.

Tom said…
This comment has been removed by a blog administrator.
UC said…
Hi Tom,

I removed your comment from this post and other 2 posts as they are just links with out any context or discussion relevant to the posts. Please let me know if you have any concern.