November 18, 2015 at 1:39 am
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: )
November 18, 2015 at 1:47 am
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
November 18, 2015 at 2:37 am
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.
November 18, 2015 at 2:48 am
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
November 18, 2015 at 3:01 am
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
------------------------------
November 18, 2015 at 3:16 am
Are the SQL services running?
_________________________________________________________________
"The problem with internet quotes is that you cant always depend on their accuracy" -Abraham Lincoln, 1864
November 18, 2015 at 3:20 am
mark.williams 37494 (11/18/2015)
Are the SQL services running?
Yes of course !
November 18, 2015 at 3:25 am
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?
November 18, 2015 at 3:41 am
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
November 18, 2015 at 3:48 am
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
November 18, 2015 at 11:44 am
mark.williams 37494 (11/18/2015)
So you are on the SQL server itself and you are trying to connect to 127.0.0.1 ?
Yes. It connects when I'm connecting with "." or server name but it doesnt connect when using "127.0.01" !!!
November 19, 2015 at 1:53 am
farax_x (11/18/2015)
mark.williams 37494 (11/18/2015)
So you are on the SQL server itself and you are trying to connect to 127.0.0.1 ?Yes. It connects when I'm connecting with "." or server name but it doesnt connect when using "127.0.01" !!!
so is the instance configured to listen on the network card loopback address?
_________________________________________________________________
"The problem with internet quotes is that you cant always depend on their accuracy" -Abraham Lincoln, 1864
November 20, 2015 at 12:11 am
HI,
Sounds like you have a security\vulnerability scanner running somewhere in your environment .Try stopping it
and check if the issue persists. If it resolves your issue, kindly chat to your security team.
Regards,
Ashal
April 20, 2017 at 4:57 pm
I had a similar situation - except my error was:
Connection Timeout Expired
[Pre-Login] Initialization =18090; handshake=14281” error
This was where I was setting up an Availability Group and the first thing we do is try and connect to each secondary node from the primary node using SSMS.
Node 1 could not connect to Node 2 when using windows authentication but could using SQL Authentication.
But Node 2 could connect to Node 1 using windows and/or SQL Authentication..
For AGs we needed to use windows authentication.
The root cause was that Node 1 & 2 had secondary addresses that SQL Server was listening on and DNS had not been correctly setup for accessing the secondary address.
By putting in forward and reverse DNS entries the nodes could be connected to.
I have blogged further about it here:
https://hybriddbablog.com/resolution-to-connection-timeout-expired-pre-login-initialization-18090-handshake14281-error/
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply