SQL 2008 Connection timeout period has expired

Question

1.00/5 (1 vote)

See more:

hello,
"
Connection timeout period has expired. When trying to use the pre-login handshake confirmed that exceeds this timeout. This may be because the pre-login handshake fails or the server failed to respond. Try to connect to the server when the duration is spent - [Pre-Login] initialization = 0; handshake = 14997;
"

Posted 29-Apr-14 2:30am

H_Zihuatanejo

Add a Solution

Comments

CHill60 29-Apr-14 8:33am

How are you trying to connect?

H_Zihuatanejo 29-Apr-14 8:38am

C# VS2008

RahulMGunjal 29-Apr-14 9:00am

Share code snippet for better understanding

H_Zihuatanejo 30-Apr-14 5:14am

Thanks.

1 solution

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)

CHill60 · Accepted Answer · 2014-04-29T02:57:00

You can adjust the timeout property on the C# connection object reference here[^]

Here is an article about alternate methods of doing that catering for other circumstances controlling timeouts[^]

And just in case it's something more severe have a look at this guys blogs ...e.g. http://blog.sqlauthority.com/2007/04/23/sql-server-fix-error-40-could-not-open-a-connection-to-sql-server/[^]