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

Question

Let me begin by saying, I am aware of this thread and others around the web that seek to trouble shoot this issue.

The solutions posted there do not apply to my issue. I have spent 5 hours trying to resolve this before deciding to ask the question.

The problem: When I attempt to log into SSMS (or connect from a java application) using SQL Authentication I get this 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)

Although it does work, it is not an option for me to use integreated authentication. The database I am attempting to connect to is on the same machine as my SSMS instance. There is no network, this is a stand-alone system.

NAMED PIPES is ENABLED in my configuration, I HAVE rebooted since, TCP IP is a higher priority than named pipes in my configuration.

I have even gone as far as to uninstall SQL Server and reinstall it, to no avail.

The details of my SQL Server instance are as follows:

Microsoft SQL Server Management Studio - 10.0.2531.0 Microsoft Analysis Services Client Tools - 10.0.1600.22 Microsoft Data Access Components (MDAC)  - 6.1.7601.17514 Microsoft MSXML - 3.0 5.0 6.0  Microsoft Internet Explorer - 9.0.8112.16421 Microsoft .NET Framework - 2.0.50727.5466 Operating System     - 6.1.7601 

Configuration details are as follows: http://i45.tinypic.com/vxdz7c.png http://i45.tinypic.com/vxdz7c.jpg

I connect from java using this code.

Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver"); String connectionUrl = "jdbc:sqlserver://localhost;database=AdventureWorks;integratedSecurity=false;User=JIMBO; Password=JIMBO;"; Connection con = DriverManager.getConnection(connectionUrl); 

But please remember, this error also occurs when I atttempt to log in to SSMS directly. Thanks in advance.

-Jim

Answer 1

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.

Answer 2

Forcing the TCP/IP connection (by providing 127.0.0.1 instead of localhost or .) can reveal the real reason for the error. In my case, the database name specified in connection string was incorrect.

So, here is the checklist so far:

• Make sure Named Pipe is enabled in configuration manager (don't forget to restart the server).
• Make sure SQL Server Authentication (or Mixed Mode) is enabled.
• Make sure your user name and password are correct.
• Make sure the database you are connecting to exists.