SQL 2005 Login Error: A connection was successfully established with the server, but then an error occurred during the pre-login handshake

Question

0.00/5 (No votes)

See more:

Hello everyone

I'm trying to connect to a sql 2005 shared server with a dedicated Ip by Microsoft Sql server management studio.

I have no problem to connect and use it, but after a while, the connection will be closed and need to reconnect, I try to do, but the following error appears:

"A connection was successfully established with the server, but then an error occurred during the pre-login handshake"

The interesting point is, when I try to connect with another PC ( with another internet connection I mean ), the connection will be created with no errors.

I've googled it and found some solutions like: enabling the pipe names and tcp connections, but no one helped me.

if you have an idea, please help me.

thanks in advance

Posted 4-Dec-11 0:25am

vahid_gian

Updated 4-Dec-11 0:55am

Eduard Lu

v4

Add a Solution

Comments

[no name] 4-Dec-11 6:55am

EDIT: added emphasis on error

vahid_gian 4-Dec-11 7:03am

thanks Eduard

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wendelius · Answer 1 · 2011-12-04T01:13:00

Solution 1

Sounds like this could be an issue with your network. if you're using SSMS, have you tried increasing the connection time-out parameter before attempting to connect to the server.

Posted 4-Dec-11 1:13am

Wendelius

Comments

thatraja 4-Dec-11 7:49am

Possible case, 5! But I found MSDN link

Wendelius 4-Dec-11 16:13pm

Could be, hopefully the OP updates this if it gets solved.

thatraja · Answer 2 · 2011-12-04T01:48:00

From MSDN[^]:
Error "A connection was successfully established with the server, but then an error occurred during the pre-login handshake" occurs when connecting to remote SQL Server databases on SQL Server 2008

Problem

BizTalk Server loses connectivity with a remote SQL Server computer that houses the BizTalk Server databases and an error message is generated:

Cause

This problem may occur if one or more of the following conditions is true:

* SQL Server is not configured to accept remote connections.

* The necessary protocols for SQL Server are not enabled on either the SQL Server computer or the SQL Server client computer that is running BizTalk Server.

Resolution

Follow these steps to resolve this problem:

* The SQL Server Surface Area Configuration tool is not available on SQL Server 2008. To enable remote connections for SQL Server on a SQL Server 2008 computer follow the instructions in the SQL Server 2008 online help.

* Use the SQL Server Configuration Manager tool to enable the TCP/IP and/or the Named Pipes protocols on the SQL Server computer.

1. Click Start, point to All Programs, and click SQL Server Configuration Manager.

2. Click to expand SQL Server Network Configuration and then click Protocols for MSSQLSERVER.

3. Right-click the TCP/IP protocol and then click Enable.

4. Right-click the Named Pipes protocol and then click Enable.

5. Close the SQL Server Configuration Manager tool.

* Use the SQL Server Configuration Manager tool to enable the TCP/IP and/or the Named Pipes protocols on the SQL Server client computer that is running BizTalk Server.

1. Click Start, point to All Programs, and click SQL Server Configuration Manager.

2. Click to expand SQL Server Network Configuration and then click ClientProtocols.

3. Right-click the TCP/IP protocol and then click Enable.

4. Right-click the Named Pipes protocol and then click Enable.

5. Close the SQL Server Configuration Manager tool.