Connection Error question

Hi All,

Using ms sql 2005 on Windows XP SP2

Why would I get the below error? In the Surface Area Configuration I went
into the Remote Connector and selected as follows:
Local and Remote connections
Using both TCP/IP and named pipes.

Connection Error(s):
Index #: 0
Source: .Net SqlClient Data Provider
Class: 20
Number: 233
Message: A connection was successfully established with the server, but then
an error occurred during the pre-login handshake. When connecting to SQL
Server 2005, this failure may be caused by the fact that under the default
settings SQL Server does not allow remote connections. (provider: Named
Pipes Provider, error: 0 - No process is on the other end of the pipe.)

Thanks,

Joe

Have you checked the Books Online topic "Troubleshooting: No Process Is on
the Other End of the Pipe"?
http://msdn.microsoft.com/en-us/library/ms175496.aspx
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"JoeP" wrote in message
news:uG%23XE59AJHA.6060-at-TK2MSFTNGP04.phx.gbl...
> Hi All,
>
> Using ms sql 2005 on Windows XP SP2
>
> Why would I get the below error? In the Surface Area Configuration I went
> into the Remote Connector and selected as follows:
> Local and Remote connections
> Using both TCP/IP and named pipes.
>
> Connection Error(s):
> Index #: 0
> Source: .Net SqlClient Data Provider
> Class: 20
> Number: 233
> Message: A connection was successfully established with the server, but
> then an error occurred during the pre-login handshake. When connecting to
> SQL Server 2005, this failure may be caused by the fact that under the
> default settings SQL Server does not allow remote connections. (provider:
> Named Pipes Provider, error: 0 - No process is on the other end of the
> pipe.)
>
> Thanks,
>
> Joe
>

Hello Joe,

I documented a similar error like yours. I know it's not exactly the same
error message, however its error number is the same and problem seems akin.

Error Message:
"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)"

Description:
You get this error if you try to connect to your SQL Server Instance using a
wrong Login info. For example, if you type a wrong password for your Login,
then you get this error and you see a message like this: ""Login failed for
user '...'. (Microsoft SQL Server, Error: 18456)" in your SQL Error Logs.

You also may get this error if the Login you try to log on is disabled. For
example, "sa" Login is disabled by default (in some editions of SQL Server
2005). If you try to use this Login, then you may get the above error
message.

--
Ekrem Önsoy




"JoeP" wrote in message
news:uG%23XE59AJHA.6060-at-TK2MSFTNGP04.phx.gbl...
> Hi All,
>
> Using ms sql 2005 on Windows XP SP2
>
> Why would I get the below error? In the Surface Area Configuration I went
> into the Remote Connector and selected as follows:
> Local and Remote connections
> Using both TCP/IP and named pipes.
>
> Connection Error(s):
> Index #: 0
> Source: .Net SqlClient Data Provider
> Class: 20
> Number: 233
> Message: A connection was successfully established with the server, but
> then an error occurred during the pre-login handshake. When connecting to
> SQL Server 2005, this failure may be caused by the fact that under the
> default settings SQL Server does not allow remote connections. (provider:
> Named Pipes Provider, error: 0 - No process is on the other end of the
> pipe.)
>
> Thanks,
>
> Joe
>

Thanks for the replies