Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ODBC Clients Dropping Connection

Status
Not open for further replies.
GuyEBCS

GuyEBCS

Programmer
Sep 26, 2006
10
US
Help would be GREATLY appreciated!

Our database's infrastructure consists of a Server database which has around 30 client connections. Sometimes, and without warning, client connections will drop with a message stating something like "ODBC error: Connection was terminated."

All of our clients connect to the server under the same login and password. We thought that I may have been a licensing issue but we have since ruled that out through trial and error.

If anyone could help, even a nudge in the right direction, it would be greatly appreciated. Thanks!
 
Sort by date Sort by votes
Oh, also, it probably isn't anything to do with an Idle Timeout since these clients are in full use when the connection is dropped. The only way to connect back to the database has seemed to be restarting BOTH the Client and the Server machines.
 
Upvote 0 Downvote
The ODBC Server is... still running and has other client machines that can connect to it freely. Is that what you meant?
 
Upvote 0 Downvote
No.

What is the database? ODBC is a standardized interface used by dozens of database systems. Which database system are you using? It might help to know this minor detail...

Tom Morrison
 
Upvote 0 Downvote
My first step would be to enable ODBC tracing on the client(s) and see if there is some specific request that is causing this problem.

Enable ODBC tracing for the datasource through the Control Panel applet.

Tom Morrison
 
Upvote 0 Downvote
OK will do. I will report any findings from the log.
 
Upvote 0 Downvote
There is an idle timeout set to 240 minutes (4 hours). Since all of the connections are connecting to the DB with the same user/pass, does that mean they are all using the same license? If so... could it be that one of the computers is idle for 240 minutes, the server sees this, and disconnects all of them? Just a thought...
 
Upvote 0 Downvote
Idle timeout? Can you specify how you determined this? What ODBC function was used to specify this, for example? There are several timeout values in the ODBC spec.

If there is a problem with using the same user identification, I would think it most likely that you would experience difficulty establishing a connection, rather than dropping an existing connection.

What is in the ODBC trace?

Tom Morrison
 
Upvote 0 Downvote
I haven't done a trace yet... I physically need to go to the site of this problem to do that, and also I just got that post anyway.

Well, I know from experiance that the idle connection timeout is defaulted to 240 minutes. Also, I can PCAnywhere into their server computer and read their connection log using the sql icon in their systray. That's where I saw the idle timeouts.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

Rudraya
  • Locked
  • Question
failed connecting odbc
Replies
0
Views
288
Rudraya
Rudraya
dcern
  • Locked
  • Question
Ingres ODBC Driver slow
Replies
0
Views
282
dcern
dcern
MDGarcia
  • Locked
  • Question
ODBC error: Specified driver could not be loaded due to system error 193
Replies
1
Views
479
k5tm
k5tm
ceil32
  • Locked
  • Question
ODBC Connection - Windows 7 64 Bit
Replies
0
Views
281
ceil32
ceil32
brk1221
  • Locked
  • Question
ODBC connection from Windows to IBM Informix
Replies
3
Views
364
genomon
genomon

Part and Inventory Search

Sponsor

Back
Top