Error Message: (Provider: Shared Memory Provider, Error: 0 - No Process Is on the Other End of the Pipe.)

Error message: (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)

Typically, to troubleshoot this, you go to SQL Server Configuration Manager (SSCM) and:

  1. ensure Shared Memory protocol is enabled
  2. ensure Named Pipes protocol is enabled
  3. ensure TCP/IP is enabled, and is ahead of the Named Pipes in the settings

Maybe it can help: Could not open a connection to SQL Server

Note : If this is a new instance of SQL Server be sure SQL Server and Windows Authentication is enabled

  1. Right Click the Server in SSMS and pull up server properties
  2. Go to Security--> Select 'SQL Server and Windows Authentication Mode'
  3. Restart the Server and Login with the credentials

No process is on the other end of the pipe (SQL Server 2012)

The server was set to Windows Authentication only by default. There isn't any notification, that the origin of the errors is that, so it's hard to figure it out. The SQL Management studio does not warn you, even if you create a user with SQL Authentication only.

So the answer is: Switch from Windows to SQL Authentication:

  1. Right click on the server name and select properties;
  2. Select security tab;
  3. Enable the SQL Server and Windows Authentication mode;
  4. Restart the SQL Server service.

You can now connect with your login/password.

Here are the directions by Microsoft: https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/change-server-authentication-mode?view=sql-server-ver15

A connection was successfully established with the server, but then an error occurred during the login process. (Error Number: 233)

Turn out to be some SQL service was stopped somehow on server. Restarting SQL Server service manually was the solution.

Error: No process is on the other end of the pipe

I would start by checking the consistency of your data. Run a DBCC CheckDB against your DB. You may have corruption in the table. You can also try selecting against msdb.dbo.suspect_pages

No Process Is on the Other End of the Pipe

I tried the troubleshooting steps in both microsoft tech articles, and oddly no luck.

I managed to fix the solution by changing my authentication from SQL Server Auth to Windows Auth. Though I am not sure the technical reason why this works?

SQL Server 2008 Connection Error No process is on the other end of the pipe

To force TCP/IP being used replace localhost with 127.0.0.1 in your connection string.

As you are using a username and password make sure SQL authentication is enabled. By default only Windows integrated is enabled on sqlserver 2008.

With SqlServer authentication keep in mind that a password policy is in place to enforce security.



Related Topics



Leave a reply



Submit