then an error occurred during the login process - Connection Error 233

Question

We have SQL Server 2008 installed on 64Bit Windows Server 2003. When we try connect to the local SQL Server using SQL Server Management Studio at the console, we get the 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.

When we try TCP from same local SSMS to local server, we get the same error but intead of the pipe message its something like

"connection forcibly closed".

Now, here is the strange part - we CAN connect to this SQL Server from any other machine on the network using SSMS. - AND - WE CAN'T connect to ANY SQL Server from the problem server.

So it seems the SQL Server instance is fine and accepting remote connections. However, the SSMS on that machine will not connect to any SQL Server even remotely.

When we try an ADO.NET connection from C# remotely we can connect, run that same code on the console of the trouble server and we get the same errors.

How can this be solved?

Answer 1

Often a password change or some other account issue (eg locked out).

See this on one of the MS SQL Protocol blog. And another.

Answer 2

The fact that you can't connect to any other SQL Server as well from that machine is interesting. It could be that your SQL Server client components are not properly installed or configured - can you try reinstalling them? Look at your firewall settings on that machine too; are the ports that SQL Server uses blocked?

Another possibility: do you have Shared Memory, Named Pipes and TCP/IP protocols enabled on your SQL Server configuration?

Answer 3

Open up SQL server configuration manager: Start>MS SQL server..>Configuration tools>SQL server configuration manager. In the SQL Native client configuration>Client protocols, check if Shared Memory is enabled.