Monday, June 01, 2009 1:14 PMHi,
We are using domain name instead of IP in connection string. It may be issue for this type of error:
Unable to complete login process due to delay in opening server connection
We are getting this error suddenly after transfer our SQL Server 2005.
Monday, June 01, 2009 1:23 PMModeratorHave a look at:
A successful TCP connection from SqlClient to the server was broken due to a TCP keep-alive heartbeat failure (typically indicating problems with the underlying network infrastructure):
Check your duplex settings of your network cards for the SQL Server as well as the client machine making the connection to make sure that they are configured properly.
Please click the Mark as Answer button if a post solves your problem!
Monday, June 01, 2009 1:42 PMHi Jonathan,
If we will use direct IP in connection string, then it will fix this issue or still in this case, we have to check the configuration for TCP/IP. Because this issue comes occasionally.
Wednesday, June 03, 2009 8:41 AMModerator
You mean the error doesn’t occur every time and it happens random. Try to enlarge the connect timeout to around 30 seconds. If you want to connect using FQDN as server name, try to turn on File and Printer Sharing and explicitly use named pipe protocol.
If there are any more questions, please let me know.
***Xiao Min Tan***Microsoft Online Community***