SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


** Urgent !!! ** Connection Timeout Expired !


** Urgent !!! ** Connection Timeout Expired !

Author
Message
farax_x
farax_x
Hall of Fame
Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)

Group: General Forum Members
Points: 3297 Visits: 571
I have this error randomly while connecting to Sql Server instance :

Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.
This could be because the pre-login handshake failed or the server was unable to respond back in time.
The duration spent while attempting to connect to this server was - [Pre-Login] initialization=0; handshake=14999; (Microsoft SQL Server, Error: -2)

Firewall is Ok
Ipv4 and Ipv6 are enable and active in network configuration


Microsoft SQL Server 2012 (SP2-CU8) (KB3082561) - 11.0.5634.1 (X64) Enterprise Edition (64-bit) on
Windows NT 6.2 <X64> (Build 9200: )
shamshad.ali
shamshad.ali
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3456 Visits: 700
1- Check Eventviewer
2- Check disk free space
3- Try login with SQLCMD using [sysadmin] windows login or sa if it works
4- Read database Error Log, what is going on the server.
5- Check history to see what is changed/modified or ran over last moments.

There is a list going on. See if this helps to have some clue on issue and you can resolve.


Shamshad Ali
farax_x
farax_x
Hall of Fame
Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)

Group: General Forum Members
Points: 3297 Visits: 571
I have problem when using network because I have no problem when connect using "." but I have difficulty when using "127.0.0.1" !
Event long errors are these :
1- Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 192.168.128.76]

2- SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

3- Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

4-TDSSNIClient initialization failed with error 0x50, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The file exists.
shamshad.ali
shamshad.ali
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3456 Visits: 700
How you are trying to connect to your server. Write some details about your environment. Like Server OS, SQL Server Version/SP, [Server and client], Client tools you are using to connect.
Is your server far from premises. what client software you are using to connect to SQL Server etc. Much environmental details may require to understand first.

see furthermore here: https://www.mssqltips.com/sqlservertip/3114/sql-server-could-not-spawn-fruncommunicationsmanager-thread/

Shamshad Ali
farax_x
farax_x
Hall of Fame
Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)

Group: General Forum Members
Points: 3297 Visits: 571
It occurs in all environments when connecting also "Sql management studio" :
TITLE: Connect to Server
------------------------------

Cannot connect to 127.0.0.1.

------------------------------
ADDITIONAL INFORMATION:

Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=1; handshake=14998; (Microsoft SQL Server, Error: -2)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476

------------------------------

The wait operation timed out

------------------------------
BUTTONS:

OK
------------------------------
mark.williams 37494
mark.williams 37494
UDP Broadcaster
UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)

Group: General Forum Members
Points: 1485 Visits: 289
Are the SQL services running?

_________________________________________________________________


"The problem with internet quotes is that you cant always depend on their accuracy" -Abraham Lincoln, 1864
farax_x
farax_x
Hall of Fame
Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)

Group: General Forum Members
Points: 3297 Visits: 571
mark.williams 37494 (11/18/2015)
Are the SQL services running?


Yes of course !
anthony.green
anthony.green
SSC Guru
SSC Guru (106K reputation)SSC Guru (106K reputation)SSC Guru (106K reputation)SSC Guru (106K reputation)SSC Guru (106K reputation)SSC Guru (106K reputation)SSC Guru (106K reputation)SSC Guru (106K reputation)

Group: General Forum Members
Points: 106716 Visits: 8698

1- Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 192.168.128.76]

Whats the client library, is it 3rd party, have you spoke to them



2- SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

What does the error log and event log say?


3- Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

What does the error log and event log say?


4-TDSSNIClient initialization failed with error 0x50, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The file exists.

Not using SSL certs to encrypt client traffic between client & server are you? If so has the cert expired? If you remove SSL from the SQL config does it work?
What previous errors are there in the error and event log?



How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger


farax_x
farax_x
Hall of Fame
Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)Hall of Fame (3.3K reputation)

Group: General Forum Members
Points: 3297 Visits: 571
anthony.green (11/18/2015)

1- Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 192.168.128.76]

Whats the client library, is it 3rd party, have you spoke to them

ado.net


2- SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

What does the error log and event log say?

these are errors which are related to MSSQL in eventlog



3- Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

What does the error log and event log say?

these are errors which are related to MSSQL in eventlog




4-TDSSNIClient initialization failed with error 0x50, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The file exists.

Not using SSL certs to encrypt client traffic between client & server are you? If so has the cert expired? If you remove SSL from the SQL config does it work?
What previous errors are there in the error and event log?


I dont have any ssl configuration
mark.williams 37494
mark.williams 37494
UDP Broadcaster
UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)UDP Broadcaster (1.5K reputation)

Group: General Forum Members
Points: 1485 Visits: 289
So you are on the SQL server itself and you are trying to connect to 127.0.0.1 ?

_________________________________________________________________


"The problem with internet quotes is that you cant always depend on their accuracy" -Abraham Lincoln, 1864
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum









































































































































































SQLServerCentral


Search