ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    MS SQL Server Error: No Process is on the other end of the pipe

    IT Discussion
    database ms sql server
    3
    3
    1.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • scottalanmillerS
      scottalanmiller
      last edited by

      Full error...

      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)
      

      This error tends to happen when you are trying to authenticate with a SQL Server account on a system that is only configured for Windows Authentication. MS SQL Server allows SQL accounts to be created regardless of this setting in the configuration and gives no errors (for logical reasons we could go into) so it is easy to do without realizing it. So if you see this error, check to make sure that SQL Server authentication is enabled or use a Windows account instead.

      PhlipElderP 1 Reply Last reply Reply Quote 2
      • PhlipElderP
        PhlipElder @scottalanmiller
        last edited by

        @scottalanmiller said in MS SQL Server Error: No Process is on the other end of the pipe:

        Full error...

        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)
        

        This error tends to happen when you are trying to authenticate with a SQL Server account on a system that is only configured for Windows Authentication. MS SQL Server allows SQL accounts to be created regardless of this setting in the configuration and gives no errors (for logical reasons we could go into) so it is easy to do without realizing it. So if you see this error, check to make sure that SQL Server authentication is enabled or use a Windows account instead.

        We deal with some really clunky front ends that run with SA/SQL Authentication so hybrid mode is a setting that gets done during the initial instance setup process.

        The other thing to keep in mind is that if there is more than one admin account being used to manage that instance, or those instances, to make sure to add those accounts during the instance creation process otherwise pain ensues.

        1 Reply Last reply Reply Quote 1
        • ITivan80I
          ITivan80
          last edited by

          Thank you for the heads up @scottalanmiller

          1 Reply Last reply Reply Quote 0
          • 1 / 1
          • First post
            Last post