Sql 2005 err 233 ?  
Author Message
balaganesh





PostPosted: Tue Apr 24 09:20:29 CDT 2007 Top

SQL Server Developer >> Sql 2005 err 233 ?

Hi all
I have this problem when connecting to sql 2005 :
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.) (.Net
SqlClient Data Provider)
what should I do?
thanks in advance

SQL Server61  
 
 
Martin





PostPosted: Tue Apr 24 09:20:29 CDT 2007 Top

SQL Server Developer >> Sql 2005 err 233 ? Would you please further describe how you make the connection?
What protocols are enabled on the SQL Server? ( Named pipes? )
What protocols are enabled on the client machine? and, what is the
connection order for the protocols?
Whether SSL encryption is used on the SQL Server? and, what is the operating
system?

I think you may be trying to connect to the SQL Server using named pipes,
while named pipes are not enabled on the SQL Server;
Or, are you using SSL encryption on the SQL Server that is running under
Winidows XP or Windows 2000, while the SSL certificate is having problem?

Depending on your problem/situation, either one of the following may help to
solve the problem.
~ On the client computer, use TCP/IP to connect to the SQL Server;
~ Or, on the client computer, use SQL Server Configuration Manager to move
TCP before named pipes in the protocol order list;
~ Or, on the SQL Server, use SQL Server Surface Area Configuration tool to
enable named pipes;
~ Or, on the SQL Server, use a valid certificate that has the AT_EXCHANGE
key specification.

--
Martin Poon | Microsoft MVP (SQL Server)
http://msmvps.com/blogs/martinpoon

-----------


> Hi all
> I have this problem when connecting to sql 2005 :
> 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.)
> (.Net SqlClient Data Provider)
> what should I do?
> thanks in advance
>

 
 
perspolis





PostPosted: Tue Apr 24 09:08:55 CDT 2007 Top

SQL Server Developer >> Sql 2005 err 233 ? thanks :)
I found it..
I enabled it with Sql Server Surface


> Would you please further describe how you make the connection?
> What protocols are enabled on the SQL Server? ( Named pipes? )
> What protocols are enabled on the client machine? and, what is the
> connection order for the protocols?
> Whether SSL encryption is used on the SQL Server? and, what is the
> operating system?
>
> I think you may be trying to connect to the SQL Server using named pipes,
> while named pipes are not enabled on the SQL Server;
> Or, are you using SSL encryption on the SQL Server that is running under
> Winidows XP or Windows 2000, while the SSL certificate is having problem?
>
> Depending on your problem/situation, either one of the following may help
> to solve the problem.
> ~ On the client computer, use TCP/IP to connect to the SQL Server;
> ~ Or, on the client computer, use SQL Server Configuration Manager to move
> TCP before named pipes in the protocol order list;
> ~ Or, on the SQL Server, use SQL Server Surface Area Configuration tool to
> enable named pipes;
> ~ Or, on the SQL Server, use a valid certificate that has the AT_EXCHANGE
> key specification.
>
> --
> Martin Poon | Microsoft MVP (SQL Server)
> http://msmvps.com/blogs/martinpoon
>
> -----------


>> Hi all
>> I have this problem when connecting to sql 2005 :
>> 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.) (.Net SqlClient Data Provider)
>> what should I do?
>> thanks in advance
>>
>