Fixing Error 0: No process is on the other end of the pipe.

Zac Watkins 6 Reputation points
2020-08-18T16:55:09.007+00:00

Recently trying to work on some SSRS stuff with a local instance of my company Database, and I messed with number of allowed connections. Now attempting to connect to my local instance yields:

Microsoft SQL Server Management Studio


Cannot show requested dialog.


ADDITIONAL INFORMATION:

Failed to connect to server DESKTOP-68S3Q92. (Microsoft.SqlServer.ConnectionInfo)


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

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476


No process is on the other end of the pipe


Interestingly, if I restart my server from SQL Server Configuration Manager it will successfully connect, but then immediately give the same message, and prevent me from touching properties or anything else.

If anyone has some insight to the problem I would be most appreciative, I'm still pretty new at this SQL game.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,690 questions
{count} vote

7 answers

Sort by: Most helpful
  1. m 4,271 Reputation points
    2020-08-19T02:46:07.73+00:00

    Hi @Zac Watkins

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

    Enable TCP\IP protocol and then test it again.

    Steps as next:
    1 .Turn off your firewall and antivirus software;
    2. Enable the TCP\IP protocol both in server and client side and use 1433 port.
    3. Restart the SQL Service and try again.

    More detail steps :setting-up-management-studio-for-remote-sql-server

    More helpful information: how-to-connect-to-a-remote-sql-server

    BR,
    Mia
    If the reply helped, please “Accept Answer” and upvote it.--Mia

    6 people found this answer helpful.

  2. Raúl R 16 Reputation points
    2021-09-07T11:50:24.957+00:00

    Hi,

    In my case, Login was set it up only as Windows user, therefore I could not login as SQL Server user. I could not find out how or who did the change. Anyway, I found a way to fix it by changing the Loginmode thruogh the registry.

    Open the registry and go to HKLM \ Software \ Microsoft \ Microsoft SQL Server \ <instance> \ MSSQLServer \ LoginMode
    then change the value to “2” for the mixed mode.

    Restart SQLServer services. Now you should able to login as Server user

    Regards

    3 people found this answer helpful.

  3. Sandro Di Muccio 11 Reputation points
    2021-02-09T07:26:17.893+00:00

    hello everyone i had the same problem and i solved it by disabling password expiration,
    I hope this will help

    Disable password expiration on SQL user login

    1. Open SQL management studio
    2. Login with an appropriate admin-level account (using either Windows or SQL authentication)
    3. Expand Security – Logins
    4. Right click the desired login and choose properties
    5. Untick enforce password expiration
    6. Choose OK
    2 people found this answer helpful.

  4. Shashank Singh 6,246 Reputation points
    2020-08-19T16:35:48.87+00:00

    Can you please check below two Stackoverflow links, they are highly voted answer and points to step that you enable mixed mode authentication and restart SQL Server service. I don't know logic behind this but please test and let me know if that works for you

    a-connection-was-successfully-established-with-the-server-but-then-an-error-occ

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

    1 person found this answer helpful.

  5. Ray Tate 5 Reputation points
    2023-06-14T15:32:18.4133333+00:00

    In all likelihood, your SQL server login is locked out.

    • In SQL Server Management Studio, login into the server with a Windows account.
    • Expand the Security Tab, right-click the account in question and choose Properties.
    • Click "Status" and see the checkbox labelled "SQL Server Authentication".
    • If the "Login is locked out" is checked, uncheck it.
    • It may prompt you to reset the password. Click the General tab, reset the password (can be the same as teh old one)
    • hit OK and you should be all set.
    1 person found this answer helpful.