No process is on the other end of the pipe.) (Microsoft SQL Server, Error: 233)

Kiran Kumar 0 Reputation points
2024-08-28T13:53:09.1266667+00:00

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)

so above error was getting when i am trying to login to my db. So what happened is i have deleted the my db log file C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\NEWDB_log.ldf. So after the logfile i am getting above error and my db went to mode -- recovery pending. Help in resolving it.

SQL Server | Other
{count} votes

2 answers

Sort by: Most helpful
  1. Erland Sommarskog 122.4K Reputation points MVP Volunteer Moderator
    2024-08-28T21:23:15.7766667+00:00

    The login message may be due to that you are specifying the unfortunate database in your connection string. Change it to another database, and you will get into your instance.

    As for the database, if you have a clean backup, restore that backup. If you don't have a backup, I am afraid that your prospects are bleak. You can try

    ALTER DATABASE db SET EMERGENCY 
    

    I am not sure that it works, but if it does, you can access the database on a read-only basis, so that you can extract as much as you can to a new database.

    0 comments No comments

  2. Anonymous
    2024-08-29T01:54:33.9633333+00:00

    Hi @Kiran Kumar,

    Thank you for your reaching out and welcome to Microsoft Q&A!

    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)

    In addition to Erland's suggestion, here is the list to be checked when Microsoft SQL server error 233 in SQL server occurs:

    1. Enable SQL server and Windows authentication
    2. Check default database
    3. Max allowed connections
    4. Shared memory, TCP/IP, Named Pipes
    5. Check if the SQL server browser has started
    6. “Maximum server memory” to below the amount which could run the services
    7. Check for remote connection

    For more detailed steps, please refer to this article. Here is an official documentation, hope it can help you resolve the issue!

    So, after the logfile I am getting above error and my db went to mode -- recovery pending.

    I agree with Erland, you could restore your backup to resolve this issue.

    Feel free to share your issues here if you have any concerns!

    Best regards,

    Lucy Chen


    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    https://docs.microsoft.com/en-us/answers/support/email-notifications


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.