November 16, 2017 at 4:00 pm
Getting this while trying to login via SSMS on a SQL 2014 Server
TITLE: Connect to Server
------------------------------
Cannot connect to (local).
------------------------------
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=51; handshake=14954; (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
------------------------------
Br. Kenneth Igiri
https://kennethigiri.com
All nations come to my light, all kings to the brightness of my rising
November 16, 2017 at 4:32 pm
Br. Kenneth Igiri - Thursday, November 16, 2017 4:00 PMGetting this while trying to login via SSMS on a SQL 2014 ServerTITLE: Connect to Server
------------------------------Cannot connect to (local).
------------------------------
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=51; handshake=14954; (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
------------------------------
Is the server running? Can you ping the server name? If not can you ping the IP address for the server?
Other things to check would be
is the firewall is blocking the port - you can test by seeing if you can telnet to the server port.
is the browser service running if a named instance or are you providing the port,
is TCP/IP protocol enabled.
Sue
November 16, 2017 at 5:58 pm
Thanks so much Sue.
I am logged in via RDP.
Apparently this was only happening when I used (local). And the I account I was given does not have sysadmin privileges so I have decided to rebuild the instance.
Br. Kenneth Igiri
https://kennethigiri.com
All nations come to my light, all kings to the brightness of my rising
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply