connection failure
-
Tuesday, January 22, 2013 10:03 AM
Hi,
We have encountered a problem that I will explain as bellow:
We have an application that uses ADO to connect to SQL Server 2008 R2. Our clients are connected to the SQL engine throw LAN.
Sometimes our client's software faced with "connection failure" error message without LAN disconnected.
This error message does not contain "server does not exist or access denied" message. The connection should be restart so the software could work normally again. In fact it seems that you had disconnected the LAN Cable and reconnect it again.
Of course we tested the network platform and its dependencies. The network that we used for test was LAN with cat6 SFTP cables and or Wireless network with low noise and high quality signal. We also tested different switches and routers.
This error usually happens when user does not work with interface for a few minutes.
If you have any idea how should I fix this, please let me now.
All Replies
-
Tuesday, January 22, 2013 10:06 AMAre you able to ping the server in the client machine? Make sure you do this before building the connection.
Many Thanks & Best Regards, Hua Min
- Edited by HuaMin ChenMicrosoft Community Contributor Tuesday, January 22, 2013 10:06 AM
-
Tuesday, January 22, 2013 10:51 AM
Only SQL services are affected ?What about the other application like IE, outlook or anything that uses LAN?
This doesn't look like a SQL related issue.
Regards
Satheesh
-
Tuesday, January 22, 2013 11:17 AM
It seems a problem about time out. It's not a SQL problem but need to help each other. So, do you have a domain controller? When this happens ( I mean the error message) you should try to connect in internet for example just to understand if the problem belong to the software or to the client ( I think first option). If is a software problem and not a LAN problem you are near the solution. Try and afterward let us now....
This error usually happens when user does not work with interface for a few minutes.
If you have any idea how should I fix this, please let me now.
-
Tuesday, January 22, 2013 9:05 PMModerator
This is almost always a symptom of the application timeout or the database having "Auto Close" set ON (which is the default in SQL Express).
- Proposed As Answer by Kalman TothMicrosoft Community Contributor, Moderator Tuesday, January 29, 2013 8:15 PM
- Marked As Answer by Iric WenModerator Wednesday, January 30, 2013 9:21 AM

